request: tags option to use ID3 v2.3 date vs. ID3 v2.4

[ultracode]

MediaMonkey 4, by default, saves Year and Date metadata using the ID3 v2.4-associated TDRC frame. This leads to a situation where, when existing date tags from other software (Mp3tag, etc.) are overwritten, and then the same files are revisited in the alternative software, the date shows as "YEAR\\YEAR" instead of just "YEAR". This can be confusing to a user who is not familiar with the intricate technical details associated with variance between ID3 v2.3 and ID3 v2.4 implementations.

As seen in numerous forum entries, the user generally first discovers the issue when MediaMonkey overwrites some of their existing well-formed dates, and suddenly their collection has two different date formats, which "messes up" organization in other software. The user then searches for a solution and perhaps finds this obscure reference: http://www.mediamonkey.com/support/inde ... year--date which requires the user to manually edit an .ini file just to get the date tagging to conform to their other software. The user must add the following to the MediaMonkey.ini file:

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

This disables the ID3v2.4 TDOR which MM is using for Original Year, and enables use of the ID3v2.3 TORY, intended for original release year. Even more confusing to a non-technical user, the MP3Tagging section does not exist in the file but must be created, so if a user initially searches the .ini file for "MP3Tagging", they won't find it.

Not a good user experience. The average, normal user will just get frustrated/deterred and might give up on MM, thinking it is simply "messing up" their collection (as I've read in forum posts across the web).

Could you please create an option under Options > Tags which is something like:
"Use ID3 v2.3 date tags instead of ID3 v2.4"
or something even more accurate but similar, which will make this .ini file change for the user? A rollover could tooltip an explanation of the "double-date" issue and how this setting can resolve the issue.

[Peke]

Hi,
This can be easily Scripted into MMW and as it is not recommended/preferred to be used there is no direct option in MMW.

[ultracode]

Thanks, Peke (Pavle) -

What do you mean precisely when you say: "This can be easily Scripted into MMW"?

[ultracode]

Just again requesting a clarification from Peke (Pavle).