AIMP Forum

AIMP for PC => Вопросы / Questions => Topic started by: Orator on March 25, 2025, 11:54:03

Title: AIMP ID3v2 tag compatibilty with older or other revisions of the tag?
Post by: Orator on March 25, 2025, 11:54:03
I use AIMP today mostly for listening, but I also use Mediamonkey 4 to quite extent due to it's superior database and file management capabilities and I've noticed that the ID3v2 tags aren't entirely compatible between these two programs anymore, like they've been in the past, what I believe.

This has been going for quite a while already, but would it be possible to have some kind of legacy mode added to the tag handling so that files that have been rated or tags in general managed with older software would be as compatible as possible with the latest AIMP revision too (from here to the future)?

Also another compatibility issue that makes life hard switching between MM4 and and AIMP is that MM4 uses semicolon ; as a separator for multiple entries within one field, but AIMP isn't compliant with that using forward slash instead, which conflicts with MM4, so I can't use AIMP to edit tags effectively.

I have a fairly large library of (mostly) MP3s from long time in the past that I'll keep managing with MM4 as long as there's an older Windows compatibility option available for the latest Windows revision, but I'd also hope that AIMP could be compliant with MM4 tagging, particularly user rating and separator character wise.

Please consider looking into this, if that's not too much to ask. It would be great to be able to keep using both programs side by side, they both have their strengths and weaknesses, but I simply can't afford to loose MM4s overall convenience in music files management, that's for sure.

What makes AIMP stand out for me as a player is the ease of quickly pre-listening the songs due to the waveform display, which helps browsing the songs by structure or 'where it happen' and that has made me favor AIMP over the other players, plus there are enough features that help managing the playlists. :D
Title: Re: AIMP ID3v2 tag compatibilty with older or other revisions of the tag?
Post by: Artem on March 25, 2025, 12:35:36
This has been going for quite a while already, but would it be possible to have some kind of legacy mode added to the tag handling so that files that have been rated or tags in general managed with older software would be as compatible as possible with the latest AIMP revision too (from here to the future)?

AIMP stores the rating according ID3v2 standard.

Also another compatibility issue that makes life hard switching between MM4 and and AIMP is that MM4 uses semicolon ; as a separator for multiple entries within one field, but AIMP isn't compliant with that using forward slash instead, which conflicts with MM4, so I can't use AIMP to edit tags effectively.

AIMP uses native values separator that depended from tag format. For example:
ID3v2.x: separator is '/'
ID3v2.4: separator is #0
Vorbis: has no separator, each value stored in separate paired-value.

So, this is MediaMonkey's issue.
Title: Re: AIMP ID3v2 tag compatibilty with older or other revisions of the tag?
Post by: Orator on March 25, 2025, 13:22:20
Alright I see, thank you for clarification. Too bad, if only there was an MM4 compatibility plugin or something, but have no programming skills myself whatsoever. I haven't upgraded to MM5 and see if it had become compliant with ID3v2 standards, since I didn't like changes in some UI features and MM4 still works well enough in compatibility mode.
Title: Re: AIMP ID3v2 tag compatibilty with older or other revisions of the tag?
Post by: Artem on March 25, 2025, 14:14:50
Alright I see, thank you for clarification. Too bad, if only there was an MM4 compatibility plugin or something, but have no programming skills myself whatsoever. I haven't upgraded to MM5 and see if it had become compliant with ID3v2 standards, since I didn't like changes in some UI features and MM4 still works well enough in compatibility mode.

Have you contact with MM4 support? What they say about that? I've checked my code and it seems there no any bugs - all fields written according ID3v2.3 standard