When I record Hooten and the Lady it records and names fine, but since TVDB calls it Hooten & the Lady, it doesn’t match. If I manually fix after the show is recorded it works. Can the server be updated to consider “&” and “and” the same thing?
Odd, I record that as well and haven’t had a problem.
I wonder what the difference is that is causing the problem. I don’t even want to think about trying to decipher the “Agents” UI in Settings.
Ah, yes, but see #3? You’ve got a mismatch. Episode 3 should have a real episode image. If you did a fix mismatch it would rename to Hooten & the Lady, and you’d get the actual Episode 3 image. Of course, then it would continue to mismatch for future recordings. So, you wouldn’t want to try the fix mismatch if the episode images don’t bother you. 
Yea, I don’t really pay attention to the Episode Images if the Show and Season posters are correct. I tried out your theory and changed the “and” to “&”, refreshed metadata and had no difference. I noticed that the ‘Episode Image’ on all three episodes are different on my Plex vs theTVDB. If I check Season 3 of iZombie for comparison, my Plex has the Episode Images from theTVDB. Nice catch. I wonder if you could edit the TVDB to make it work.
The problem with adjustments to matching algorithms is that you may fix the problem for one show but end up with issues for others possibly resulting in wrong show getting a higher score - and I presume if both have same score then that could be an issue. I always worry about asking the developers to make changes like this - but I will suggest it
Understand. Thank you for passing it along.
Actually it is either already allowed for (for the next release) or it is not just the & and and issue
Just tried with dummy files.
See file names and folder name
and the Plex Media Server library
Ok, thanks. I did the Plex Dance added an extra sample file and it worked. Maybe it was just the Plex Dance that I needed. I’ll know for sure if the problem is definitely gone when I record Hooten & the Lady on Monday.
I got a mismatch again tonight after Hooten & the Lady finished recording. Seems like it has to do with the DVR rather than the matching.
Full logs zip please covering time when this happens
I think I waited too long for all the logs, but here’s the Server log with the details after the recording completed on 7/31 at 10 PM. I can send full logs the next time it happens.
@mbarylski said:
I think I waited too long for all the logs, but here’s the Server log with the details after the recording completed on 7/31 at 10 PM. I can send full logs the next time it happens.
sorry can’t help
- Debug Logging is disabled
- In addition need all the PMS Plugin Logs as well
Ok, I’ll zip up everything on Monday after the next airing of the show.
@mbarylski said:
Ok, I’ll zip up everything on Monday after the next airing of the show.
but you need to enable debug logging on the server
Settings / Server / general / show advanced
enable debug logging
save changes
restart the server to get new logs created
Yep, got it. Thanks.
Ok, same thing happened tonight after the recording finished at 10 PM. Attached is the entire Log folder.
@mbarylski said:
Ok, same thing happened tonight after the recording finished at 10 PM. Attached is the entire Log folder.
Thank you. I will refer the evidence to the development team
The evidence has been passed. The problem was not because of the and and & although it played a part - the issue is to do with the matching being done using the wrong year. Hence when you refresh the metadata it corrects itself - not sure if you need the Plex Dance or whether a refresh corrects anyway
Ah, ok, thanks for tracking down the reason. Appreciate the follow up. Luckily I don’t need to do the Plex Dance to get it to manually correct it. The “Fix Mismatch” function works, but it’s manual of course. How long does a fix like this typically take to make it into a public release?
@mbarylski said:
Ah, ok, thanks for tracking down the reason. Appreciate the follow up. Luckily I don’t need to do the Plex Dance to get it to manually correct it. The “Fix Mismatch” function works, but it’s manual of course. How long does a fix like this typically take to make it into a public release?
I do not have any such information
