TAK 1.0.1 Development
Reply #37 – 2007-03-31 16:04:25
I think maybe two different things are being discussed here. In the APEv2 tag there may be multiple items stored under the same key, and these are separated by NULLs (although the last one doesn't have a NULL because the byte count is used for the length). However, when the strings are specified (or displayed), there's no way to input (or output) a NULL, so this has to be converted into some other regular but uncommon character. I added two different values to one key with TAG, and TAG seperated them only with "<>" (says my hex editor), but not with a zero character... But you are right, my initial question referred to the binary representation of the tag, not the way it is beeing specified at the command line. David is correct that I was discussing the interface, rather than the storage method - in Tag.exe the null separator is created using "<>". I tested this yesterday following your initial enquiry, and did note that it looks awful when displaying current tags, so I'm thinking of changing it to something more aesthetic, or reverting to "; " and pre-processing the content of files. When I tested I loaded the tagged files into foobar, and foobar listed them with the ";" separator as expected (or "," in ColumnsUI). I'm very confused regarding what you have seen in your hex editor - I guess I best take a look also. Given the following screenshot though I can't see how it can be the case - unless perhaps you used it in a field that won't allow it (if there is such a thing). Well, i should have shown you my command line parameters...TAG.EXE --artist "My Artist 1<>My Artist 2" --artist "My Artist 3" TAG will separate "My Artist 1" and "My Artist 2" with a zero char. Fine. But then it will add "<>My Artist 3", hence use "<>" instead of a zero as separator. Until your latest post i always used: "TAG.EXE --artist "My Artist 1" --artist "My Artist 2", and you were probably talking about TAG.EXE --artist "My Artist 1<>My Artist 2". This generated more confusion... Sorry. Next time i will immediately post the cmd line. I don't know how important this minor bug is, probably nobody else is using my syntax. And maybe i should read TAG's documentation...