Server Version#: 1.31.0.6654
Credtis detection is failing on all my files with Dolby Vision.
More precisely I have 4K DV and 1080p SDR files of those media items, but credits detection always tries using the 4K DV (instead of the 1080p SDR, which would be more suitable in many ways I assume).
Credtis detection is tried again on those files every mantainance window over and over, but is never succeeding.
Me too, although it’s not every dolby vision file, only some. It’s really annoying that it keeps trying over and over to detect and never succeeding.
This might have more to do with having multiple versions than it does being DV
No thats a different issue with multiple files of different lenght.
Multiple versions with same length detect credits fine if they are e.g. 4K HDR10 and 1080p SDR.
But they don’t if one file has DV (at least thats what I’m seeing).
Ok, it now seems to have managed most of the files, but there are currently 4 movies left, where credit detection is happening over and over again without a result.
Duration of the detection process is about HALF AN HOUR each.
EDIT: I stand corrected. There are many (DV) movies still not detected, but it seems Plex never even tries them now, because it repeats the same files over and over again each scheduled tasks window.
Is there a process to filter movies without credits marker ALL AT ONCE?
I have the same issue with multiple files that are for sure not Dolby Vision because they’re downloaded from YouTube.
I have now disabled credit detection altogether because trying and failing and repeating the process all over again is just a waste of electricity, because it does put a very high load on my NAS.
I am honestly a bit disappointed here. I would have expected better error handling on this feature that has proven to be so problematic that is requires multiple patches.
For the future with such issues, I’d like to ask the Plex devs not to enable the feature by default, do so only after all the bugs have been ironed out, or have better error handling that just skips files if they can’t be processed after several attempts on a Plex version.
This nightly repeated waste of electricity honestly really gets to me. Not from an actual money standpoint, but just because it’s such a waste that could probably have been avoided with a couple days’ work from a developer on error handling.
I did the same, I turned off the credits detection altogether. It’s not working for me (DS220+ Synology NAS).
I always get the same generic error:
ERROR - BufferingLineReader: failed to read line (error: -1)
that in itself means nothing: it lacks details.
I reported this initially in the alpha tests and it has not been solved yet even with the latest PMS beta version.
Other users reported this as well and yet Credits recognition was pushed in the official release, enabled by default. I wander how many servers just endlessly waste resources since clearly it’s not working in some situations.
Oh yeah, same error. Sorry I forgot to mention that. I have whole log files here, if one of the Plex team wants to ping me via DM.
I’m just lucky I caught that it was happening at some point since these tasks are usually scheduled to run at 2am in my timezone. This makes sense from a load perspective of course, but it does make it hard to catch these types of errors.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
