You can use this to protect any tag that you don't want changed, including replay gain tags and MB custom tags. To solve the problem of incompatibility with Mp3Tag it is sufficient to make a passage through the save with another tagger that does not have the problem. One thing that is super important in using Picard and MB together is the 'preserve these tags from being cleared or overwritten with MusicBrainz data' field. :-)įinally I was able to do some quiet trials and I can confirm what was said by Jacko.

I'm not a Python expert but maybe you, with a bunch of minutes. There's a '002_WARNINGS' tag that, in my opinion, it's a wrong tag and it has anytime the value 'No works for this track'. The same appears with the tag 'MUSICBRAINZ ALBUM ID', the right name is 'MUSICBRAINZ_ALBUMID'.Īgain, there's no 'PUBLISHER' tag but 'LABEL' is the right one. But I expect to have a 'RELEASETYPE' tag, cause normally (with FLAC files) Picard write a 'RELEASETYPE' tag, not the 'MUSIC BRAINZ ALBUM TYPE'. Ther's a tag 'MUSIC BRAINZ ALBUM TYPE' with an 'album' string wrote by the plugin. I noted that, even if the above error is resolved, many specific Musicbrainz tags don't appear in MP3Tag where I normally expect to see them. Many specific Musicbrainz tags have a wrong name. I don't know this particular tag but this is the origin of the '(!BAD ID3v2)' error if you remove this tag all the others come to life in MP3Tag.Ģ. There's a 'COMMENT WORKPARTS_OPTIONS' tag (containing a lot of text) on every Picard saved DSF file. Tag 'COMMENT WORKPARTS_OPTIONS' not valid Then I used TagScanner to investigate and I think I've found the reasons of the problem.ġ. I reinstalled Picard (maybe my installation was broken for some reason) and I confirm what you found in your last test. Which media player/streaming server do you use? Have you tried the Picard tagged files with that? I previously used LMS and as I recall the tags could be read fine (that would have been on the original plugin and a much older Picard version). So there is at least some incompatibility with Mp3tag. Loading the same file in another tagging programme (Kid3) I can see the correct Picard tags (see screenshot attached). However, if I try and read the file in Mp3tag then there is a warning '(!BAD ID3V2)'. Picard knows which release it is from without me having to 'Lookup in Browser' and the 'Original Value' tag fields are fully populated. Then 'remove' the release and load the file again.

First I tag a file using 'Lookup in Browser', then drag the file to the right position, then save. For me Picard is definitely writing tags. Just tested myself with Picard 1.4.2 and the plugin from the link above.

Musicbrainz picard could not load album