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

[yocker 1931]

51 minutes ago, fbourg said:

Hi everyone,

I'm looking to test the latest beta version of the EmbyCredits plugin, but I cannot find the beta .dll file on GitHub.

Could someone point me in the right direction or share where to download the latest beta build? (Is it shared via PM, attached to a specific post in this thread, or hosted on another branch?)

Setup & Hardware Specs

CPU: Intel Core i7-14700K (Quick Sync Video active, no dedicated NVIDIA GPU)

RAM: 128 GB

Library size: ~61,000 episodes

Questions regarding settings:

1. Chromaprint triggering at the beginning of episodes

When trying to use Chromaprint (audio fingerprinting), it's misbehaving and matching way too early, near the start of the video:

What are the recommended settings or search offsets to force the audio scan to focus strictly on the last few minutes of the episode?

What are good values for the minimum match duration and confidence thresholds to prevent opening themes or incidental audio cues from triggering false positive markers?

2. OCR tuning & performance scaling

With 61,000 episodes, running OCR takes a massive amount of time:

Without a dedicated NVIDIA card (no CUDA), the OCR engine is relying purely on the CPU/RAM, while frame extraction can use Intel QSV.

With 20 cores / 28 threads on the 14700K and 128 GB of RAM, what are the recommended settings (worker threads, extraction FPS, temp directory configuration) to maximize throughput without bottlenecking the system?

Are there best practices to avoid the initial scan choking the server on such a large library?

Thanks in advance for your help and feedback!

Now that i'm sitting at my computer i can answer the other questions without having to fight my phones autocorrect.

1. Chromaprint is not very accurate and i generally advice against using it.
I'm planning some time in the future to try and merge it with blackframe detection to more accurately find the end credits.
It's a rather big operation to implement that so might be a good while before that is ready.
There are settings you can fine tune for the chroma detections, sadly the defaults are the best ones i have found so far.

I strongly advice using OCR when possible.

2. Only the PaddleOCR supports Nvidia cards. If using the Tesseract it's CPU only. The plugin it self can use GFX cards for extracting the images but in reality it's not really that much faster.
With an 14700K it shouldn't be to slow (I'm running it with a 7950X3D so not that much bigger a CPU).
It's not memory intensive so 128GB is WAY overkill.
If you insist on fine tuning and not using the presets already there then I suggest using Tesseract and the default settings but change:
1. Paraelle FFmpeg Sessions to 4 (If this bogs down the machine than lower it a bit)
2. FFmpeg Thread Limit: to 4 or higher. You can set it to 0 if you are comfortable with it being allowed to take all your CPU.
3. Hardware Acceleration Type: Set to Quick Sync. (If that fails set it to VAAPI, havn't tested if Quick Sync finally works with the newest Emby)
4: Parallel Batch Size: 4 (again lower this if you find it bogs down the machine.

The rest of the settings should be pretty self explanatory as they say if they are recommend to enable or disable.

A single high quality TV show episode takes about 20 seconds for me so... 65.000 episodes would be a bit over 2 weeks if running one at a time.  

If you have any questions don't hesitate to ask.
In case i'm not here to help then @Neminemmight be able to help as he is a big user of the plugin as well and always ready to help.

Edited 2 hours ago by yocker

[fbourg 2]

Thank you for your message. I haven't applied your suggested settings yet, but with the default ones, the scan stopped twice... Here is the log file.

embyserver.txt

[yocker 1931]

14 minutes ago, fbourg said:

Thank you for your message. I haven't applied your suggested settings yet, but with the default ones, the scan stopped twice... Here is the log file.

embyserver.txt 4.74 MB · 0 downloads

I'll take a quick look but sadly don't have much time as i'm going away for the weekend, sorry.
If i don't find anything now it will have top priority when i get back!

[yocker 1931]

@fbourg Looks like the files were changed mid detection and the detections failed because of that.
In fact the whole settings page looks to have soft crashed.

If the logs don't reveal anything then I should be able to conquer something up to help with that. 

As said i'm going away for the weekend so will take a little while, sorry about that.
I promise it will have top priority once i'm back!

Edited 21 minutes ago by yocker