Jump to content

Plugin: EmbyCredits, detect end credits and add auto skip.

yocker

By yocker
in Plugins

 Share
Go to solution Solved by yocker,

Recommended Posts

yocker

yocker 1947

Posted
  • Author
Posted
4 minutes ago, fbourg said:

High failure rate despite OCR being enabledimage.thumb.png.93502c09eed3001afd2dd3fb864de362.pngimage.thumb.png.50fce1f18c8f80b1ec11fe8a6f30e382.png

That points to the problem being the files if all detections fail.
Can i get you to run a dry run with debug on one of those TV shows that there is a problem with and upload the log file that it gives?
Like for example the "Jane the Virgin" 

yocker

yocker 1947

Posted
  • Author
Posted (edited)
5 hours ago, fbourg said:

I haven't tested this version yet. I started it last night on 8.1, but when I woke up, the scan had stopped again. Even after adjusting the OCR, I still have quite a few episodes failing, even with 'OCR with hash fallback' enabled.

embyserver.txt 4.75 MB · 0 downloads

I'll look into it.
My theory as it is right now is that you might have some other plugin or outside program that might interfere with it as i have recently added automatic restarts if the plugin ever stops before the detections are done. 

Edit: Scratch that, i might know what's wrong. Will start on a fix now.

Edited by yocker
fbourg

fbourg 4

Posted
Posted

2.8.9.3 is new version ? 

yocker

yocker 1947

Posted
  • Author
Posted
20 minutes ago, fbourg said:

2.8.9.3 is new version ? 

Will be in the next one after that.
This was just a small quick fix to the black frame detection fallback.

  • Like 2
yocker

yocker 1947

Posted
  • Author
Posted
3 hours ago, fbourg said:

2.8.9.3 is new version ? 

I just uploaded 2.8.9.4. See if that one helps.

fbourg

fbourg 4

Posted
Posted
1 hour ago, yocker said:

I just uploaded 2.8.9.4. See if that one helps.

Time too longer (3000 hours)

yocker

yocker 1947

Posted
  • Author
Posted (edited)
35 minutes ago, fbourg said:

same problem with severance (i tested only this show)

credits-detection-debug-2026-09-21T21-00-21.log 246.43 kB · 1 download

That should have fixed the:
[swscaler @ 0x1feb500] [swscaler @ 0x22632c0] deprecated pixel format used, make sure you did set range correctly

Will keep trying.

Can you try and do a short detection with CPU and then Hardware acceleration only if possible?

Edited by yocker
yocker

yocker 1947

Posted
  • Author
Posted
15 hours ago, fbourg said:

I went back to the default settings (I had added +fra to the OCR as well as quite a few keywords; now I've removed both fra and jpn, along with the Japanese keywords, and it's running much better. I'll add them back once I've finished the essentials). That said, the scan could still stop again at any moment.

I just re-read this.
The keywords does not support jpn and fra as in the language codes. The OCR engine only looks for letters so adding a language code will do nothing.
Just add keywords that you know are in the credits of the episodes like for example "written", "story" "actor" and so on.

fbourg

fbourg 4

Posted
Posted

Thanks for the clarification on the keywords and language codes. Just to confirm, the latest tests were already done with "eng" only—I had already removed both "fra" and "jpn" as well as the non-English keywords.

  

Regarding the range warning (make sure you did set range correctly), I wasn't sure if that was a setting I had to configure on my end or just an internal FFmpeg warning.

  

Those tests were run with QSV. I will run a short detection using CPU only as requested, test it again with hardware acceleration, and share the new logs.

yocker

yocker 1947

Posted
  • Author
Posted
14 minutes ago, fbourg said:

Thanks for the clarification on the keywords and language codes. Just to confirm, the latest tests were already done with "eng" only—I had already removed both "fra" and "jpn" as well as the non-English keywords.

  

Regarding the range warning (make sure you did set range correctly), I wasn't sure if that was a setting I had to configure on my end or just an internal FFmpeg warning.

  

Those tests were run with QSV. I will run a short detection using CPU only as requested, test it again with hardware acceleration, and share the new logs.

The range setting is nothing you can do anything about. It's just noise indirectly caused by the yuv420p format of the video.
I should remove that from being logged.

yocker

yocker 1947

Posted
  • Author
Posted (edited)
2 hours ago, fbourg said:

with cpu only solve on severance show, but for this show, another problem : 

credits-detection-debug-2026-09-22T07-39-28.log 458.72 kB · 1 download

There's a new version in the catalog.
Version 2.8.9.6 beta.

Also please send me your embycredits.xml settings file.
You will find it in plugins/configurations.

Edited by yocker
fbourg

fbourg 4

Posted
Posted
40 minutes ago, yocker said:

There's a new version in the catalog.
Version 2.8.9.6 beta.

Also please send me your embycredits.xml settings file.
You will find it in plugins/configurations.

Here is the XML file. If you have any edits or feedback, feel free to send an updated version over. Thanks a lot!

EmbyCredits.xml

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...