Tag Conflicts

[ddjksa]

(31-08-2018 11:09)simoncn Wrote:  MinimServer doesn't have any size limit on path names and I don't know why you see more warnings on subsequent restarts.

Thanks for uploading the "rogue" file. It contains two ID3v2.3 tags and MinimServer is reading both of these and merging the contents. The Album value in the second tag is different from the Album value in the first tag and this is why you are getting the conflict message.

Note: In ID3v2, the "tag" is a complete block of tagged information. Each value in the tag (Artist, Album, etc.) is a "frame".

The ID3v2.4 spec explicitly supports multiple tags with or without merged contents. There is no mention of this in the ID3v2.3 spec and I haven't been able to confirm whether or not it is valid to have multiple ID3v2.3 tags.

Mp3tag shows information from the first ID3v2.3 tag only and it seems that many other tagging programs do the same. I have found a program (see this page) that can show the contents of multiple ID3v2.3 tags and delete all ID3v2.3 tags after the first. It does work but it isn't very easy to use and it reports problems that aren't really problems. For example, it says that your file has a image that can't be loaded but MinimServer is able to read the image correctly.

@paultaylor: How does Jaikoz handle multiple ID3v2.3 tags?

Thanks for the info Simon. I'll check out the suggested program and see if it helps. Very frustrating that the vast majority of tagging software (certainly the ones I use like TagScanner, Tag&Rename, MP3Tag and even MusicBrainz Picard) have no option to show if there are multiple tag values for the same field. I assume, unlike my DATE truncation errors which your previous post helped with enormously, there's no similar "cheat" to fool the log in to not reporting them? It's not a biggie as I say because the files play fine and your Intelligent Browsing is superb.

DDJ