Support Musicbrainz IDs in .plexmatch files for audio

Summary
Updating a large audio library could easily be a non-starter, either due to the time it would take to carefully match everything with Musicbrainz IDs or due to the risks involved with using quickie tools like Musicbrainz Picard. Plex and Plexamp could be great at music playback but the effort to get there isn’t worth it, presently.

What if there was a more efficient approach?
Instead of manually updating 10’s or 100’s of thousands of files across several or many terabytes of data, why not extend an existing Plex capability to knock the work effort down to a fraction of the time with comparatively little file I/O?

Support Musicbrainz IDs in .plexmatch files
Instead of modifying individual tracks, a .plexmatch file could simply be added to each album or album/disc# folder. All you need need inside of the .plexmatch file is the specific album release ID and the disc index. The artist, release group, and technical data are all implicitly known at that point. All that’s left for the Plex agent is to match the very limited number of files to the track IDs belonging to one release ID, which should be super easy since everyone’s tags are already meticulously perfect, right? Right. The amount of work it would take to capture those two Musicbrainz tags for every album or disc is trivial compared to current options.

Background
I’ve been building my digital audio library for almost 30 years now. My library is a respectable 4TB and growing. Like most anyone I see discussing audio library management, my tagging is thorough and meticulous and is organized to meet my preferences and use cases. I bought into Plex for its video library features and simply gave it read access to my audio library, not thinking much about it.

…until recently. I’ve now observed albums that are missing, mis-categorized, over-consolidated, and mis-identified. “Prefer local metadata” does not help. Additionally, I catch Plexamp’s Library Radio repeating songs quite often, which shouldn’t even be possible with >4TB of music and a good random seed. Mind you, this is all with good tagging in place.

I since discovered that Plex relies heavily on Musicbrainz for audio identification. Great! Presumably, 99% of the issues mentioned above would simply vanish if every track was perfectly updated with the correct Musicbrainz IDs.

That sort of undertaking is probably measured in decades. Seriously. MP3Tag could do it but at a rate of one disc at a time, if I want to do it right by measuring twice cutting once, it’ll take decades. Musicbrainz Picard is far too aggressive and would destroy all of the meticulous work I’ve already put into the archive. It’s not an option. I felt sorry for my test file copies after seeing what that thing did to them. :face_vomiting: If you’ve got a Napster-era thing going on in terms of tagging quality, sure, maybe that’s the right tool. I could write something to work specifically with my archive and all its nuances but that would still probably take a couple of years to build, and it would only help me. What about everyone else?

Forum thread reference that got me here:

Update.

Nevermind. Just, nevermind. It doesn’t matter. Even if .plexmatch files were supported, it wouldn’t help.

Though I’ve not yet embarked on trying to append matching Musicbrainz ID tags to all of my music archive, I have been taking the additional step of adding Musicbrainz ID tags to all new rips over the last few months. Musicbrainz is vastly disappointing. Maybe 1 out of every 5 things I rip has a match. If I could stand to be sloppy about it, maybe 3 out of every 5 things has a different Release in the Release Group that’s functionally a match, at least in terms of track content. I’m spending 10~50x more time adding new Releases to Musicbrainz than I am just ripping discs.

Unless you’re also going to align with a bigger database, like Discogs, and match against both, local ID3 metadata is the only way to go, and the only way that’ll ever work right is if multiple versions of the same album aren’t auto-consolidated. Master/remaster year, format, resolution, etc. would all need to be distinguishing factors.

Viva la FooBar. Or any other direct-file playback program. Sorry, Plex.

+1

This is absolutely needed, unless there is a way to provide hints for music matching. .plexhint file support should be added to every library type.

Another possibility would be to allow the .plexhint information in tags.

More than 90% of my music is matched automatically and it would be great if I could just manually fix the albums that aren’t matched such that if the albums are ever added again to a new different library, they will be matched effortlessly.

You can include the MUSICBRAINZ_ALBUMID tag in the metadata: https://picard-docs.musicbrainz.org/en/appendices/tag_mapping.html#id23

Tried it, doesn’t seem to work and I completely removed the album, emptied trash, and then added the album back. Will try again.

Also, if this is a “thing”, could it be added to the docs?

Yes, adding a MUSICBRAINZ_ALBUMID tag to each audio file works so long as Musicbrainz has a good definition for the album (lol…don’t get me started on how MB can’t cope with DVD and Blu-rays that contain more than just a simple album) and that you also have your audio files stored in the same manner as the definition of the Release in MB.

But this is the problem: correctly updating 10s or 100s of thousands of audio files with this one hint of a tag requires a superhuman effort. It would be a lot easier if .plexmatch files could be utilized instead: no editing of ID3 tags and the folder count is usually about 1/10 to 1/20 the file count. If you only had to focus on the albums that Plex+Musicbrainz gets wrong, it becomes a tangible effort.

To my knowledge, this feature still isn’t available. This thread represents a feature request.

I will try again, I added the correct MUSICBRAINZ_ALBUMID to all files in the album as an “Extended Tag” in mp3tag. I will try again, but it didn’t work and I wonder if it only works for the first scan of a new library.

Both tags and plexmatch files should work on all library types.

I used the MUSICBRAINZ_ALBUMID with the associated “release” MBID and the album was not matched even when being added to a brand new library.

I tried two different albums, a stereo M4A AAC-HE and a multi-channel M4A EAC3 and added the tags via mp3tag.

Edit: It seems to be working if I uncheck ‘Prefer local metadata"‘ and then ‘Refresh Metadata’. Why can’t local metadata be preferred and MUSICBRAINZ_ALBUMID still be used to auto match?

Ok, good, I’m glad you figured it out.

Indeed, Prefer Local Data doesn’t work the way I’d want it to, either. It seems to be an all-or-nothing approach to cataloguing the library. If enabled, no MB referencing is used, and even with complete tags it still somehow misses or confuses things. It’d be nice if Plex would use MB as a backup when the locsl data confuses it.

Update, I am not sure if this is working because m4a albums with MUSICBRAINZ_ALBUMID are not being automatically matched upon a metadata refresh.

I hope this gets working at some point and now I think .plexmatch files are better because it seems easier/better.