Why can't Plex detect episodes of The Morning Show

DVR is a different beast because the EPG data does not match with theTVDB at times and it causes things to mess up. I know the DVR team are working on some things to help with that.

I’m just referring to the naming convention, in general. And, thankfully, I’ve not had any real issues using that convention yet.

I can’t really do that.
I don’t keep unmatched items around to test with - they are either matched naturally, fixed, or hand edited.
I add so much I can’t recall which work and which don’t work, but testing reveals the success rate is GREATLY improved by putting the (YEAR) field in ONLY when TVDB lists it as such and FileBot names those rascals perfectly every time.

I will try to make note of stubborn items and present them for perusal, but that’s about as much as I’m willing to do right now. I’m busy with new work-arounds. The old ones are working still.

The ā€˜newest’ work-around doesn’t have much to do with TVDB matching as it does with TVDB simply not having any data to fetch. Users, apparently aren’t exactly embracing the idea of sticking a picture of a Rodent in the spot where an actor image is supposed to go - so they aren’t falling in line to place the data as quickly as TVDB hoped.

Now the work-around is to add the data to The Movie Database - 'cause they have no such crazy rules laid down for our behavior – yet.

1 Like

well for one, the original post in this thread

  • the morning show (2019)
  • 911 lone star (2020) - linked above in my previous post
  • The Office (US) (2005) - I vaguely remember having problems with this one in the past, not sure if still applies

I think there is a similar/related issue with on demand subtitle search.

if the series has (year) in the file name but the ā€˜scene name’ does not, then no subtitles results.

2 Likes

That’s a big one - not named precisely how TVDB names it and… nothing. Stick a (YEAR) field in where it’s not required - nothing.

here is a post with specific example on subtitle search

I’ve always named/structured my files strictly according to Plex official specs. But for some time now I’ve been checking ahead of time to see how the databases name the show, or movie, itself. Things like if they append the year to a show (as with ā€˜The Americans (2013)’), or variations like ā€œandā€ vs ā€œ&ā€, movie alternative titles between countries (ā€œFord v Ferrariā€ vs ā€œLe Mans 66ā€), and so on.

I don’t know if these things are critical (I never can be bothered to run test cases - with the necessary Plex Dances - to see exactly what will and will not match properly) but having had my fair share of frustrations over the years with getting metadata, these relatively small efforts, to maximise the chances of a straightforward automatic match, are well worth it, IMHO.

1 Like

That is a sure fire way to cut down on mismatches. You are wise.

I am lazy.
I use Filebot that in milliseconds goes to TVDB/TMDB and gets the name they use - then uses that name.

:slight_smile:

I also know the TVDB ID# trick - and chances are I’ll be using it soon.

Haha, yeah, I’ve no doubt Filebot would pay dividends. Just I’m finding that first hurdle of committing to learning a new tool a bit of . . . well, a hurdle.

I heard that.

I recently had to leap that hurdle when I wanted to put the remaining 1500+ Movies into a unique folder of their own - to cut down wear and tear on storage by negating an unnecessary scan - I needn’t have worried tho… it was easy and Filebot and I completed the task the other day after about a month of doing 200 files at a time - when I had time - and Filebot made it easy.

I KNOW 'cause the first 1500+ I did by hand.

I MUCH prefer the Filebot assisted version.

hmm Office and The Morning show loaded fine for me with test files i just made. (i don’t have any of those shows so all completely new to my server)

For 911 Lone Star I needed to add the dashes between the numbers. In your other post in the other topic looks like you had an extra dash to replace the colon between the 1 and the L. not sure if that might have caused the issue there. Does seem to be a lot more strict than it used to be as far as punctuation/special characters but it does not seem like adding the year to file name that causes issue.

1 Like

While you’re at it - look for subtitles.

I will agree exact naming with punctuation as supplied, or simply omitted, does return a higher percentage of natural matches.

Judging TVDB right now can probably proceed normally - after recent difficulties that could skew results more sideways than normal.

I’m keeping an eye on it - will post results.

Subtitles I know are different beast. Opensubtitles is much more strict trying to match an exact file name if I recall which are all mostly named like scene releases. but I will have a look at that other thread @TeknoJunky mentioned and reply there when I find out more info on what is going on.

1 Like

Fair enough.

You asked for some case studies.
We’ll post the failures here.

as far as scanning the shows. for subtitles please use the other topic

1 Like

Here’s one:

I have directed it’s victim here.

Sorry I guess i needed to be more clear. You made the claim that adding the year in the file name causes the search to mess up sometimes. I asked for an example of that happening. I didn’t mean for this topic to be a dumping ground for every time fix match fails in some way.

I see.

I think a new topic containing match failures across the board needs to be at the top of the forum - until it gains some traction.

That way you guys can pick and choose what you want to work on.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.