Movie stuck on Processing / Detecting Commercials

Channels DVR Server Troubleshooting
#1

I have a recently recorded movie that has been stuck on the "Processing recording Movies" and "Detecting Commercials" for a few hours. I've restarted the Windows computer Channels is running on, but it just continues to try and process the movie after the restart. Most of my other comskip tasks take 20 - 25 minutes per movie. All 4 cores of my Intel i5 are running at around 40-45% utilization, so it appears something is trying to run.

I'm currently on build 2020.02.03.1850. I've tried re-detecting commercials, but nothing seems to work. Is there some reason why this movie would take so much longer than other similar length movies? Not sure how to fix it.

StuckonProcessing

Edit%20Commercials
Edit Commercials.PNG889×321 14.6 KB

#2

What does it show if you click that "comskip.log" link? It must be stuck processing due to some sort of bug in comskip..

#3

It shows a lot when I click on the comskip.log. Not sure what I am looking for there. The log file it creates is 39MB and increasing by the looks of it. Is there someway I can send this to you?

On a side note, I did look at what was eating the CPU cycles and noticed that windows defender was using 20% and comskip is listed twice both at around 10%. Just for giggles, I excluded the Channels DVR directly in windows defender and comskip is now using 19% per process (there are still 2 of them), and windows defender dropped to 15%. It is still stuck processing the movie though.

#4

The comskip.log for that movie is up to 109MB now. Is that normal? Is there a way to tell it to stop processing this one movie? I'm concerned that it won't process other shows since it seems to be stuck on this one.

#5

It will eventually give up after a few hours. You can also use Windows task manager to kill comskip and it will give up right away.

What are the last ten lines of the log?

#6

Some good news, when I went to check the log, the comskip finally completed. Not sure why it took so long, but the comskip.log was filled with this (see below). This just keep repeating through the log.

DFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
Frame Rate corrected to 59.940 f/s
Frame Rate set to 48000.000 f/s
Frame Rate set to 48000.000 f/s
DFps[1]= 59.940 f/s
DFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
Frame Rate corrected to 59.940 f/s
Frame Rate corrected to 59.940 f/s
Frame Rate set to 48000.000 f/s
DFps[1]= 59.940 f/s
DFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
Frame Rate corrected to 59.940 f/s
AFps[1]= 59.940 f/s
Frame Rate corrected to 59.940 f/s
Frame Rate set to 48000.000 f/s
Frame Rate set to 48000.000 f/s
DFps[1]= 59.940 f/s
DFps[1]= 59.940 f/s
RFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
AFps[1]= 59.940 f/s
Frame Rate corrected to 59.940 f/s
Frame Rate corrected to 59.940 f/s

#7

1hou51mins

Something was definitely weird though. Processed 7 hours ago, and took 1 hr and 51 minutes.