by dsmacdo » Thu Aug 07, 2014 6:13 pm
Hi Funkeyro,
MM by default uses the semi colon but can also be configured to use | under the options menu. As far as I know, Mp3Tag by default uses a double backslash.
Please note that I am in no way an expert at all this stuff and realize that tagging can be quite problematic as multiple media players or devices support one format but not necessarily others. My impression is that MM "officially" supports ID3V2 natively and thus, I was hoping that it would also handle much of the standard as defined. MM handles multiple genre fields & values with flac tags and I would have thought, that it would behave similarly with ID3V2.
MM does seem to understand that the file contains multiple genre values but for whatever reason, inserts a non-visible character on the second and subsequent field. I had a look at both the Flac's frame and equivalent frame contained within the MP3 file using a hex editor, and from my perspective, there is no difference whatsoever. Foobar does not seem to have an issue with the MP3 as tagged either.
At the request of support, I just tried to synch the tag from within MM and it seems to not re-tag correctly either. Despite having used the semi colon delimiter within MM's GUI, the resulting tag "merged" the separate fields into one. IMHO, there is indeed an issue with how MM handles ID3v2.3 tags. I had previously sent support the file (which was originally tagged with MP3Tag) and from what I got as a response, the file itself is fine. Please understand this is not to dis MM but rather, I am simply trying to resolve what I consider a "bug".
I am tagging in Unicode. Would anyone know if MM expects ISO- 8859-1 tags rather than UTF-16?
Hi Funkeyro,
MM by default uses the semi colon but can also be configured to use | under the options menu. As far as I know, Mp3Tag by default uses a double backslash.
Please note that I am in no way an expert at all this stuff and realize that tagging can be quite problematic as multiple media players or devices support one format but not necessarily others. My impression is that MM "officially" supports ID3V2 natively and thus, I was hoping that it would also handle much of the standard as defined. MM handles multiple genre fields & values with flac tags and I would have thought, that it would behave similarly with ID3V2.
MM does seem to understand that the file contains multiple genre values but for whatever reason, inserts a non-visible character on the second and subsequent field. I had a look at both the Flac's frame and equivalent frame contained within the MP3 file using a hex editor, and from my perspective, there is no difference whatsoever. Foobar does not seem to have an issue with the MP3 as tagged either.
At the request of support, I just tried to synch the tag from within MM and it seems to not re-tag correctly either. Despite having used the semi colon delimiter within MM's GUI, the resulting tag "merged" the separate fields into one. IMHO, there is indeed an issue with how MM handles ID3v2.3 tags. I had previously sent support the file (which was originally tagged with MP3Tag) and from what I got as a response, the file itself is fine. Please understand this is not to dis MM but rather, I am simply trying to resolve what I consider a "bug".
I am tagging in Unicode. Would anyone know if MM expects ISO- 8859-1 tags rather than UTF-16?