You only get a skip credits button if there is mid or post-credit scene.
3 Likes
Just to let you know that I have reverted back to v1.30.2.6563 and the issue is not present in this release.
I understand credit detection isn’t in the prior build, but large cpu spikes well above 100% is not normal?
Yes, high cpu activity is expected even if its just credit detection running. The server should be automatically managing how much cpu is available and using just that. But huge spikes that cause a degraded performance should not be the case, hence why i said this was never an issue till this build. Meaning whatever is causing this, is likely due to credit detection specifically…
Anyway, I DM’d you my logs 
This is not a normal build. “cough” alpha “cough”.
Got your logs. You don’t have debug logging enabled, so there’s nothing to diagnose. Please enable, reproduce, and grab new logs.
At what point did I say it wasn’t Alpha? Literally the whole point of testing, is to report abnormal behaviour…
Well I’m not exactly a mind reader 
i’ll sort it out when I get home and send them via dm
This has now made it into the latest beta which released earlier today.
The feature has however not yet been lit up on that version while we ensure our support pages make it up and everyone involved is up to speed. The release notes will be updated to reflect the new features once they’re lit up.
That does mean that the feature inside this preview build will be disabled so it will no longer function.
Just want to say thanks again for everyone here that tested and provided feedback. All the issues brought up here, that are not related to the accuracy of the algorithm, have been addressed in the beta. The main ones being:
- Crashes
- Resource priority has been set correctly (shouldn’t hog CPU cycles when other things are more important).
- Items on which no credits were detected would continually be retried when the scheduled tasks ran.
- The detection process could timeout on slower systems.
Apart from tweaks to the underlying algorithm we have one currently known issue that still exists:
- The end of the credits markers can sometimes not match the end of the video when they should. This will lead to the skip credits button skipping to a few seconds before the end of the video instead of bringing up the post play screen.
I’ll leave this thread open for a bit until the feature is enabled on our beta.
15 Likes
How long will it take to unlock in the new beta?
5 Likes
Any update on the release time window? Thanks!
2 Likes
I would like to add to this, that I didn’t test the most recent builds yet so please keep that in mind, but like 3-4 weeks ago. The credtis detection was using 100% of my CPU permanently, making any other action laggy and degrading the performance of the entire host machine.
Unusable for an entire library if it’s still like this and if I was to run it with some 10k episodes and k-ish movies in my case
I’ve been experiencing the same exact thing as well and I am wondering if it’s related. I run a beefed up hetzner server and it never had spikes like thst before until the past twos weeks.
I’m tried various builds since this alpha, but it’s still happening during detection on any build since.
Oh that’s bad news. I thought this issue would’ve been addressed in the meantime 
Anyways, I’ll wait until CPU usage is down or maybe similar to Intro detection, which only needs a few % of CPU while running. And yeah I see the point that intro detection uses only audio to identify intros, whilst credit detection analyses video, but shredding my CPU for hours, days or most likely months until all my items have credit markers is probably not worth it 
@OhMyBahGosh and @SartBimpson:
Based on what @drzoidberg33 mentioned about this being “in” the latest beta but not actually turned on here [Forum Preview] Credits Detection for Plex Media Server - #151, I’m thinking that you can’t actually say if this issue is resolved yet or not. In the post by drzoidberg33, they mention:
So I would say until the feature is turned on in the beta and people can use the latest build of it, I would hold off on assuming it hasn’t been fixed because it sounds like it should’ve been in the latest (not yet active) version in the beta build.
I could be completely wrong, but that’s my take on what I’m seeing in this thread.
-Shark2k
I run a EX62-NVMe on hetnzer, and I’ve NEVER experienced CPU spikes like this prior. It’s NEVER even come close to preventing users from streaming/ accessing the server.
This started right after the alpha, and even on other builds now. I never was able to disable the credits detection, so I wonder if it’s still actively trying to run behind the scenes even though I no longer have the option to disable it.
What version are you running at the moment ?
1.31.0.6654 ?
Correct
Ouch, won’t 100% know for good until they light it up.
Although it sound like it could be still reading the setting from the DB and acting up on it.
Worth rolling back, if you haven’t already, to 1.30.2.6563?
Just another thought…
What happens if you go in to :
/PlexMediaServer/AppData/Plex Media Server/Preferences.xml
and if:
GenerateCreditsMarkerBehavior=“scheduled”
set it to never and then restart the server service?
2 Likes
Ain’t nothing like getting dismissed over “expected” spikes for them to be confirmed by other people and another dev 
Salt aside, if this is now a fixed known issue, my logs should no longer be necessary. I’ll hold off judgment till it goes live in the beta build and do some testing. If the issue still persists I’ll collect my logs and make sure debugging is turned on this time…
1 Like
Is this a way to activate the feature early? I had a look in my preferences file and didn’t see that code so I added it in but it didn’t work.
Any other suggestions on how to get it running in the beta? Thanks.
I don’t believe it is, it was still in my preferences after the alpha test. I don’t see any attempt for credit checks happening in the log files on the latest beta.
Just wondered if setting it to never may have helped OhMyBahGosh.
Sorry for the wait, but we decided to push this out with the public release of 1.31.0.
The support article is here: https://support.plex.tv/articles/credits-detection/
The feature has been enabled for all Plex Pass users now running PMS 1.31.0 or greater. It may take a while for your server to pick up the feature change, if you don’t feel like waiting a server restart should kick it into gear.
Please create a new forum post to report issues going forward, as this thread will get locked now.
4 Likes
