Commercial Detection slow

I am commercial detecting on a 1 hour show and I'm only allowing 1 core because it runs that core at 100%, here it is on htop over 30min of detection. Should you expect a 1 hour show will take 1 hour to detect commercials?

and if you happen to have a EPG update scheduled during detection it corrupts the database. Below is the system I'm running on. More that enough power

image

1 Like

Something wrong there.
One hour movie on a 5 year old NAS with a 4-core Celeron using 2 threads.
Runs 2 of the cores at 100%.
Screenshot 2024-07-30 at 19-03-55 Channels Settings
Screenshot 2024-07-30 at 19-04-28 Channels Settings
Will report the time it takes when it's finished
13 minutes

2024/07/30 19:00:21.848514 [DVR] Running commercial detection on file 813 (The Colorado (2016).ts)
2024/07/30 19:13:31.488221 [DVR] Commercial detection for The Colorado (2016).ts finished with 8 markers in 13m9.664162887s.

About the same results using the same movie with Channels running in a container on the same NAS, using 2 threads, same load averages.

2024/07/30 19:27:19.135445 [DVR] Running commercial detection on file 2877 (The Colorado (2016).ts)
2024/07/30 19:40:33.814455 [DVR] Commercial detection for The Colorado (2016).ts finished with 8 markers in 13m14.718500392s.

Screenshot 2024-07-30 at 19-30-25 Channels Settings

What type of video is in the show you're running detection on?
My example is an H.264 1920x1080p recording.
Screenshot 2024-07-30 at 19-48-54 Channels The Colorado...

1 Like

You don’t really say what the source of the show is but if it is a 1 hour TVE recording I would expect with that cpu a 14-15min commercial detection. If you set it at 6 you should get it down to 3-4 minutes. Why are you only using a single core?

1 Like

I'm not following the logic here. If you use more cores you will have more resources to allocate to comskip thus making the commercial detection time faster. You've got 8, allocate 4 to it and see if it gets better.

Also it depends on your bitrate as to how much processing time it takes
My LinkPi set at 9000kbps (30min show = 5min):

Commercial detection for Contraband Seized at Sea S01E03 Bahamian Rhapsody 2024-07-29-2059.mpg finished with 12 markers in 4m58.583291576s (7 threads).

Here is a 30min recording from frndly TV (bitrate ~2500kbps):

Commercial detection for Prison Chronicles S01E01 Alcatraz 2024-07-29-2203.mpg finished with 10 markers in 53.847625668s (7 threads).

Depends on the show being detected as well.

2024/07/27 20:02:23.514251 [DVR] Commercial detection for Wheel of Fortune S40E43 2022-11-09 Veterans Week 2024-07-27-1929.mpg finished with 12 markers in 1m22.4377412s (3 threads).

2024/07/28 19:27:08.074397 [DVR] Commercial detection for Big Brother S26E06 2024-07-28-1758.mpg finished with 14 markers in 27m3.276015672s (3 threads).

2024/07/29 09:36:36.609742 [DVR] Commercial detection for The Price Is Right 2024-07-29-0800.mpg finished with 18 markers in 35m35.554027546s (3 threads).

INTEL Celeron J4125 2 GHz 4C/4T
18 GB RAM

I have EPG update running once a day and if commercial detection happens during that update it corrupts the database.

That doesn't sound like expected behaviour. You may want to investigate that becuase I run guide updates every hour and have never had an issue on my bare metal or Docker Channels servers.

Regardless all the more reason to allocate more cores to get it done faster.

I agree with @slampman that it shouldn't be corrupting your database.
Both comskip and EPG updates are the most cpu intensive parts of Channels DVR.

Would still like to know what type video is taking an hour to comskip an hour program.
Generally an MPEG video is quickest, followed by an HD H.264, followed by a HEVC 2k and 4k.
Besides the duration, bitrate comes into play also.

I run 6 Channels DVR Servers on my 5yr old NAS doing comskip and EPG updates on each. One runs in the native Synology Package and the other 5 run in containers. Never have that issue.

Yes, I'm recording mpg. I upped the cores to 4
Commercial detection for TMZ ᴺᵉʷ 2024-08-01-0359.mpg finished with 4 markers in 2m17.736659223s (4 threads).

I think the issue I'm having is something different and not related to detection. Thanks for all the responses

1 Like