What is this error?

[Kiwi]

What is this error?

"No errors, but no data delivered. This is usually because the device failed to lock a signal."

[sub]

It's pretty much what is says. ie, it tried to do the recording, and everything went fine, there were no errors, but the device never delivered any data, so you ended up with a recording that was zero bytes long.

[Kiwi]

It's pretty much what is says. ie, it tried to do the recording, and everything went fine, there were no errors, but the device never delivered any data, so you ended up with a recording that was zero bytes long.

Is this caused by the signal or the TV card?

So far, I seem to identify a trend that the card stops receiving signal at about 8.40pm on Fridays, so I don't think it's the card problem. Could be the signal problem, yes.

However, I have had to reboot the system in order to get the card to start receiving the signal again. So I'm confused on what to do next.

[sub]

Is this caused by the signal or the TV card?

Yes, one of those two. Unfortunately I've got no way to know which.

[Kiwi]

I would like to check again on the handling of the error.

Does the NextPVR program keep retrying to initialise the tuner and recapture the signal for each scheduled recording, or once the above error is detected, NextPVR will ignore the tuner and not do any more initialisation?

[johnsonx42]

post your logs, make sure all the ndigitalhost-xxxx and NRecord logs are included. also identify a specific recording where the problem happened, and hopefully where in the log to find it.

based on your description I'd say the tuner driver is probably locking up somehow; depending on the exact nature of the lockup, the tuner may work again for the next recording, or it may be dead until you reboot. NRecord takes several steps to recover from this type of problem, but it's not always possible.

[Kiwi]

post your logs, make sure all the ndigitalhost-xxxx and NRecord logs are included. also identify a specific recording where the problem happened, and hopefully where in the log to find it.

based on your description I'd say the tuner driver is probably locking up somehow; depending on the exact nature of the lockup, the tuner may work again for the next recording, or it may be dead until you reboot. NRecord takes several steps to recover from this type of problem, but it's not always possible.

I notice that the tuner is never recovered upon the first error.

Ok I will try to capture some logs.

[martint123]

I've had a couple of TBS tuners in the past and found that the drivers were a bit fragile. Once it had stopped delivering data the only way to record again was a power reset.

[Kiwi]

I've had a couple of TBS tuners in the past and found that the drivers were a bit fragile. Once it had stopped delivering data the only way to record again was a power reset.

My experience was that just a device disable/enable would do.

[Handy.Man]

Is this caused by the signal or the TV card?

So far, I seem to identify a trend that the card stops receiving signal at about 8.40pm on Fridays, so I don't think it's the card problem. Could be the signal problem, yes.

However, I have had to reboot the system in order to get the card to start receiving the signal again. So I'm confused on what to do next.

I had issue with a tuner that became disable around a specific time ....
Watching Hauppauge Signal monitor during that time period, I found that something was grabbing the tuner and this broke recordings.

I disabled Windows Media Center, something called Windows User Experience, Hauppauge WinTV server, etc and the problem disappeared