And what about implementation of 2.4 UTF-8 ?
I also have a bug on ID3v2, since I use TagScanner to edit tags, it saves in 2.3 unicode or 2.3 AINSI. But I have the probleme with both. The probleme is that the popularimeter tag & picture tag mix up. If I resave it, ID3v2 tag corrupts & information deletes. I both use TagScanner & MC for years and have the probleme only if I try to put cover art into the tag. Here's the step to reproduce.
- 1. In MC rate the MP3 more than 1 star (Be sure it save in the tag in options).
- 2. Edit tag of an MP3 with TagScanner & save a picture in it. Save
- 3. In MC Auto-Import to get external change (First bug the rating goes to 1 star in MC).
- 4. In MC reset the rating to more than 1 star. (Second bug the picture inside tag goes away)
- 5. In TagScanner you can see that pictures gone but file size didn't change. (probably still inside but unreadable).
- 6. In TagScanner do not edit tag and just save it. (Third bug all the tag disappear).
Since the picture is dhowing correctly in MC after save & every other data written by TagScanner is correct I would say the it'S MC the problem. but since the popularimeter is not implemented in TagScanner, it'S maybe the fact that if it'S their TagScanner screw up things & if not everything works. Both program are closed source so just letting you know to verify. I've send an e-mail to the author of TagScanner.
I'm also wondering if MC will support array of pictures (front cover, back cover,...) array of genres, artists,... As much as I know multi info in MC is kept as single string separated by comma.
Please stop using comment frame to keep intensity when analysing. Would be great to be able to deselect that functionality when analysing. You could instead use Private frames or something less commonly used.
Keep up good work!