Comskip by channel reversal

I used the following command to stop commercial checking for a channel. It worked fine.

curl -XPUT http://192.168.0.232:8089/comskip/ignore/channel/6073

Now I want to restore that channel to normal operation. I tried:
curl -XDELETE http://192.168.0.232:8089/comskip/ignore/channel/6073

This did not work. Does anyone know the correct command?

That's correct. Which part doesn't work?

I did the -XDELETE, got back "OK", but it still is not checking for commercials.

Just in case I messed up something, I'll do the -XDELETE again and check the results. Will report back on results.

Is this for new recordings made after the change?

The command will not retroactively scan old recordings for commercials. To do that you must manually scan the old recordings.

You can verify by looking at /settings (http://x.x.x.x:8089/settings)
When enabled you have the line
comskip.ignore.channel.6073 = "true"
After curl -XDELETE the line will no longer be there

To manually run commercial detection of a recorded program, from the DVR web UI:
Library > TV Shows > Program Name > Episode > :gear: > Redetect Commercials

Channel doesn't appear in "settings", log shows ComSkip failed, but ComSkip works fine on other channels. Here is what is in the log when I tested:

2021/12/02 12:32:38.866810 [DVR] Starting job 1638464400-ch6073 Outnumbered on ch=[6073]
2021/12/02 12:32:38.866810 [DVR] Waiting 47m21.1331894s until next job 1638469200-ch6073 Fox for Lunch
2021/12/02 12:32:38.866810 [DBG] Scheduling wake timer for scheduled recording in 45m51.1331894s
2021/12/02 12:32:39.605457 [TVE] stream timestamps: fnc: start_at=2021-12-02T12:31:38-05:00 current_at=2021-12-02T12:31:58-05:00 end_at=2021-12-02T12:32:06-05:00
2021/12/02 12:32:39.606456 [TNR] Opened connection to TVE-Fubo for ch6073 FNC
2021/12/02 12:32:39.607456 [DVR] Recording for job 1638464400-ch6073 from TVE-Fubo ch6073 into "TV\Outnumbered\Outnumbered 2021-12-02-1232.mpg" for 27m51.1331894s
2021/12/02 12:32:39.628588 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 12:32:39.636746 error loading snapshot epoch: 3565: error opening segment 2475: error loading segment fromt directory: open recorder.idx\groups\0000000009ab.seg: The system cannot find the file specified.
2021/12/02 12:32:39.640965 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 12:32:39.649146 [IDX] Generating video index for job 1638464400-ch6073

2021/12/02 13:00:30.038891 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 13:00:30.040101 [MTS] Statistics for "TV\Outnumbered\Outnumbered 2021-12-02-1232.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=176 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=1681.109189
2021/12/02 13:00:30.066638 [TNR] Closed connection to TVE-Fubo for ch6073 FNC
2021/12/02 13:00:30.066638 [DVR] Finished job 1638464400-ch6073 Outnumbered
2021/12/02 13:00:30.076545 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 13:00:30.077079 [DVR] Processing file-4174: TV\Outnumbered\Outnumbered 2021-12-02-1232.mpg
2021/12/02 13:00:30.080889 [DVR] Waiting 19m29.9191109s until next job 1638469200-ch6073 Fox for Lunch
2021/12/02 13:00:30.080889 [DBG] Scheduling wake timer for scheduled recording in 17m59.9191109s
2021/12/02 13:00:30.979269 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 13:00:31.382187 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.
2021/12/02 13:00:31.384282 [DVR] Running commercial detection on file 4174 (TV\Outnumbered\Outnumbered 2021-12-02-1232.mpg)
2021/12/02 13:02:10.051880 [DVR] Commercial detection failed for Outnumbered 2021-12-02-1232.mpg with exit status 1

Produced the following log:

2021/12/02 13:26:38.506506 [DVR] Running commercial detection on file 4174 (TV\Outnumbered\Outnumbered 2021-12-02-1232.mpg)
2021/12/02 13:28:17.964136 [DVR] Commercial detection failed for Outnumbered 2021-12-02-1232.mpg with exit status 1

The lines before this in the log show there were errors in the recording, meaning the file itself has issues. The line I quoted shows that commercial detection is indeed being run. However, because the recording had errors, it could not properly run detection.

Everything is working as it should. There just happened to be problems with the stream, which probably confused you into thinking your un-ignoring of commercial detection failed.

I’ve also seen that it reports “failure” if it was unable to identify any commercial breaks, even if the recording is flawless. I wish they would improve the message in that case, but I’m sure that’s a comskip problem and not something Channels can fix. It really confused me the first time I saw it too.

1 Like

I don't believe that there are errors in the recording.

2021/12/02 14:42:13.503899 error loading snapshot epoch: 351695: error opening segment 211740: error loading segment fromt directory: open recorder.idx\files\000000033b1c.seg: The system cannot find the file specified.

This error keeps showing up over and over again regardless of what is recording, what is playing, and regardless of what is being checked for commercials.

It is ALWAYS EPOCH: 351695, SEGMENT: 211740, FILE: 000000033b1c.seg.

Anyone know why I would be getting the same error over and over again?

Sometimes comskip fails, for any number of reasons. You can inspect the comskip log for more details.

The other error is related to a corrupted search index. Fix as follows:

curl -XPUT /dvr/database/reindex

Problem is fixed. Not sure what fixed it. I did the reindex, reran the -XDELETE, rebooted the server machine. I now understand the Comskip reports an error if no commercials are detected.

Somewhere in all of this, things are working again. Thanks for all who helped.

1 Like