Force MM to write id3 v2.4 tags

[EGECK]

hello,
as long as the search option ignores "." it's very hard to search for v2.4. so i haven't found a good thread for my question.
if the question is already answered, I'm sorry for bothering you.

Is there any option to force MM to write id3 v2.4 tags instead of v2.3?

thanks for your support

egeck

[Lowlander]

No MediaMonkey currently uses 2.3 instead of 2.4. There has been a discussion about this where it was mentioned that 2.4 is a controversial version of the ID3 standard which might be the reason it isn't implemented.

[mistresso]

Question for the devs then:

I have been trying to figure out how the Mutagen library works - a Python library for manipulating Mp3 metadata ... and found out the hard way that their API seems to "auto convert" everything to 2.4 format. Ie, if I load an MP3 file, and then display its tags ("native frames" in the technical lingo), it uses some 2.4 specific tag names instead of the 2.3 versions... namely the ones for recording year. TYER has become TDRC, for example. But using another program that shows the raw binary data for each frame, it is still in 2.3 format.

Are any of you guys actually familiar at all with the Mutagen library, and if so, how are you getting around this? (maybe using an older version of the software library?)

It's all quite the headache. I wish the industry would pick a standard and go with it, but right now you can cause yourself quite a bit of pain while using multiple tagging apps. It is far too easy for developers who do not understand the intricacies of the version variations to cause more harm than good, as it's rarely included in your usual open source documentation as a warning.

[Lowlander]

For date see this Knowledge Base article, it might be of some help.