Force credit recognition

Sometimes it happens, that credits do not get recognized on some files for whatever reason.

For example the credits of episode 3 of a show get recognized correctly, while the next episode does not recognize credits at all, although the creditstyle is the same. When I let it reanalyze the episode it didn’t detect any credits, it appears to do nothing because it probably already scanned for it and sees no reason to do it again.

Therefore I would like a dedicated option to force recognize credits and/or the option to manually place and correct credit markers. Preferably the same goes for intro detection.

By setting the marker source to “Local only” and then manually running an Analyze on the episode will force the detection. See the support article on where this option is: https://support.plex.tv/articles/credits-detection/#toc-3

If it’s still failing then there is something else going wrong and I would need to see the server logs.

Unfortunately it did not help. I checked the xml file for credits on one episode, saw it hadn’t any, switched to “local detection only” and reanalyzed it. It appeared to do nothing and rechecked the xml file.

Plex Media Server Logs_2023-02-21_11-29-26.zip (2.8 MB)

There will be an new beta version in the next day or two, try again when that releases as it fixes a few cases where detection wasn’t running correctly.

1 Like

Related question … when a new server version is released (as was today), does the server go back and fix credit markers that may have been missed or identified incorrectly?

1 Like

Version 1.31.1.6733 did not help with my problem. I did the same procedure I described before.

Plex Media Server Logs_2023-02-21_19-42-12.zip (2.2 MB)

Version 1.31.2.6739 did not help with my problem.

Plex Media Server Logs_2023-02-28_15-32-00.zip (905.1 KB)

Try a Plex Dance on the offending file. It’s just one episode in one show you are looking at for this, right? Shouldn’t be too much trouble to dance the one file.

If it still fails to find credits, then the logic must hate the visuals (the logic doesn’t find anything). It’d be worth looking into to see if anyone else has the same issue.

It happens with episodes and movies. I did the following procedure with a movie for example and got a very weird result

  1. Looked in xml file for the credit tag on the movie “Emily”. There was none
  2. Did the Plex Dance on the named movie
  3. Did a manual Analyze on the movie, which was very quick and usually takes a couple of minutes to scan for credits on my server (although “local detection only” is active)
  4. Looked for a credit tag in the xml file and found a credit tag
  5. Started the movie and skipped to credits, but there was no option to skip the credits

Plex Media Server Logs_2023-02-28_17-29-42.zip (865.2 KB)

Update: It exclusively happens with items that have multiple files with different runtime, because one version has a different framerate or other intros, although some of them still have credit tags.

Ah, it happens when you use “versions”? Interesting. I don’t have any clue how Plex handles that, as I don’t think Plex has separate XMLs for each version.

By versions, I mean exact same content, but different framerate or different intros, which differ from region to region. Not different cuts, editions or whatever.

Yeah, that is “versions”. “Editions” is like the extended Snyder-cut version of the Justice League movie, or the black and white one.

I think Plex has more support for multiple XMLs for “editions” than it does “versions”. I guess “versions” are supposed to be the exact same file with the exact same length, so any variation in length (with cut-out intros, or cut-out Netflix dub credits) can cause havoc with credit skip markers.

So it’s a more complex problem than I though, because I have a lot of items with different “versions”. For example, one file for 4k HDR one file for 1080p only. It wouldn’t be a solution for me to use the Edition feature, because I would have too many duplicates.

Wait for confirmation from a dev before taking anything I say as truth. I am not a developer, but looking at the UI it seems like items only have one XML per entry. I’m simply taking your statement that items with multiple “versions” have issues and making assumptions. I could be wildly wrong.

I investigated a little more. Like I said, only items that have multiple files with different runtime don’t get scanned at all. But sometimes it happens, that those items still get credit markers. Those items with different runtime and a credit marker don’t have the option to skip credits, though. Items with multiple files, but the same runtime, don’t have any problems as far as I can tell.

Is there an update or can someone confirm my theory?

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