Channel not Locked behaviour

[Petrovski]

Changed to Win8 a few weeks back and have had a few zero length recordings due to channel not locking.

2012-11-18 18:59:03.233 [DEBUG][4] Calling LockChannel()
2012-11-18 18:59:03.237 [DEBUG][4] locked=0, present=0, strength=80, quality=0 (took 16ms to check)
2012-11-18 18:59:03.237 [DEBUG][4] DigitalRecorderDVBT::Tune@8
2012-11-18 18:59:03.241 [INFO][4] DigitalRecorder.StartStream() allocated handle: 0x1
2012-11-18 18:59:03.253 [DEBUG][4] Temp at 18/11/2012 18:59:13
2012-11-18 21:02:00.052 [INFO][236] DigitalRecorder.StopStream() handle: 1
2012-11-18 21:02:00.453 [INFO][236] No more streams active. Stopping device.

Now that's probably not NPVR's fault but what I'm thinking is shouldn't NPVR retry or restart service automatically instead of staying in record mode for the full duration? I find that restarting the service picks up the channel. [I guess that's not the best solution if another recordings are in progress]

[sub]

It will retry the recording if it noticed an error like a device failing to hook up, or failing to run etc. Unfortunately locked=0 isn't considered a failure though, since some devices return this even when they're correctly locked onto the signal and delivering data.

[Petrovski]

Hi Sub
Ok some devices don't return reliable info but mine does [and probably others too]:
locked=1, present=1, strength=80, quality=100 (took 156ms to check)
So maybe there this could be an optional feature?
[A "no data flowing" check might allow all devices to be supported?]
Thanks