I have gone through and updated most of my library using Picard. Now I am wanting to clean up the formats a bit. Everything to MP3 192k or lower if it already exists.
Looks like my files are getting thrown into the Unclustered folder again.
Is there a way to prevent this?
Using ffmpeg with:
Thanks Ivan.
That checkbox isnât ticked (I havenât touched it). Iâll do some more testing to see if I can track anything down.
Appreciate the idea and welcome anymore.
Yeah, that looks good - I think the only settings I changed was the naming convention / move files.
I can âmapâ this specific file again, save, reload it, and see if any of the data changes from what it is now.
EDIT: I should have looked at a good file first.
Those tags arenât right⌠(this screenshot is me having mapped it and it showing the Original vs New tags)
The values are correct but the tags themselves arenât in the âhuman readableâ format for lack of better words. There are a lot like this (ORIGINALDATE vs Original Release Date).
If you are format shifting then you need to remap some of those. FLAC has different tags to MP3, etc. There is a chart in the help files below. And the best expert is also in this thread.
I see whatâs happening. Picard has different tag names for different formats. When this got defined many years ago, the idea was to follow naming schemes that existing tags for each. So you get something like MUSICBRAINZ_ALBUMID in Vorbis/FLAC, TXXX:MusicBrainz Album Id in ID3, ----:com.apple.iTunes:MusicBrainz Album Id in MP4 etc.
Now when converting formats if the format support copying metadata at all it will often convert known properly (e.g. it will now about converting Vorbis ARTIST to ID3 TPE1), but all unknown / custom tags it will write to the target format as a freeform tag with the original name. So you end up with Vorbis MUSICBRAINZ_ALBUMID being written to ID3 TXXX:MUSICBRAINZ_ALBUMID.
What you could do in Picard is using a small script like this:
Add this as a new script in Options > Scripting. Load your files, they end up in the unmatched pane. Right click them and select âRun Scriptsâ > Your script name. This should update the tags to use the standard tags.
Then save the files (I would suggest to only enable âSave tagsâ, not move or rename), remove the files from Picard and load them again. If everything went fine they now should load into the proper releases and tracks.
The above script is for the relevant tags needed for automatically matching loaded files, but you can of course extend it to all other mapped MBID fields.
where $1 is the input file and $2 the output file and convert_metadata is a bash function that reads from stdin and writes to stdout the converted metadata. Maybe I will post the full script when I am done.
Adding another option and having two separate naming schemes does not seem to be less complicated. Especially as a lot of software supports the existing names.
Picard (and other software) need format specific mappings anyway because of the specific predefined tags for different formats.
Iâm maintaining my library in flac with Vorbis metadata. I transcode to mp3s. Adding the need to script the changes is the extra complexityâŚnot the software design part. I understand that, but itâs a different issue.
I don;t know the details of " TXXX:MusicBrainz Album Id in ID3". Canât the format handle uppercase? Is there really that much software that handles the MusicBrainz IDs? Couldnât we have upper case as well?
The program you use for encoding just needs to support translating the tags. FFmpeg doesnât but I just found out that fre:ac (freaccmd) does this correctly.