I also still don't understand why MusicBee is using the NULL value for 2.3 creating duplicate/multi-tags on save since any player that requires 2.3 cannot read multi-tags, and who knows how it will "break" the players reading ability due to that.That has been explained to you, but you choose not to accept the explanation, and keep complaining about it both here, and on other fora, misrepresenting what has been discussed here, and discrediting MusicBee and its users and developer.
I've had to work with the Picard people to figure out how to use "Scripts" for the force creation of Multi-tags,You had to 'Work with'
You mean that they also had to explain and help you with things you didn't understand yet.
I find it problematic that every time you don't understand something, or don't agree with something, you create a 'bug report'.
While they are actually mostly matters that you don't have a full understanding of, or are a repetition of you complaining about how MusicBee decided on doing things that you personally don't agree with.
It is good practice for any bug report to be to the point, raising a specific reproducible issue that actually breaks functionality.
Please try to understand, respect and stick to such good practice.
'Bugs' is for actual bugs.
'Questions' is for things that you don't understand, can't figure out and need help with.
'Complaints' is not available at this moment. But perhaps your input to this forum justifies considering it to be raised.
I'm not interested in your personal attacks and misrepresentations...
Move along... I'm here reporting actual issues. You're here just causing problems.
I understand perfectly well how the NULL tag works, you however don't comprehend that it's NOT supported by 2.3, and ANY player that requires it also DOES NOT support it, as well NO OTHER Tag Editor creates multi-tags except some do when using 2.4, but ZERO do when using ID3 2.3.
Anyway, I've explained everything, and you make it personal as if my reporting a problem means I have something against MusicBee and the Developer. Stop LYING.I've now reported TWO bugs with MusicBee's functionality in this thread
... so, I don't need your "lecture".1.
MusicBee Creating duplicate YEAR tags on save is not a "feature" (there is no multi-tag purpose for the YEAR tag).2.
and neither is MusicBee's Editor not displaying the "Original Year" tag under the Tags (2) Tab in MusicBee's Editor, when those values ARE within my music files.
(Note to the DEV if you read this... The zipped files I sent you (or above) will also show this last issue that's NEW that I've discovered.)
So, stop causing problems... You living in happy laa laa land with no problems doesn't mean there aren't problems. Neither does it mean I'm "attacking" MusicBee or its developer. I'm reporting problems, PERIOD, problems which wouldn't exist as I've said before had MusicBee not been using the NULL (multi-tag) save for 2.3 when it's NOT supported by 2.3. Again, Picard doesn't do it, and Mp3tag doesn't do it, Mp3tag doesn't even do it on 2.4... Mp3tag saves whatever Separator people have chosen to use, instead of "forcing" NULL on them. So don't tell me "I'm" the problem... I work with these 3 programs, I'm reporting actual problems and compatibility/consistency issues.
One other thing, the other thread that brought this issue out, the Original Poster of it, he's been working with digital music files for 20 years, but you all abused both of us as if we were ignorant. We aren't, but you are... Because you can't claim to be "following the standard" when what you're doing is NOT the "standard" for 2.3. No player that requires 2.3 reads multi-tags, and thus anyone using ID3 2.3 would not WANT multi-tags, thus MusicBee NOT following the actual Standards, is not "me/us" being the ignorant... If we were, then other Editors, the actual EXPERTS in Tag Editing would do the same, but NONE do so.
MusicBee is the ONLY exception of the some 12 editors and programs I've been trying. So, I don't need you telling me what I do and don't "understand".... I know what I do and don't know, and you couldn't be more wrong, because the actual experts in tagging DON'T agree with you, I know because I've talked with them both openly and in PM, as well have used their programs, and if they agreed, they would be doing the same as MusicBee, but they don't. Mp3tag, which is considered the gold standard of tag editors doesn't even force Null Save for 2.4.
So, what does that tell you? You've been engaging in nothing but ideologue protectionism, as if any criticism of MusicBee means we don't appreciate MusicBee and the Developer. Well, it's NOT true... Reporting problems, wanting them to be be respected and understood, and then wishing for them to be fixed is not "us" being the problem. But you are in your personal attacks, contributing nothing to helping to fix the issues.
Not a single person at Mp3tag or Picard in which I've posted MANY issues, as well as questions, FAR FAR MORE than I've done so here, have they engaged in personal attacks, made issues personal, as if I'm attacking MusicBee and it's developer etc. They've listened, explained how I can fix issues or problems I'm having, they've taken feedback to fix issues I've found, including me creating TICKETS in their Bug systems, etc. So, what is YOUR problem?