How to avoid zero byte files?

[micmij]

Hi,

I occasionally have zero byte files created and would, obviously ( !!), like to avoid it as much as possible.  I think part of the issue is that the antenna in my rental is a little flakey, so it's something that will remain an issue until/if that's fixed.

However, until that time, is there something that I can do to get NPVR to retry getting a locked signal every 30-60 seconds (looking at the log of the latest failure, it appears to have tried once or twice - see log entry below).  I also think that some recordings are cut short when the signal is lost, and it would be great if there was an option to try to restart the recording.

Any other options/advice?

Thanks for your help!
Mic

============================= Log =============================
2020-05-08 23:46:05.206 [INFO][18] Got POST request: /stream/start?slipseconds=1200&target=C%3A%5CTV%20Recordings%5Crage%5Crage_2020-05-08_23510459.ts
2020-05-08 23:46:05.212 [DEBUG][18] Starting Stream: C:\TV Recordings\rage\rage_2020-05-08_23510459.ts
2020-05-08 23:46:05.212 [DEBUG][18] SlipSeconds: 1200
2020-05-08 23:46:05.212 [DEBUG][18] Tuning:
<tuning>
  <type>DVB-T</type>
  <locator>
    <frequency>226500</frequency>
    <bandwidth>7</bandwidth>
  </locator>
  <service_id>549</service_id>
  <tsid>545</tsid>
  <onid>4112</onid>
  <service_type>25</service_type>
  <provider>ABC</provider>
</tuning>

2020-05-08 23:46:05.213 [DEBUG][18] StartStream(): C:\TV Recordings\rage\rage_2020-05-08_23510459.ts
2020-05-08 23:46:05.241 [DEBUG][18] Using tuner: Silicondust HDHomeRun Tuner 1251B89D-0 (1)
2020-05-08 23:46:05.242 [DEBUG][18] About to connect...
2020-05-08 23:46:05.242 [DEBUG][18] has network provider
2020-05-08 23:46:05.242 [DEBUG][18] has tuner
2020-05-08 23:46:05.255 [INFO][18]             [0441e7cc-0026-0000-68e741047d98b101]-0000004c-01b73bfc
2020-05-08 23:46:05.255 [DEBUG][18] About to auto detect capture filter...
2020-05-08 23:46:05.255 [DEBUG][18] Skipping capture filter detection
2020-05-08 23:46:05.255 [DEBUG][18] No BDA capture filter for this device
2020-05-08 23:46:05.266 [DEBUG][18] Graph filter list:
2020-05-08 23:46:05.267 [DEBUG][18] - MPEG-2 Sections and Tables
2020-05-08 23:46:05.267 [DEBUG][18] - BDA MPEG2 Transport Information Filter
2020-05-08 23:46:05.267 [DEBUG][18] - MPEG-2 Demultiplexer
2020-05-08 23:46:05.267 [DEBUG][18] - NPVR TS Mon
2020-05-08 23:46:05.267 [DEBUG][18] - Tuner
2020-05-08 23:46:05.267 [DEBUG][18] - Network Provider
2020-05-08 23:46:05.267 [DEBUG][18] Starting graph...
2020-05-08 23:46:05.268 [DEBUG][18] Calling LockChannel()
2020-05-08 23:46:05.268 [DEBUG][18] locked=0, present=0, strength=0, quality=0  (took 0ms to check)
2020-05-08 23:46:05.268 [DEBUG][18] DigitalRecorderDVBT::Tune@1
2020-05-08 23:46:05.268 [DEBUG][18] DigitalRecorderDVBT::Tune@2
2020-05-08 23:46:05.268 [DEBUG][18] DigitalRecorderDVBT::Tune@3
2020-05-08 23:46:05.268 [DEBUG][18] DigitalRecorderDVBT::Tune@4
2020-05-08 23:46:05.274 [DEBUG][18] DigitalRecorderDVBT::Tune@5
2020-05-08 23:46:06.902 [DEBUG][18] Unexpected error on DVB-T put_TunerRequest: 0x8000FFFF
2020-05-08 23:46:06.902 [DEBUG][18] DigitalRecorderDVBT::Tune@post
2020-05-08 23:46:07.152 [DEBUG][18] Calling LockChannel()
2020-05-08 23:46:07.152 [DEBUG][18] locked=0, present=0, strength=0, quality=0  (took 0ms to check)
2020-05-08 23:46:07.152 [DEBUG][18] StartStream()@exit handle=46
2020-05-08 23:46:07.153 [DEBUG][18] StartStream succeded. Handle: 46
2020-05-09 05:29:16.264 [INFO][15] Got GET request: /stream/stop?handle=46
2020-05-09 05:29:16.276 [DEBUG][15] About to request async graph stop
2020-05-09 05:29:16.278 [DEBUG][38] Graph stopping... (async)
2020-05-09 05:29:16.296 [DEBUG][38] Graph reports state 'Stopped'
2020-05-09 05:29:16.296 [DEBUG][38] Graph stopped (async)
2020-05-09 05:29:16.297 [DEBUG][15] Async stop completed successfully
2020-05-09 05:29:16.298 [DEBUG][15] Removing filter  MPEG-2 Sections and Tables
2020-05-09 05:29:16.298 [DEBUG][15] Removing filter  BDA MPEG2 Transport Information Filter
2020-05-09 05:29:16.298 [DEBUG][15] Removing filter  MPEG-2 Demultiplexer
2020-05-09 05:29:16.299 [DEBUG][15] Removing filter  NPVR TS Mon
2020-05-09 05:29:16.300 [DEBUG][15] Removing filter  Tuner
2020-05-09 05:29:16.301 [DEBUG][15] Removing filter  Network Provider

[sub]

It's just reporting the signal status at the start of the recording for later diagnostic purposes. It doesn't need to retry getting a signal lock. The device is tuned to the frequency for that whole time of the recording, and it'll any data that comes from the device at any time.

ie, on a channel with a normally good signal, if you unplug the antenna, then start an hour long recordings, then plug the antenna back in at about 30 minutes, you'll still get a file with 30 minutes of content.

[micmij]

Oh OK, thanks for the explanation. So, that begs the question - why did I get a zero byte file in the example above? The recording was set for about 6 hours and I was watching the program for part of that time on TV - there were a few dropouts here and there, but the signal was essentially coming through OK. Is the issue more likely to be at the device level (SD HDHomerun), rather than with the antenna?

Incidentally, I made another recording of similar length last night without any issues.

[mvallevand]

Perhaps if you had properly posted all the logs by the support rules https://github.com/sub3/NextPVR/wiki/get-help and not a snippet we would have a better answer.

FWIW my two HDHR devices do not have that have as good a tuner as some other devices I have. It could be the HDHR the antenna, the weather, the cable between the antenna and the HDHR, a splitter.

Martin

[Graham]

I was watching the program for part of that time on TV - there were a few dropouts here and there, but the signal was essentially coming through OK.

FWIW my two HDHR devices do not have that have as good a tuner as some other devices I have.  It could be the HDHR the antenna, the weather, the cable between the antenna and the HDHR, a splitter.

What he said ...

The tuners in computer devices are reckoned to be less sensitive than the tuners in televisions ... try some test recordings, perhaps overnight, after removing all possible splitters and extensions cables from the signal into the tuner.

[sub]

Oh OK, thanks for the explanation.  So, that begs the question - why did I get a zero byte file in the example above?  The recording was set for about 6 hours and I was watching the program for part of that time on TV - there were a few dropouts here and there, but the signal was essentially coming through OK.  Is the issue more likely to be at the device level (SD HDHomerun), rather than with the antenna?

In some ways the HDHomeRun devices are more complicated than other PCIe/USB devices, and who know how it behaves behind the scenes in this scenario. They fake having a BDA tuner, but they may have some differences from the regular behaviour. They may have some logic of their own, that says if it can't start delivering data in x seconds, then disconnect. Or it may just mean the tuner was in use by some other app when we initially tried to start it.

[micmij]

Sorry for the delay in replying - have been waylaid the last few days...

Thanks for all the replies - the consensus being that the issue is almost definitely with something other than the NPVR software, which is great! As it turns out, I've just found out that I need to move house shortly (hopefully, sorting out the antenna issue - though it could end up worse!) If I'm still running into problems, I'll look more closely into the HDHomeRun side of things. I'll try to report back when I get to the bottom of things.

Sorry about the logs.