Win 10, new PC -> Scan shows no channels for HDHomeRun

[wtg]

In the US, trying to setup NextPVR again after years of absence. New stick Lenovo PC with Win 10.

Installed latest HDHomeRun software and firmware, ran it's setup and scanned for Clear QAM channels. Worked fine and I can view the channels using HDHomeRun software.

Next, installed NextPVR. During Scan for channels none are found. Disabled firewall completely to make sure that wasn't the cause of trouble, and tried scan with BDA Compatibility Mode setting as Default and NextPVR. No dice.

I've attached the logs. Maybe the interesting part is the error shown below, repeated for each channel:

Code:

2016-07-09 13:14:36.100    [DEBUG][1]    About GetTuningString() : 71
2016-07-09 13:14:36.100    [DEBUG][1]    transponderInfo: 71,0,0
2016-07-09 13:14:36.100    [INFO][1]    DigitalRecorder.StartStream(c:\nowhere\null.ts)
2016-07-09 13:14:36.100    [DEBUG][1]    Switching BDA graph to tune:
<tuning>
  <type>QAM</type>
  <locator>
    <physical_channel>71</physical_channel>
  </locator>
</tuning>


2016-07-09 13:14:36.100    [DEBUG][1]    Frequency has changed, so stopping recording from previous frequency. (Handle 390)
2016-07-09 13:14:36.100    [DEBUG][1]    tune@1
2016-07-09 13:14:36.100    [INFO][1]    Setting locator to BDA_MOD_256QAM


2016-07-09 13:14:36.100    [INFO][1]    Tuning to frequency 71
2016-07-09 13:14:36.140    [DEBUG][1]    About to try setting tuner modulation
2016-07-09 13:14:36.140    [DEBUG][1]    Got tuner output pin
2016-07-09 13:14:36.140    [DEBUG][1]    Unable to get IKsPropertySet interface
2016-07-09 13:14:36.140    [DEBUG][1]    Resetting metadata
2016-07-09 13:14:36.140    [DEBUG][1]    About to submit tuning request
2016-07-09 13:14:36.250    [DEBUG][1]    Resetting metadata
2016-07-09 13:14:36.250    [DEBUG][1]    whoosh whoosh
2016-07-09 13:14:36.250    [DEBUG][1]    tune@2
2016-07-09 13:14:36.260    [DEBUG][1]    Calling LockChannel()
2016-07-09 13:14:36.260    [DEBUG][1]    locked=0, present=0, strength=0, quality=0   (took 0ms to check)
2016-07-09 13:14:36.260    [DEBUG][1]    File size is 0 bytes (non-existant)
2016-07-09 13:14:36.260    [INFO][1]    DigitalRecorder.StartStream() allocated handle: 0x187
2016-07-09 13:14:36.260    [INFO][1]    DigitalRecorder.StopStream() handle: 186
2016-07-09 13:14:38.294    [INFO][1]    Metadata:
</sdt>


2016-07-09 13:14:38.294    [ERROR][1]    Unexpected end tag. Line 1, position 3.:
</sdt>

Any thoughts on what I should try next?

Thanks,
Tim

[sub]

Try this patch:

http://forums.nextpvr.com/showthread.php...post504758

[wtg]

This seemed to have resolved the issue... thanks!!

[sub]

I've now updated the installer to include that patch.

[rnwells]

I have the same problem. NPVR Live TV is blank. I upgraded to Windows 10 Pro with a Silicon Dust tuner and a Cox cable card. NextPVR worked well under Windows 8.1.
I upgraded to Windows 10 and followed instructions to reinstall NPVR. I can view Live TV with WMC, HDHomeRun View and Kodi with good video and sound. NPVR setup
found all the channels and lists the tuner as a source but cannot view them. I have tried all the suggested video decoders. I have enabled NPVR in the firewall. Suggestions?

[sub]

I have the same problem. NPVR Live TV is blank. I upgraded to Windows 10 Pro with a Silicon Dust tuner and a Cox cable card. NextPVR worked well under Windows 8.1.
I upgraded to Windows 10 and followed instructions to reinstall NPVR. I can view Live TV with WMC, HDHomeRun View and Kodi with good video and sound. NPVR setup
found all the channels and lists the tuner as a source but cannot view them. I have tried all the suggested video decoders. I have enabled NPVR in the firewall. Suggestions?

If you try recording a show from the guide, do you end up with a file getting created, and does it have a size of bigger than zero bytes?

[rnwells]

No file is created.

[sub]

I'd take another look. It's unlikely a file is not being created.

If you're sure it's not being created, then look into the permissions you've got on the recording directory you've specified.

If the file is created, but zero bytes, then there is other stuff we'd have to look at.

[rnwells]

No file. It says failed because no signal.

[sub]

Try doing a recording then post the logs and we'd take a look.

Typical creating the file isn't usually a problem...whether you end up with anything in that file comes down to receiving data from the HDHomeRun. If it stays zero bytes, then you sometimes need to check BDA Compatibility mode setting in the HDHomeRun setup utility, or check the firewall is letting data through, or that the HDHomeRun has a real signal.

For no file, you need to check that the recording directory really exists, and that the application has the permission to create files in that directory