What does this message I get upon scanning for credits with the new function?
CreditsDetectionManager] Mis-matching media items detected, skipping
The metadata item has multiple media versions that aren’t all the same durations.
Check the xml info for the item and inspect the durations for the listed media items.
Well yes, thats true for quite some of my media items (mostly due to SD 25fps vs HD 23.976fps).
Does that mean credits detection won’t work on that items? That would be very unfortunate. Why is that the case?
We only store a single marker for the metadata item, if the timestamps differ depending on which media is played then the marker will not be correct if you play a different media.
How much difference is there in the durations of the two files?
curious about this…
If I have a 720p version with x264 video, and a 1080p version with x265 video, does/will the server only do the analysis once? In my case, they would both be from the same blu-ray source, with the 720p version having a stereo audio track, the other version the original soundtrack. The credits detection should be exactly the same.
Hmm, that would explain some offset I noticed with the intro markers (it seems there you are NOT checking for mismatching duration).
In most cases about 4% because its due to PAL-Speedup
Correct. Lessons learned from that. It is something we’ll implement for intros too when we’re happy it works well for credits.
Right now we only store a single marker and having an difference like that could cause potential issues, mainly if the marker offset value is larger than the duration of the video that might cause problems for the apps.
A way around this case for movies right now would be to use editions instead, that’s not supported for TV currently though. That way they could both have their own separate markers.
As long as the durations are identical (well within 1s of each other) then you won’t have problems.
1 Like
I’d say this is exactly correct. From my Bluray I always get the 1080p or 4K video that I need. The smaller versions are then a result of getting Plex to Optimize that media so they are essentially the same video and I’ve noticed that I have credits detection working fine for that.
I must say I was pleasantly surprised when I saw the “Skip Credits” button since I hadn’t seen the forum announcement that the feature is now generally available and I didn’t even know my server updated. Right now I’m literally watching something just so that I can skip credits at the end.
Oh! I’m glad I found this thread. As I have some TV shows with different versions coming from different sources (e.g., DVD, Blu-ray, etc.), this explains why some of them don’t generate credits markers at all. I was wondering why that was happening.
That said, it would be so amazing if TV show libraries were supporting the editions feature. It would solve a lot of problems.
I think, best solution would be supporting intro and credits markers on a file basis instead per media item.
I wonder why they decided to attach it to the media item in the first place, because they obviously use a FILE hash to store and share the markers in the cloud.
Yeah this seems like the best way to go.
Also, from the logs, how can I tell which items in my library are triggering this message?
Sorry for asking about that thing again.
I just upgraded some media items with a higer resolution and the credits detection did not seem to update the marker position, despite at least some of them are having a different length now and so I guess the position is not right anymore?
Is that expected behaviour? I come to the conclusion, that attaching those markers (intro and credits) to the media item instead of the media file is such a bad idea for so many reasons?
Why did you decide that way? Are there plans to change that?
How would I be able to reanalyze the credits marker? I will not Plex Dance all those items for sure…
There is any way to “list” all media with multiple versions so we can “fix” it?
Yes, you can filter by duplicates. But at least for me, having multiple versions of my media is intended.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
