Oh and using the replaygain scanner on your files will alter your tags and change them as mentioned above.
If you’d actually read the initial post, you’d know that the changes have nothing to do with how ReplayGain information is written; RG was only mentioned incidentally.
oh and using the replaygain scanner on your files will alter your tags and change them as mentioned above.
I use Pop/Rock as a Genre and don't want this to become multi-valued; i consider a single genre.Similarly, I use forward slash in my Style and Mood tags.Basically following the AllMusic standards.
I hope at the end of the day the page http://wiki.hydrogenaudio.org/index.php?ti...ID3_Tag_Mapping is enhanced to clarify exactly which frames handle multiple values (ID3v2.3 spec seems to only indicate TCOM, TOLY, and TOPE frames), and clearly indicate the characters users must enter to separate values, the character Foobar2000 displays to separate values, and the character written to files to separate values. Lastly, however Foobar2000 deals with multiple mp3 tags with the same field name of "comment", or any user attempts at multivalue entries for comments, it would be helpful if the ID3 tag mapping wiki page had a note clarifying that as well.
...or am i too confused to understand
Thus, I like the recent changes to TXXX frames, since this is more consistent with ID3v2.3. JRiver has no problems I can see in dealing with TXXX frames with unique descriptions, regardless of how JRiver handles TXXX frames with duplicate descriptors.
Edit: Neotheone, I've not noticed any problems in my TYER tags that display in Foobar2000 as "Date", but I've only looked at this in passing - can you please describe in a much more detailed manner (with examples) what you observed that concerns you regarding year and date?
Regarding mulit-value TCON:I'm open to suggestions how to do this yet keep foobar2000 tagging compatible with apps that do not recognize multiple TCON frames (iTunes, WMP).Semicolon as a separator sounds like a good starting point.
Regarding multi-value TXXX again:Maybe I'll just revert to the previous behavior since despite of being not strictly spec compliant it is less likely to cause trouble with other software.
4.2.6. User defined text information frame This frame is intended for one-string text information concerning the audio file in a similar way to the other "T"-frames. The frame body consists of a description of the string, represented as a terminated string, followed by the actual string. There may be more than one "TXXX" frame in each tag, but only one with the same description. <Header for 'User defined text information frame', ID: "TXXX"> Text encoding $xx Description <text string according to encoding> $00 (00) Value <text string according to encoding>
id3lib does not enforce proper frame formatting, it will let you write as many values to a frame as you want, regardless of how many that particular frame is supposed to support.If you want a library that enforces strict compliance, try libid3tag, if you can stomach the silly notion of a library being GPL.