iTunNORM getting removed when add comment
Moderator: Gurus
iTunNORM getting removed when add comment
My Mp3s have the sound levelled by iTunes, and this is stored in a COMM field with description of iTunNORM. When I open file in MM the comment field is blank (which is fair enough because its not really a comment even though stored in COMM field) so I enter something into the Comment, then view in anotehr program to find my iTUnNORM field has been deleted and replaced by my newly added comment. Surely you should be adding the comment since multipel COMM Fields are allowed as long as thew description is different.
Re: iTunNORM getting removed when add comment
in fact it doesnt seem to see normal comments entered into iTunes either, I think because iTunes set a language of 'eng' (for english) and MM seems to use 'xxx'
Re: iTunNORM getting removed when add comment
The commment field weirdness with ITunes and several other mp3 management programs is pretty well known by now. Near as I can tell, MM doesn't always properly ignore or workaround the custom ITunes comments (Apple also can store gapless playback, cddb id, and a few pieces of metadata here). And since it doesn't harm playback - and EXISTING comments made in MM don't seem to be getting overwritten - I believe it's considered a low priority bug as chronicled elsewhere on this forum.
On top of that, sometimes switching between apps that save in different ID3 tag versions can cause "Artifacts" in the comments field or other tags themselves... the "xxx" and "eng" has something to do with either the 2.3 or 2.4 standard. All I know for sure is that whenever I inadvertently pull up ITunes (usually to do some sychronization task I can only do there), when I come back to MM it's padded all my blank comments fields with one of its aforementioned comment field hex data. But on the reverse side of things, our MM comments tend to often not be recognized in Itunes, or wipe out some of Itunes' own metadata.
You may want to read some other posts I found:
http://forums.slimdevices.com/archive/i ... 29719.html
http://hydrogenaudio.org/forums/lofiver ... 54617.html
http://yabb.jriver.com/interact/index.p ... =showPosts
Yeaaaa... probably more information than you wanted to know.
<---- Has a Mac & a PC, still hates ITunes ....
On top of that, sometimes switching between apps that save in different ID3 tag versions can cause "Artifacts" in the comments field or other tags themselves... the "xxx" and "eng" has something to do with either the 2.3 or 2.4 standard. All I know for sure is that whenever I inadvertently pull up ITunes (usually to do some sychronization task I can only do there), when I come back to MM it's padded all my blank comments fields with one of its aforementioned comment field hex data. But on the reverse side of things, our MM comments tend to often not be recognized in Itunes, or wipe out some of Itunes' own metadata.
You may want to read some other posts I found:
http://forums.slimdevices.com/archive/i ... 29719.html
http://hydrogenaudio.org/forums/lofiver ... 54617.html
http://yabb.jriver.com/interact/index.p ... =showPosts
Yeaaaa... probably more information than you wanted to know.
<---- Has a Mac & a PC, still hates ITunes ....