Thanks for the fast response, Tom. Correct, I do not want to cannibalize existing feature suggestions. However, I would still argue that there is still an overarching theme to my request regarding self-consistency. There are many things that work or don’t work depending on the type of library it is in or depending on the client, which is exacerbated when you see something work or have a workaround in one part of Plex but not in another.
Regarding the external extras not working, I saw that one of the most recent PMS updates had a bugfix specifically for this. I did update but I’m still experiencing difficulties getting them to play. I’m running 1.41.0.8994 on RHEL8 right now. I’ll have to research how to pull logs from the Plex app for the Amazon Firestick, which is where I last noticed the problem.
Regarding the extras not being available uniformly across all clients, the toughest one to cope with is the webpage not presenting extras in series. One would intuitively expect that the website on the machine hosting the database, the PMS service, and the content to actually have the most detailed, reliable, and visible representation of the content, but it doesn’t. Very odd. Whether working on the server or on another machine on the network, the webpage is the first point of testing to make sure something new got added right - it’s easy to forget that you can’t check extras for series that way. The bug where movie extras don’t work when multiple editions of the movie exist adds another dimension to the issue.
Regarding the “prefer local meta data” idea…I will try that. I’ll make a separate music library as a Plex Personal Media library and see how that fares. It won’t solve the problem of distinguishing different versions of the same album but it could potentially eliminate all of the Musicbrainz mismatches.
Regarding the {version-XYZ} feature, I’ve only seen this work in scenarios where we’re talking about a video might be on the server as both an MP4 and an MKV, which isn’t something I come across often.
- However, I do come across videos that get remastered. Let’s say I have “SeriesName S1E2 {version-Original}.mkv” and “SeriesName S1E2 {version-Remastered}.mkv”. A Series library won’t display both options like a Movies library will, regardless of the client. If you’re on a web client, you can click the “…” button, choose “Play Version”, and it’ll display a list of the version options, However, it doesn’t display the version names I provided, just some base stats about the videos - not much to go by.
- If we’re talking audio libraries, I’ve not seen the {version-XYZ} tag work at all. Maybe that’s because Musicbrainz can theoretically provide a superior distinction.
Regarding TV series cross-referencing, I mean something different. If I’m reading the post you linked to correctly, they’re asking for a way to weave several series and possibly movies into a cohesive watching sequence (either by release date or by the narrative’s own time order). Cool idea. I was looking for something simpler, something to alleviate users from delving into the world of hardlinks and recursive filesystem workarounds: Multi-series episode matching BUG Also, I thought TVDB was the preferred master for TV series and that TMDB was only meant for individual/non-series matching.
