NextPVR Recording service creates zero length file, high CPU utilization

[zb21]

If it was the network trafic why this works sometimes? And why can I always record after manually restarting the recording service?

I guess there is something missing in the NPVR configuration file in the way how it does the channel scan. When I open HDHomeRun Config utility I see only two devices: 122028CB-0 and 122028-1. Then in Configuration/channel I can select eu-bcast, eu-cable, au-bcast, au-cable, tw-bcast and tw-cable. My guess would be that somewhere in NPVR the configuration file is incomplete and does not contain all parameters of eu-bcast. For that reason NPVR can not find any channels. That config file may be different and OK for Prime tuner, which shows up for some reason in the device selection.

Another thing is that this 'almost' works as a Prime tuner, but this 'almost' has a small bug, most likely the tuners are not properly released and when the new recording starts NPVR 'thinks' there is no tuners available and waits, also causing high CPU utilization due to some other bug.

Please let me know if there is another way to find out what is the problem. Another log files, another diagnostic software etc?

ZB21

[zb21]

BTW NextPVR and NRecord.exe are in the Exceptions list of my Windows firewall.

[sub]

If it was the network trafic why this works sometimes? And why can I always record after manually restarting the recording service?

I'm pretty sure it's never working when you use the DVB-T/C options. It's only ever sometimes worked when you're using the HDHomeRun Prime capture source option, which is slightly different, and not intended to work for your European DVB-T HDHR.

Scanning the HDHomeRun DVB-T source needs network traffic to get from the HDHomeRun to NextPVR.exe. Scanning with the HDHomeRun Prime source did not need network traffic - instead it just runs hdhomerun_config.exe and captures the output.

I guess there is something missing in the NPVR configuration file in the way how it does the channel scan. When I open HDHomeRun Config utility I see only two devices: 122028CB-0 and 122028-1. Then in Configuration/channel I can select eu-bcast, eu-cable, au-bcast, au-cable, tw-bcast and tw-cable. My guess would be that somewhere in NPVR the configuration file is incomplete and does not contain all parameters of eu-bcast. For that reason NPVR can not find any channels.

Thats not the case. There is no configuration file for these devices at all. NPVR just treats all DVB-T devices exactly same, and the BDA standard specifies that they should all behave the same. This works fine for me, and other HDHomeRun users, so I'm pretty sure the app is fine, and it'll just be the same types of things that always trip up HDHomeRun users (firewall).

The SiliconDust config utility allows you to select eu-bcast, eu-cable, au-bcast, au-cable, tw-bcast and tw-cable. NPVR does the same, but it might not be obvious you. The "cable/bcast" bit is like choosing between DVB-T and DVB-C. The "eu/au/tw" part is selecting a table of frequencies to scan, ie in NPVR you choose a country and region to get a list of the frequencies in your area.

Another thing is that this 'almost' works as a Prime tuner, but this 'almost' has a small bug, most likely the tuners are not properly released and when the new recording starts NPVR 'thinks' there is no tuners available and waits, also causing high CPU utilization due to some other bug.

Sorry, the Prime option isnt going to work for you. I'm intending to hide it in the next release to avoid any confusion.

Please let me know if there is another way to find out what is the problem. Another log files, another diagnostic software etc?

You could try creating a c:\temp directory, and setting HKEY_LOCAL_MACHINE\Software\NPVR\LogTSFlow=1, then start the app and scan on the DVB-T device, and post the npvr.log and c:\temp\mon.txt

[zb21]

I attached the mon.txt log file (nothing really in there ???).

Thank you again for your time,
ZB21

[sub]

You forgot to also attach the npvr.log.

That log is pretty much showing what I guessed though. Not a single byte of data is delivered from the drivers to NextPVR.exe. It sure looks exactly the same as when other users have had firewall issues.

[zb21]

I do not disagree with your diagnosis, I just don't know what to do ???
One puzzling thing for is that hdhomerun_config also has to communicate over the network with the device, and it does that (as I can watch the TV and even 'sometimes' record). I am just running out of ideas....

For now I also attached the npvr.log file.

Thank you again for your time and help,
ZB21

[sub]

I do not disagree with your diagnosis, I just don't know what to do ???

I'm not really sure what to suggest. I'm no expert in firewall software etc. In the past we've had some users find they were unexpectedly using two firewalls, for example ZoneAlarm and the built in XP one, so even though they'd been attempting to configure things in ZoneAlarm, the XP one was still blocking the connections.

Also could be caused by netnanny type software, or sometimes antivius software. These types of utilities can also block network connections.

One puzzling thing for is that hdhomerun_config also has to communicate over the network with the device, and it does that (as I can watch the TV and even 'sometimes' record). I am just running out of ideas....

The SiliconDust installer does setup all sorts of firewall exceptions when the software is installed, but unfortunately this is only done for their own software and for Windows Media Center.

[Reddwarf]

@zb21: I don't remember XP's firewall setup well, but isn't it possible to see what ports are open for the native software (and Mediacenter) in the firewall's configuration? If so you can open the same ports for NextPVR.exe and Nrecord.exe. I remember having cases of XP firewall when I explicit had to open gbpvr's ports, ie just adding PVRX2.exe to the firewall's exception was not enough. I never figured out why.

[jcjefferies]

As its XP and seems to be a twin tuner have you tried installing DVBfix?

[nobody]

Something else to check?

SiliconDust HDHomeRun
In the SiliconDust driver configuration, there is an option to set the Application you'll be using with it. Do not set it to GB-PVR; you will not be able to scan for channels. Instead, set the application to "Other".

http://forums.nextpvr.com/showthread.php...arted-info