Recording failed. No errors, but no data delivered

[ozhans]

Hi,

I'm new to NextPVR and started using it to replace WMC.
I noticed that some recordings are failing, but I can't find errors in the log files.
NextPVR is recording to a NAS, the computer is running W7 Pro 64 bit with a network cable connected to the same switch as the NAS is connected to. The computer can access the NAS fine. Enough free space on the NAS as well. Computer has 2 dualport USB tuners attached and all 4 tuners are configured in NextPVR.
Examples of failed recordings (all of them are series recordings and .ts files are 0 bytes):
Neighbours Eleven 16/1/2016 12:59PM-1:49PM
Neighbours Eleven 16/1/2016 12:29PM-1:19PM
Around this time other Neighbours episodes recorded fine 11:29AM-12:19PM + 11:50AM-12:49PM + 1:29PM-2:19PM

Mythbusters SBS TWO 15/1/2016 8:55PM-10:10PM
Other programs around this recorded fine as well:
DCI Banks ABC 8:27PM-10:18PM + Escape to the country 7TWO 15/1/16 9:25PM-10:47PM

Attached are the relevant ndigitalhost and nrecord logfiles, please let me know if additional information is required as I can't work out what's happening here.

[sub]

Do you have some other log files? It looks like the mythbusters recording was attempted on a different device than the one you provided the logs for.

[ozhans]

Sorry Sub, more logs attached now

[sub]

It looks like you've got a few failed recordings on a device called 'IT9135 BDA Filter'. It looks like it probably has no signal. What is the manufacturer and device is this?

[ozhans]

Thanks for that Sub, it's a Digitalnow Tinytwin USB received, USB stick with 2 receivers built in. I have 2 of them plugged in at present, but different models, so I will check which one this is and remove it and plug it back in.
Is there a way I can test the signal for just this device with NextPVR?

[sub]

Is there a way I can test the signal for just this device with NextPVR?

Sorry, no there isn't.

[ozhans]

No worries, thanks Sub. I have unplugged the device and plugged it back in, re-scanned devices in Windows and restarted the computer hopefully that will fix it. Which log should I check to see if it happens again? It might be a hardware issue in which case I will contact the supplier since it's still under warranty.

Another question if you don't mind, the default recording location is set to a NAS device while the second option is set to the local computer d: drive. I noticed before when the NAS is turned off, it will change the default location to c:\users\public instead of using the second location. But from reading other posts, the locations can be used for specific recordings or whichever does have most space available.
However when I move the recordings from the local computer back to the NAS, it looks like the metadata is lost. From reading other posts I can export and import recordings to get the metadata back, but just found the settings to keep the metadata with the recording, so I will give that a go.
Basically what I would like to achieve is this (but I'm not sure if it's possible):
- default recording is to the NAS
- when the NAS is not available record to local d: drive
- when recordings are moved from the local d: drive to the NAS, the metadata should be maintained with export/import recordings

Hans.

[Graham]

Which log should I check to see if it happens again?

Simply stated NextPVR runs three components. NextPVR is the part that you see on screen to view the Guide and watch recordings and do Settings and all that. Ndigitalhost tasks run as required and are the software that connect to the tuner and transfer data from the tuner to the hard drive for recordings (and for Live TV, but that's another story). The Recording Service runs continuously and kicks off scheduled tasks like creating a recording. The Recording Service is also the interface between the NextPVR frontend and the ndigitalhost tasks. The NextPVR frontend log is npvr.log, The Recording Service log is nrecord.log. There is one ndigitalhost log for each tuner and create logs called ndigitalhostNN where the numeric is consistent so, for example, ndigitalhost20.log will always be the log for the same tuner. You can rename the tuners in Settings --> Devices if that would help identify one from another but that won't change the names of the ndigitalhost log files.

Edit: A new log is started when a task starts and the immediately prior log is renamed to .1 and .1 is renamed to .2 and so on. Plus there is an upper size limit for logs and and a log is closed and a new log starts when the size limit is hit.

[ozhans]

Thanks for that Graham!

[jcjefferies]

I have had one of those IT9135 tuners (Kworld UB499-2T) for several years and had a problem with one tuner going off line about every 4 weeks. A reboot didn't cure the problem but unplugging for a few seconds did. The problem was that the power was always on the USB connectors when the server went into Sleep or Hibernation so the tuner was always on. I never found a way to force power down of the USB sockets. My current server powers off the USB sockets when the server hibernates so don't get the problem any more!

Chris