Wrong behavior of COMMENT field [#11218]

[MonkeyStrut]

hi all --

I've just migrated from Winamp to MM because it is much more appealing on many aspects. However, there is a wrong behavior I have just noticed which might make me go back to Winamp if I can't resolve it. I rely on your help to keep using MM.

I explain the problem:
* I have a large library of music files, all tagged in various fields, including the COMMENT field
* All my replaygain values are calculated (album and tracks) and are used for playback
* At work I listen to music from my computer (Winamp before, now MM)
* At home I listen to music using Sonos
* Sonos doesn't support replaygain values for MP3 files, but only volume information calculated from iTunes
* So I have to run a script in Mp3tag to transform my replaygain values to iTunes values and write them in the files tag, where they are supposed to be: in the COMMENT ITUNNORM field
* In MM, the first strange thing (i.e. wrong behavior at how it uses the COMMENT field) -- but which is not too much of a problem -- is that when my "traditional" COMMENT field of a given tag is empty, the value displayed in MM in the Comment column is not empty but the value of the COMMENT ITUNNORM field (which is always filled) (case 1). When my "traditional" COMMENT field is filled with values, those values are showed without the COMMENT ITUNNORM values (case 2).
* Now, the big problem is related to both cases above. In case 1, I can't add a comment (where COMMENT should be empty) to a track without modifying what is displayed by MM (the COMMENT ITUNNORM), which I don't want to modify. In case 2 (when MM properly displays what is in the COMMENT filed), if I open the track property editor and erase the displayed comment, it will also automatically erase the COMMENT ITUNNORM. Which I don't want either.

I've found this old post on the forum (http://www.mediamonkey.com/forum/viewto ... =7&t=35146) that basically says that there were issues with the COMMENT field. My hope is that this post being old, there is now a solution to this problem. Do you know of any?

thanks!
-cheer-

[Lowlander]

Added as: http://www.ventismedia.com/mantis/view.php?id=11218

[MonkeyStrut]

Thanks. let's hope it will be considered at some stage.

[MonkeyStrut]

wow. It's much worst than what I thought. let's consider a file with some info in the "traditional" COMMENT field. If I open the properties of the file and edit a different field from COMMENT (e.g. genre, disc number, or whatever) and click OK, what is present in the COMMENT field overwrites the COMMENT ITUNNORM field.

in other words, any kind of edit in any field of a tag would erase the COMMENT ITUNNORM field if some information is already present in the COMMENT field. meajning: I can't use MM to edit my tags or I have each time to recalculate the replaygain/volume normalization

[MiPi]

You're right, it is quite serious bug. It is fixed. The fix will be included in the next build.

[MonkeyStrut]

That is great news indeed! Thank so much for (1) that and (2) for the responsiveness that is so quick!:

MM team is great!

thanks!

[Lowlander]

This should be fixed in the latest beta of MediaMonkey 4.1.0.1658: http://www.mediamonkey.com/forum/viewto ... 46#p374146

[MonkeyStrut]

Yes, I was controlling the beta versions. When I saw that this was addressed, I've tested it this morning (EU time). It seemed to now work perfectly: the COMMENT ITUNNORM values remain where they should be and changing the COMMENT field values doesn't seem to affect the COMMENT ITUNNOM values.

Thanks!!!!!!!!!

[renowden]

Hi MonkeyStrut. I am interested in your script for mp3tag - can you share it please.

[Ada21!a]

The problem always occurs in the Comment field and no where else. If I delete the comment field the comment field information should not reappear if I press F5 or reopen MM. That is the problem.

[Lowlander]

Which version of MediaMonkey and are you working in the My Computer node in MediaMonkey?