Ok, and yes, that is the initial post and query which opened up the looking that resulted in the rest.
I spend a good deal of time making sure tags are correct and proper… that is just me though. So when something alters tags in a way that is unexpected or unknown to me, that is a major problem… but a minor problem in the scope from your side, I agree.
This is just my view, and I can understand yours. If I wanted to write TSOP headers and they are not available in 2.4, then I use 2.3. And if I set a software to write 2.3 or 2.4 tags, I expect the result to be 2.3 or 2.4 tags, respectively… unless there is some indicator of deviation or overriding options that I have set. Deviating creates a hybrid standard that requires others to follow suit or segregation lines are created (ie… Apple and the rest of the world).
I see your point, but personally differ. You are never less compatible by sticking to the standards. I think what you are meaning (don’t mean to speak for you) is that you are unable to use the “enhanced” functionality that others use without making the same deviations they have. To that I agree. I see this a lot with MS Word, Adobe InDesign, etc on a business level.
Yep, just making sure and making sure it is clear, the software product and not the music product…
…made by Apple, to be non-compliant with standards. This should be expected as it is Apple, and their entire business model centers on incompatibility with others.
So it is clear, I do see your points and am only sharing my views on it as appropriate. I understand (I think) that the tag version crossing issue was/is centered on iTunes. If I may speak of opinion…no intent on debating anything but just explaining my view on this so it is understood vs seen as just arguing or complaining at nothing.
I see this as the users problem. If you use an Apple product, you made that choice… the choice to use a product(s) from a company that intentionally defies standards and causes difficulty in the marketplace for many. So if you opt to be an Apple user, it is on you to make changes to conform when sharing with others, not mine or other non users. I mean not to offend Apple users.
This issue is existent in many places… Microsoft Office, Adobe Creative Suite, programming for internet use, file systems, character sets, audio file containers and formats, etc. But in all those cases, there is a simple solution for compatibility… sticking to the standards and avoiding the proprietary and other forms of product specific enhancements.
I think the issue of the improper tag writing is “solved” as it relates to the 2.3/2.4 portion. I appreciate your explanation and have provided mine… and I cannot really say that either of us is more right or wrong than the other.
A side question… I reviewed the Picard mappings (https://picard.musicbrainz.org/docs/mappings/). When you state “iTunes MP4”, are you meaning/implying QTFF? I assume this, but QTFF and MP4 are different standards, but very closely related… and if I recall the MP4 standard was based on QTFF. The other option would be you are combining the QTFF and MP4 into the same, similar to how ID3 v2.3 and v2.4 are combined as ID3v2 and noted where different. Note that I do understand the common misconception is that the mp4 is an Apple format.