Defective TS files with displayed zero length

[sub]

There is one minor fix to something I saw in your logs, but I can't see it causing any issue in those files above.

[johnsta]

> What problem are you seeing with FNC that makes you think it's
> defective? I doesn't appear to have the problem with extra data at
> the start of it, and plays for me in VLC, Windows Media Player and
> NextPVR.

> I've just checked the CNN file and it seems ok too. I can't see
> any signs of extra data on that file either.

These two files (FNC* and CNN*) fit the "partially defective"
definition that I've described before. Both files run under VLC, but
display a duration time of 00:00 -- the hotkeys can't be used, but the
progress bar can be used. The FNC* file plays on WMPLAYER, but shows
a duration time of 21:31:50. The CNN* file plays on WMPLAYER, and
displays the correct duration time.

The following file, recorded starting at noon today, is "completely
defective," in that it doesn't play at all on VLC or WMPLAYER:

http://jxenakis.com/gdgraphics/Bloomberg...2001400.ts

These are the file-writer* and nrecord.log files:

http://jxenakis.com/gdgraphics/fw-1226-180214.zip
http://jxenakis.com/gdgraphics/nr-1226-180214.zip

Here's the HDHR log for the period around 12 noon (1700 gmt):


20180214-13:59:03 Tuner: tuner0 tuning 284 FOXBUSNET (auto:165MHz-2808)
20180214-13:59:03 Tuner: tuner0 streaming rtp to 192.168.1.115:36323
20180214-13:59:03 CableCARD: tuner0 284 FOXBUSNET (auto:165MHz-2808) access = subscribed
20180214-17:00:00 Tuner: tuner0 tuning 45 BLOOMBG (auto:201MHz-1214)
20180214-17:00:00 Tuner: tuner0 rtp stream ended (new request)
20180214-17:00:00 Tuner: tuner0 streaming rtp to 192.168.1.115:36312
20180214-17:00:00 CableCARD: tuner0 45 BLOOMBG (auto:201MHz-1214) access = subscribed
20180214-17:00:01 Tuner: tuner1 tuning 46 CNBC (auto:153MHz-2604)
20180214-17:00:01 Tuner: tuner1 rtp stream ended (new request)
20180214-17:00:01 Tuner: tuner1 streaming rtp to 192.168.1.115:36313
20180214-17:00:01 CableCARD: tuner1 46 CNBC (auto:153MHz-2604) access = subscribed
20180214-17:00:02 Tuner: tuner2 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
20180214-17:00:02 Tuner: tuner2 rtp stream ended (new request)
20180214-17:00:02 Tuner: tuner2 streaming rtp to 192.168.1.115:36314
20180214-17:00:02 CableCARD: tuner2 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed
20180214-17:28:24 Tuner: tuner0 tuning 45 BLOOMBG (auto:201MHz-1214)
20180214-17:28:24 CableCARD: tuner0 45 BLOOMBG (auto:201MHz-1214) access = subscribed
20180214-17:28:25 Tuner: tuner0 rtp stream ended (new request)
20180214-17:28:25 Tuner: tuner0 streaming rtp to 192.168.1.115:36312
20180214-17:28:26 Tuner: tuner1 tuning 46 CNBC (auto:153MHz-2604)
20180214-17:28:26 Tuner: tuner1 rtp stream ended (new request)
20180214-17:28:26 Tuner: tuner1 streaming rtp to 192.168.1.115:36313
20180214-17:28:27 CableCARD: tuner1 46 CNBC (auto:153MHz-2604) access = subscribed
20180214-17:28:28 Tuner: tuner2 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
20180214-17:28:28 Tuner: tuner2 rtp stream ended (new request)
20180214-17:28:28 Tuner: tuner2 streaming rtp to 192.168.1.115:36314
20180214-17:28:28 CableCARD: tuner2 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed

Presumably the problem occurred when the channel changed from 284 to
46 at 17:00.

I wonder, is there a way in the HDHR api when there's a channel change
on a tuner to completely terminate the recording with one command to
return the tuner to a reset state, then start the new stream from the
reset state with a separate command? That would seem to match the
cases that have worked reliably (restarting nrecord.exe, or canceling
and restarting a recording).

Thanks,

John

[johnsta]

There is one minor fix to something I saw in your logs, but I can't see it causing any issue in those files above.

Sorry, I didn't see this in time. I'll try it next time, but I have to go out now.

[sub]

These two files (FNC* and CNN*) fit the "partially defective"
definition that I've described before. Both files run under VLC, but
display a duration time of 00:00 -- the hotkeys can't be used, but the
progress bar can be used. The FNC* file plays on WMPLAYER, but shows
a duration time of 21:31:50. The CNN* file plays on WMPLAYER, and
displays the correct duration time.

What version of VLC are you using? I'm using the current 3.0 release, and I'm getting a valid duration for both files, and can skip around in VLC just fine. WMP also seems to be giving a valid duration and can skip.

I can't see anything wrong with these two files.

[sub]

johnsta, I'll send you a PM about one other item.