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

[Baenwort 124]

I've make sure CPU limit is 100, DMP is on, and I've set what I can figure out to Parallels processing. However, it doesn't seem to be using much resources on my server as I'm only seeing 15-20% resource usage. The server is at very low load at the moment with only ~4% cpu usage from other processes in other jails.

The settings I've adjusted:

 

[yocker 1855]

@Baenwort Looking at number of threads you have available for that CPU 30% usage sounds about right.
The FFmpeg usage is actually rather bursty so any CPU monitoring tool might not report it right either.

I can look into making some more "dedicated machine" settings to really let everything stretch it legs. Like for example increase batch size, looking into getting it to work with multiple tesseracts instances at once.
Atm. it's set rather conservative to make sure it wouldn't bog down peoples servers when running.

For now you can increase the speed a bit by disabling "Optimized Predictive Sampling in the OCR OCR Enhancements tab.

Edited August 22 by yocker

[Baenwort 124]

1 hour ago, yocker said:

@Baenwort Looking at number of threads you have available for that CPU 30% usage sounds about right.
The FFmpeg usage is actually rather bursty so any CPU monitoring tool might not report it right either.

I can look into making some more "dedicated machine" settings to really let everything stretch it legs. Like for example increase batch size, looking into getting it to work with multiple tesseracts instances at once.
Atm. it's set rather conservative to make sure it wouldn't bog down peoples servers when running.

For now you can increase the speed a bit by disabling "Optimized Predictive Sampling in the OCR OCR Enhancements tab.

The CPU used percentage isn't 30% as the FreeBSD htop command doesn't use 100% as the max but rather 100 x number of threads. If you look at the top of the htop window you will see most threads are under 30%. The CPU% column is the percent of a thread that is being used by that process. If a thread is using multiple threads fully then the percentage will show greater than 100.

I've disabled that and we'll see what the new calculation for time remaining levels out at.

[yocker 1855]

16 minutes ago, Baenwort said:

The CPU used percentage isn't 30% as the FreeBSD htop command doesn't use 100% as the max but rather 100 x number of threads. If you look at the top of the htop window you will see most threads are under 30%. The CPU% column is the percent of a thread that is being used by that process. If a thread is using multiple threads fully then the percentage will show greater than 100.

I've disabled that and we'll see what the new calculation for time remaining levels out at.

I meant to write 20% as you mentioned but guess i hit 3 instead of 2.  

Disabling it should speed it up a bit since it's an extra "detection method" used before the actual detection.
I should make it disabled by default tbh.

I've added what we discussed to my todo list and will start work on it next.

[yocker 1855]

@Baenwort did you see an improvement with the feature turned off?

[yocker 1855]

@BaenwortI have added some improvements, they are in the latest beta in the catalog.
Biggest improvement is being able to run multiple instances of local Tesseract detections.

[yocker 1855]

New version v2.7.1.3 in the catalog.

Added:
1) Ability to use multiple local Tesseract instances at once.
2) More control over CPU/GPU to improve performance on bigger machines.

Fixed:
1) Episode process bars should now show the correct info.
 

Edited Friday at 08:17 PM by yocker

[RedNo7 17]

question for understanding.

I have set a schedule for the plugin to run for 18 hours every day (as it needs to get through my whole library which will take a while).

The schedule screen shows the plugin ran correctly, but only for ~40 mins (1st screenshot).

When I run it manually, it states it needs ~450 hrs to complete (2nd screenshot).

Why is the scheduled task not running for the full 18 hours?

 

[yocker 1855]

2 hours ago, RedNo7 said:

question for understanding.

I have set a schedule for the plugin to run for 18 hours every day (as it needs to get through my whole library which will take a while).

The schedule screen shows the plugin ran correctly, but only for ~40 mins (1st screenshot).

When I run it manually, it states it needs ~450 hrs to complete (2nd screenshot).

Why is the scheduled task not running for the full 18 hours?

 

Did you set it to look in the correct folders?

Edited 10 hours ago by yocker

[RedNo7 17]

No - I cannot find those settings anywhere and it's not shown in the instructions. Where can I find them?

 

Sorry, Yes, I have these checked....

 

Edited 5 hours ago by RedNo7

[yocker 1855]

16 minutes ago, RedNo7 said:

No - I cannot find those settings anywhere and it's not shown in the instructions. Where can I find them?

 

Sorry, Yes, I have these checked....

 

And it still doesn't run detection for all videos with missing end credits?



Be sure this setting is disabled or it will only process new files since it last ran.

[RedNo7 17]

no, that's not enabled.

 

 

[yocker 1855]

23 minutes ago, RedNo7 said:

no, that's not enabled.

 

 

That's strange.
There is nothing that should stop it then other than some settings in Emby.



This is the schedule task in Emby.
See if the time limit is set as that will stop it.

Edit: I mean if it is set incorrectly.  

Also are these enabled in the plugin?

Edited 50 minutes ago by yocker

[yocker 1855]

I'm considering making an automatic resume if a failure happens.. Problem will be having it working well together with Embys time limit setting.