MediaMonkey forum

I ran into some old info on editing the INI file for the enabling/disabling of frames:

example:
[MP3Tagging]
DisableFrames=TDRC;TDOR;
EnableFrames=TYER;TDAT;TORY;

I have an issue with Mediamonkey's use of the MOOD tag (as it conflicts heavily with the EXCELLENT tagging program JAIKOZ).

Mediamonkey can write/see TMOO fine. Great. But if I touch any tag in MM, then it ALSO writes the following version of a mood tag:

COMM ... XXXMusicMatch_Mood (the '...' is a varying length of always different hex characters something like 00 00 0E 00 00 )

Once this shows up things really fall apart for my mood tags. I've tried to use the "disable in the INI" technique but have had no luck. But I'm not sure what I should CALL this 'frame' if this would even work?

Anyone have any insight?

It's only possible for those, not others.

How do things fall apart though?

Thanks for the info!

Actually, the author of JAIKOZ is very active on his forum, and super helpful; but I don't think I convinced him to change his code just to help Mediamonkey handle the mood tag better.

Trying to figure out what happens starts to make me want to go look for a beer, but my assessment is that if a MOOD tag is written in JAIKOZ (set for ID3 v3.23) then it writes
XXX Mood
Which Mediamonkey will not recognize!
Set JAIKOZ to write it in ID3 v3.24 and it writes
TMOO
Which Mediamonkey WILL recognize. Thought things were fine, but:

Write to any tag to the file in Mediamonkey, and it ADDS the 'XXX MusicMatch_Mood' version of a MOOD tag.

At this point Mediamonkey is happy, but the file has two different MOOD animals in it (troublesome someday perhaps) and JAIKOZ doesn't understand what ID3 version is going on (or something) and NO mood tag will show up in JAIKOZ ever again, unless the MusicMatch stuff is stripped.

In some sense, that is a breakdown on JAIKOZ's side, but since the MusicMatch tag isn't asked for, nor helpful, nor reversible - I also blame Mediamonkey!

I'm actually a HUGE fan of mediamonkey - and its scripting capabilities; and the generous contributions of scripts by others are the primary classroom for some significant education I've acquired this past year! Unfortunately, I have relied heavily on the MOOD tag for a cornerstone of my personal tagging system. I should have used a Custom field, but I thought the way Mediamonkey gives Mood tag selection in a drop-down of checkboxes (in search or collections setup) I would enjoy the MOOD tag. Well, its been a lot of trouble, and I HATE the painfully unalphabetized checkbox dropdowns, at this point! ...but too late, really.

If I could make Mediamonkey see the "XXX Mood" then I could preference JAIKOZ to work solely in v3.23 (ideal solution, really, as then Jaikoz won't want to convert every file that Mediamonkey changed back to v3.24!). Otherwise I MUST have JAIKOZ set to v3.24.

I'd put the problem with Jaikoz. The reason is that additional tags shouldn't cause any issues and MediaMonkey does this for compatibility with as many software as possible.

I wonder why Jaikoz writes XXX Mood in v2.3, MediaMonkey only writes v2.3 and uses TMOO: http://www.mediamonkey.com/wiki/index.p ... erties/4.0

If you see any documentation supporting XXX Mood as the tag to use I can open a bug to see if XXX Mood can be added.

As for user defining of additional tags to be written, that has been requested and discussed, however I presume this may take a while to get done if ever.

Just Guessing wrote: and I HATE the painfully unalphabetized checkbox dropdowns, at this point! ...but too late, really.

These can be rearranged pretty easily. Just find the "Mood" node under whatever collection you're browsing and drag the moods into whatever order you want.

Thanks!! I obviously had not found the capability of reordering the moodtag checkboxes.

As far as any documentation per legitimacy, that makes it sound like an academic matter, where I'm not sure but the tag realm is more like a battlefield. I don't get the "XXX mood" bit either, but I really didn't want to tell the author of JAIKOZ how he should handle it, as he is all but a hero to me for bringing as much sanity and power to tagging as he has.

I did exchange with him about this and will make another effort to push for TMOO.

I MUST add, the very next webpage I looked at after initially reading your responses was www.mediamonkey.com/wiki/index.php/Scripting_Resources
as I was going to get back to you after doing some probing for technique to merge embeded album art...Immediately I'm looking at this:

"Cover Types
Known as CoverType field in the Covers database table.
Known as ItemType property of the ISDBAlbumArtItem interface.
These are the cover type values used by MediaMonkey, as defined by the ID3v2.4 specification:
ID ----Official ID3 Description --------- MediaMonkey Description
..
16 ---Movie/video screen capture ----Video Screen Capture
17 ----A bright coloured fish ----------- Not specified "

"A bright coloured fish "...Should that make sense?
Most of the time, I'm really not sure I know what is going on.

Seems to be used here too: http://en.wikipedia.org/wiki/ID3

Looking around I see every resource referring to TMOO as the Mood tag for ID3.

It IS comforting, that no matter what frustrations, what confusions, or what limitations the ID3 tag realm has -

that I will henceforth always have a home for my images of bright coloured fishes. I do wonder, will we EVER get a tag for the unappreciated DULL, colorless fish of the world???

ALSO, as the spelling of the word "coloured" seems perhaps British, is it improper usage of the tag to embed pictures of Asian fish, for example?

OK, right after harassing the author of JAIKOZ to make my world work by using TMOO for v3.23, it dawned on me there might be more headaches ahead...naturally.

Is THIS a 'bug'?
Once Mediamonkey alters a tag, any TMOO tag gets expressed in the "XXX MusicMatch_Mood" format as well.

Once the unrequested MusicMatch version shows up, Jaikoz (or a hex editor or anything) can alter TMOO all day long - Mediamonkey will ONLY care about the OLD MusicMatch tag.


So even if JAIKOZ implements TMOO for v3.23, Mediamonkey won't care, and will only look for its lil' pet version of the tag - which I suppose is fine if one makes a new year's resolution to never alter the MOOD tag except in Mediamonkey.

I'd presume that TMOO is the first used tag and that the Musicmatch tags is only written for compatibility. Are you saying it doesn't work like that?

Mediamonkey seems to only read TMOO in order to create the MusicMatch tag, then no longer pays any attention to external changes to TMOO. That doesn't seem quite right.

I'd like to see the "DisableFrames" in the INI file permit the shutdown of MusicMatch_Mood. I mean, its a little ironic that a queer tag is being inserted to generate 'compatibility' when all it does is for me is wickedly collapse compatibility. What programs read only MusicMatch tags?

Even Music Match probably uses TMOO at this point.

Any outside changes require rescanning (File > Add/Rescan Files).

I think I know whats going on.

In ID3 v3.23, NEITHER Jaikoz NOR Mediamonkey are using TMOO!

Mediamonkey, however, has been coded to interpret TMOO and translate it to "XXX MusicMatch_Mood". But only INITIALLY!

Jaikoz is using "XXX MOOD"
and Mediamonkey is USING "XXX MusicMatch_Mood"!!!

http://www.ventismedia.com/mantis/view.php?id=2953 indicates TMOO is written.

Well, let me put it this way:

Take a file with TMOO into Mediamonkey and write to it (generating MusicMatch_Mood) or use a file with both already
MOOD = PIG

Open the fie in hex editor, change TMOO = "DOG", leave MusicMatch_Mood tag alone


Main window/properties box after rescan file into MM:
MOOD = PIG

MM reads, even writes to TMOO, yes, but it is displaying and paying attention to MusicMatch_Mood!