Comskip running twice for each recording

Channels DVR Server Troubleshooting
#1

Not sure what version this started happening, will have to examine logs tomorrow.
I had 5 recordings tonight and comskip is being run twice on each one that has its timestamps rewritten.
Here's one example from tonight using v2021.03.06.0114, can provide the other four tomorrow if needed.

2021/03/11 17:00:00.011023 [DVR] Starting job 1615510800-ch703 NBC News Specials on ch=[703]
2021/03/11 17:00:00.471389 [TNR] Opened connection to 1323AADB/0 for ch703 KCRADT
2021/03/11 17:00:00.471804 [DVR] Recording for job 1615510800-ch703 from 1323AADB ch703 into "TV/NBC News Specials/NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg" for 59m59.988833957s
2021/03/11 17:00:00.515580 [DVR] Refreshing metadata for NBC News Specials (16244624)
2021/03/11 17:00:00.836856 [IDX] Generating video index for job 1615510800-ch703
2021/03/11 18:00:00.000757 [TNR] Closed connection to 1323AADB/0 for ch703 KCRADT
2021/03/11 18:00:00.102354 [SNR] Statistics for "TV/NBC News Specials/NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg": ss=95%-97% snq=100% seq=100% bps=6706293,3092224-10279840 pps=641,311-978
2021/03/11 18:00:00.108116 [DVR] Finished job 1615510800-ch703 NBC News Specials
2021/03/11 18:00:00.152619 [DVR] Marking expired job 1615510800-ch703 NBC News Specials
2021/03/11 18:00:00.152726 [ERR] Could not find job 1615510800-ch703 to update
2021/03/11 18:00:01.029777 [DVR] Processing file-3286: TV/NBC News Specials/NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg
2021/03/11 18:00:01.536735 [MTS] Rewriting MPEG-TS timestamps for file-3286: NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg
2021/03/11 18:01:02.676592 [MTS] Statistics for "NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=3600.341211
2021/03/11 18:01:04.430863 [MTS] Finished video index generation for file-3286 in 62s
2021/03/11 18:01:04.889554 [IDX] Generating video index for file-3286: NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg
2021/03/11 18:01:32.686696 [IDX] Finished video index generation for file-3286 in 27s
2021/03/11 18:13:11.875543 [DVR] Running commercial detection on file 3286 (TV/NBC News Specials/NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg)
2021/03/11 18:51:19.279537 [DVR] Commercial detection for NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg finished with 10 markers in 38m7.404257899s.
2021/03/11 18:51:19.484880 [DVR] Running commercial detection on file 3286 (TV/NBC News Specials/NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg)
2021/03/11 19:29:29.581242 [DVR] Commercial detection for NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg finished with 10 markers in 38m10.096430029s.

Also curious why it's rewriting MPEG-TS timestamps on my HDHR Prime recordings

[MTS] Rewriting MPEG-TS timestamps for file-3286: NBC News Specials President Bidens Address to the Nation on the Anniversary of the COVID Lockdowns 2021-03-11-1700.mpg

It was doing this on another recorded file while comskip was running on the same file.

#2

Here's the one where it was rewriting timestamps at the same time comskip was running.
This DVR is running v2021.03.10.2332

2021/03/11 16:59:02.596720 [DVR] Starting job 1615510740-ch6004 PBS NewsHour Special Report on ch=[6004]
2021/03/11 16:59:03.930400 [TNR] Opened connection to TVE-Comcast_SSO for ch6004 KVIE
2021/03/11 16:59:03.930999 [DVR] Recording for job 1615510740-ch6004 from TVE-Comcast_SSO ch6004 into "TV/PBS NewsHour Special Report/PBS NewsHour Special Report 2021-03-11-1659.mpg" for 1h0m57.402995633s
2021/03/11 16:59:03.987443 [DVR] Refreshing metadata for PBS NewsHour Special Report (19641366)
2021/03/11 16:59:04.127397 [IDX] Generating video index for job 1615510740-ch6004
2021/03/11 18:00:00.052692 [MTS] Statistics for "TV/PBS NewsHour Special Report/PBS NewsHour Special Report 2021-03-11-1659.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=3667.730733
2021/03/11 18:00:00.060215 [TNR] Closed connection to TVE-Comcast_SSO for ch6004 KVIE
2021/03/11 18:00:00.064518 [DVR] Finished job 1615510740-ch6004 PBS NewsHour Special Report
2021/03/11 18:00:00.184904 [DVR] Processing file-2028: TV/PBS NewsHour Special Report/PBS NewsHour Special Report 2021-03-11-1659.mpg
2021/03/11 18:00:01.821096 [DVR] Running commercial detection on file 2028 (TV/PBS NewsHour Special Report/PBS NewsHour Special Report 2021-03-11-1659.mpg)
2021/03/11 18:00:01.859557 [MTS] Rewriting MPEG-TS timestamps for file-2028: PBS NewsHour Special Report 2021-03-11-1659.mpg
2021/03/11 18:01:30.034485 [MTS] Statistics for "PBS NewsHour Special Report 2021-03-11-1659.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=3667.730733
2021/03/11 18:01:31.151787 [MTS] Finished video index generation for file-2028 in 89s
2021/03/11 18:01:33.419097 [IDX] Generating video index for file-2028: PBS NewsHour Special Report 2021-03-11-1659.mpg
2021/03/11 18:02:18.877155 [IDX] Finished video index generation for file-2028 in 45s
2021/03/11 18:43:04.713526 [DVR] Commercial detection for PBS NewsHour Special Report 2021-03-11-1659.mpg finished with 6 markers in 43m2.892772269s.
2021/03/11 18:43:06.111822 [DVR] Running commercial detection on file 2028 (TV/PBS NewsHour Special Report/PBS NewsHour Special Report 2021-03-11-1659.mpg)
2021/03/11 19:24:11.514987 [DVR] Commercial detection for PBS NewsHour Special Report 2021-03-11-1659.mpg finished with 6 markers in 41m5.403233633s.
#4

After a recording is completed, we check to see if the recorded duration is more than twice as long as the show was. We are using this to indicate that there was a discontinuity in the timestamps on the HDHR recording and automatically reprocess them.

It's confusing that it ran and found no discontinuities... Did you happen to have a lot of padding on the show?

#5

Yes I added 30 mins padding.

I had 5 recordings, all 30 minute shows, all had 30 minutes padding added.
Source HDHR Prime - ABC, FOX and NBC. NBC was the only one that had its timestamps rewritten.
Source TVE - CBS and PBS. Both had their timestamps rewritten.

I would think you want to take padding into account and use the requested record duration instead of EPG show duration.

Why is comskip running twice, but only on shows that has their timestamps rewritten?
Also, why is comskip running while the recording is being modified (rewriting timestamps)?

#7

What are you trying to say?

That there are valid reasons for padding shows?

Just trying to understand what you're adding to this thread.

The fact is that Channels DVR is rewriting timestamps on my perfectly good recordings, doing it while comskip is running and running comskip twice on those recordings.

As far as I'm concerned, this is a bug.

#8

Sorry...will had more details now.

I have recordings with long paddings and don't see this behavior at least it's not showing anything in the logs. I checked and Family Guy i have set 15min after padding.

2021/03/07 21:15:00.078962 [DVR] Finished job 1615170540-17 Family Guy
2021/03/07 21:15:00.092594 [DVR] Processing file-713: TV/Family Guy/Family Guy S19E13 PeTerminator 2021-03-07-2029.mpg

2021/03/07 21:15:00.187537 [DVR] Running commercial detection on file 713 (TV/Family Guy/Family Guy S19E13 PeTerminator 2021-03-07-2029.mpg)
2021/03/07 21:16:19.520535 [DVR] Commercial detection for Family Guy S19E13 PeTerminator 2021-03-07-2029.mpg finished with 8 markers in 1m19.333044393s.

is see the devs post about it being 2x as long, and that does result in the behavior you described.


so, its not a bug, its expected behavior.

though, comskip running at the same time, may be.
I would think.

try setting your padding to less than 30 min. to make the recorded file less than 2x as long as the program time slot.

Edit. Dev already commented..so there's your answer. Now move on and stop being so entitled and insulting. this is a public form if you want a private conversation directly with a dev then email them. your attitude and posts are a violation of the community guide lines, and you locking the thread, just cause you don't like others posts and won't accept a devs statement, is trust level abuse.
The badge "Leader" states "set a positive example for the rest of the community in your actions and words here." should be revoked since u can't seem to adhere to those standards.

#9

You guessed wrong

You think so? Why?

NO, they need to fix the bug. Workaround is to disable auto comskip and manually run it on each show until the bug is fixed.

It's pointless replying to you if you don't understand the issue.
I'm waiting for a dev to reply and meanwhile have disabled auto comskip in DVR settings.

Go find another thread to comment on.

#10
#11

This is fixed in v2021.03.15.2225. Thanks for the detailed bug report.

2 Likes
#12

:+1: :+1: :+1: