Video Timestamp Errors on Custom Channel Recordings

Recordings that I've scheduled on a custom channel continually have timestamp issues. Most appear to only have recorded a few minutes but the file size is large/normal. Manually selecting "Fix Video Timestamps" on each recording works. Is there any way to avoid having to manually do this? I've submitted logs as 62204c82-e808-44b0-96c5-77810ae901cb.

Submit diagnostics from the dvr

Done

Any updates on this @tmm1?

1 Like

Are these recordings typically marked as Interrupted in Channels?

Yes

Please try enabling Experimental TV Everywhere MPEG-TS Rewriter and see if that improves anything for you.

I enabled that but noticed issues with TVE recordings (stuttering) and no change on some recordings from custom channels; I still have to manually “fix video timestamps”.

Thanks for testing

Sure. So, are there any other options to avoid having to manually fix video time stamps?

It's supposed to run automatically for these recordings.

Can you give me some examples of how long it was supposed to record for vs what it says for the recording duration before you fix it.

One example: a news broadcast that’s set to record for 34 minutes (padding 1 min before and 3 after it’s scheduled airing). The DVR is showing that it only recorded 16 minutes. After manually selecting fix video timestamp, it now shows 34 minutes but with a recording was interrupted flag.

Another example is a series pass that is currently recording. It is set to record for two hours. ~90 minutes and counting have recorded thus far and it already has the interrupted flag. When it’s finished recording, I expect the recorded time shown in the DVR to be less than the amount shown even now (edit: it ended up at 1hr 8m but after fixing/rewriting timestamps it’s 1hr 59m). FWIW, I’ve turned off commercial detection for this pass. Also, it is a custom channel from an MPEG-TS source.

I don’t actually mind manually fixing the video timestamp as you guys have made it stupid simple to do so. I’m more curious as to why it’s not working automatically as intended.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.