Enabling or Disabling Frames?

[Lowlander]

I don't use other tag editors, so I can't confirm, but I added: http://www.ventismedia.com/mantis/view.php?id=12185

[Just Guessing]

Thanks.

Seriously, Jaikoz is to tags what Mediamonkey is to music listening - not perfect but REAAAAAL close. Mood tag is the enemy here.

[MiPi]

Hi, you're right. MusicMatch tags are preferred during tag reading from the very beginning. It probably needs to be changed, I think, standard tags should be preferred.
Meanwhile you can forbid writing of MusicMatch tags - backup and edit MediaMonkey.ini file, find section "[Options]" and add this line there:

Code: Select all

WriteMusicMatchTags=0

[Just Guessing]

BRILLIANT!!!

I hope your suggestion works. I'm sure I won't test the tip till I have enough time to carefully ensure doing so DOESN'T BREAK DOWN OTHER TAGS THAT WERE PREVIOUSLY WORKING. At this point the MOOD tag has been my only meltdown, so I have no knowledge of where else MusicMatch tags show up. Any insight?
I found an old thread http://www.mediamonkey.com/forum/viewtopic.php?t=2015 that suggests these may be fields with potential MusicMatch conflicts:

Mood
Tempo
Occasion
Encoded By

Even if your tip works, for JAIKOZ compatibility, I will still have to go back to the JAIKOZ author (again!) and urge him to use TMOO in 3.23 (Which he has said is NOT correct - but why "XXX Mood", which he uses, is correct seems subjective).

The mood tag certainly makes me moody.

[MiPi]

Mood was the only problematic tag, because TMOO is part of ID3v2.4 standard and should be handled preferentially (implemented from the next beta build). For Encoded by we use standard ID3 field, other MusicMatch tags (MusicMatch_Tempo, MusicMatch_Situation, MusicMatch_Preference) do not have standard ID3 alternatives, so we use our own custom XXX tags (and MusicMatch tags are still preferred). This should not be problem.
"WriteMusicMatchTags" setting only causes, that MM4 will not write any MusicMatch tags any more. They are read, but deleted during saving.