If you look back in many discussions here it is surprisingly to see that this release is lead to achieve more compliance with other programs instead of more compliance with specifications. However, very senseful to to be compliant with the "real" and de-facto standard. Good decision.

whilst this is a good idea for new installs, i didn't like the way my setting was changed from 2.4 to 2.3 automatically when upgrading. i hope this won't happen with all future updates.

This was introduced with the assumption that average users don't really know or care what the differences between these ID3v2 revisions are. If you have good reasons to use ID3v2.4, I'd like to hear them.

The ID3v2 tagging changes are at least interesting. If the new system works fine it'll save me from doing the additional step of changing the format to 2.3 with Mp3tag (in my experience the old compatibility mode didn't maintain all externally tagged tags correctly).

I am not so sure if I like the Replay Gain scanner change. I have been quite happy with the old implementation during the last few years. I did some limited testing with the R128 component over a month ago and I noticed some differences in the results that were not exactly to my liking, but I did not have time to further investigate the issue and take part in the discussions. I did not expect it to replace the old implementation.

While I understand that compatibility is important, I'm sad to see that classical music is being ignored completely by the change to using TPE2 for the ALBUM ARTIST. It was already ignored by other vendors, now foobar can be added to that list. Where am I expected to store the orchestra now?I realize it's a problem for the other vendors to fix, but that won't happen. Using foobar as the ideal tagging application has now been made history because all classical music will now be listed under the orchestra instead of the composer on audio devices. Luckily this can at least be fixed manually for foobar but still...

Does the AC/DC workaround only work for AC/DC or any artist or tag with a / in? I have quite a few other artists and albums with slashes.

QUOTE (Prodoc @ Mar 20 2011, 14:16)

Where am I expected to store the orchestra now?

I use %performer% - I don't know what frame that lives in. I put %composer%; %conductor%; %performer% in %album artist%, if %performer% is multi-valued then I just put it as a comma separated list in %album artist%. Oh and %artist% = %composer% for compatibility with last.fm. I know I'm not following the ID3 standard but it works for me.

Does the AC/DC workaround only work for AC/DC or any artist or tag with a / in? I have quite a few other artists and albums with slashes.

...such as?

Slash

OK, seriously now. Creating a workaround for one particular artist here really sounds like a weird idea, because obviously there will be more artists with a "/" sign in their names, even if you can't recall any.

Actually, those who wrote the ID3v2.3 spec said exactly that!But yeah, a single-instance workaround isn’t a good idea, IMHO. Although it will relieve shakey_snake of the responsibility of having to paste that long list of topics written by confused AC/DC fans

Overall, I can see why such changes were implemented, but they wouldn’t be necessary if the ID3v2 standards and various implementations thereof weren’t so discrepant. In a way, it’s laudable that the developers tried to adhere to the standards for so long, but perhaps it just didn’t seem worth it any more.

Peter is planning on removing the AC/DC workaround and instead write different character in place of /. I'm against the change and have suggested him to not treat / as multivalue separator in ID3v2.3 artist field at all and allow it as is. Is anyone against that suggestion?