01-22-2016, 02:36 AM
I'm considering it just from the perspective of the "datatypist" now.
Currently I'm still ambitious and want to add as much metadata I can retrieve from the displayed song or elsewhere (so composers, tempos, year and so on). I'm sure that will dwindle, but for now I'm hacking it in (10 finger typing).
For such bulk editing I really dislike the "|" for a sub separator. It's just not that accessible for typing and I much prefer the ";" as I wrote about it in another post already referencing Calibre and Mediamonkey for the same handling.
Maybe the parser can be flexible for the subseparators too? Define it in the CSV somehow if it's a "|", a ";" or whatever else? (of course it can't be the same as the field separator).
Currently I'm still ambitious and want to add as much metadata I can retrieve from the displayed song or elsewhere (so composers, tempos, year and so on). I'm sure that will dwindle, but for now I'm hacking it in (10 finger typing).
For such bulk editing I really dislike the "|" for a sub separator. It's just not that accessible for typing and I much prefer the ";" as I wrote about it in another post already referencing Calibre and Mediamonkey for the same handling.
Maybe the parser can be flexible for the subseparators too? Define it in the CSV somehow if it's a "|", a ";" or whatever else? (of course it can't be the same as the field separator).