No channels found on device scan

[mvallevand]

I don't now how the hdhr works but how could a firewall only let some channel data through? If he can record and view I think it could be signal quality or perhaps an ATSC stream that isn't being parsed well enough.

Martin

[GlenH]

That's one more puzzling part of this. How can NPVR log signal quality but not the channel info?
2012-10-22 20:50:25.468 [DEBUG][1] Frequency has changed, so stopping recording from previous frequency. (Handle 46)
2012-10-22 20:50:25.796 [DEBUG][1] Calling LockChannel()
2012-10-22 20:50:26.546 [DEBUG][1] locked=1, present=1, strength=100, quality=100 (took 750ms to check)
2012-10-22 20:50:26.546 [INFO][1] DigitalRecorder.StartStream() allocated handle: 0x2F
2012-10-22 20:50:26.546 [INFO][1] DigitalRecorder.StopStream() handle: 2E
2012-10-22 20:50:31.593 [INFO][1] DigitalRecorder.StartStream(c:\nowhere\null.ts)
2012-10-22 20:50:31.593 [DEBUG][1] Switching BDA graph to tune:
<tuning>
<type>ATSC</type>
<locator>
<physical_channel>49</physical_channel>
</locator>
</tuning>

2012-10-22 20:50:31.593 [DEBUG][1] Frequency has changed, so stopping recording from previous frequency. (Handle 47)

Shows 100 for strength and quality yet nothing for the actual channel data.
What is different about getting this data and the channel data?

Thank you.
Glen

[sub]

I don't now how the hdhr works but how could a firewall only let some channel data through? If he can record and view I think it could be signal quality or perhaps an ATSC stream that isn't being parsed well enough.

Recording and watching live tv requires the network data to get from the HDHR to nrecord.exe/ndigitalhost.exe. Scanning requires network data to get from the HDHR to nextpvr.exe. So depending on firewall settings, its possible to have scanning not working, while recording/tv on existing channels works fine.

I'm not sure of the reason, but the usual symptoms for HDHR scans failing due to firewall issues is the scan shows "locked=1" on all the correct frequencies, but never delivers any data, resulting in no channels found. I'm not sure how the HDHR communicates this "locked", but it might not involved network communication. ie, could be shared memory to one of the hdhomerun background services.

[johnsonx42]

The tuning and signal quality info comes through the driver, while the actual channel data flows directly over the network to nextpvr.exe (that's my guess/understanding of how it works... I'm in no way claiming I know better than sub does).

The very fact that you have this channel lock info, but no data being received, is the telltale that it's a firewall or *something* blocking nextpvr.exe from receiving the data (as sub already said as I was busy typing all this)

The other time we see something like this is if the user has left the application setting in the hdhr driver set to "GB-PVR" or one of the other apps instead of NextPVR. Now that I'm typing it though, I do recall one user saying that he couldn't scan with it set to NextPVR, and that he had to set it to "Other - ATSC" to make it work. This was many months ago, and was never explained since everyone else had it work set to "NextPVR" both before and since, but it certainly can't hurt to try. (in the early days of NextPVR, before the Silicon Dust drivers 'knew' about it, "Other-ATSC" was the setting everyone used)

[mvallevand]

Sorry for the head palm moment. GlenH what if you right click NextPVR.exe and use the run as administrator option? This often will bypass firewall permission settings.

Martin

[sub]

The other time we see something like this is if the user has left the application setting in the hdhr driver set to "GB-PVR" or one of the other apps instead of NextPVR. Now that I'm typing it though, I do recall one user saying that he couldn't scan with it set to NextPVR, and that he had to set it to "Other - ATSC" to make it work. This was many months ago, and was never explained since everyone else had it work set to "NextPVR" both before and since, but it certainly can't hurt to try. (in the early days of NextPVR, before the Silicon Dust drivers 'knew' about it, "Other-ATSC" was the setting everyone used)

Yep, this is definitely worth trying.

[GlenH]

The other time we see something like this is if the user has left the application setting in the hdhr driver set to "GB-PVR" or one of the other apps instead of NextPVR. Now that I'm typing it though, I do recall one user saying that he couldn't scan with it set to NextPVR, and that he had to set it to "Other - ATSC" to make it work. This was many months ago, and was never explained since everyone else had it work set to "NextPVR" both before and since, but it certainly can't hurt to try. (in the early days of NextPVR, before the Silicon Dust drivers 'knew' about it, "Other-ATSC" was the setting everyone used)

I have one of those "Other" cases!! Set it to "Other: ATSC/QAM" instead of NextPVR and I get channel data. Log attached.

Thank you!
Glen

[johnsonx42]

so can you still watch/record TV with it set to Other? or do you have to set it back to NextPVR?

[GlenH]

I have to set it back to NextPVR. At the Other setting it either sits with a blank screen or crashes NextPVR.

[whurlston]

Code:

2012-10-22 22:51:53.640    [DEBUG][1]    [b]FindFilterByName failed to locate filter: Microsoft Network Provider[/b]
2012-10-22 22:51:53.656    [DEBUG][1]    Using tuner Silicondust HDHomeRun Tuner 101C62B2-0 (1)
2012-10-22 22:51:53.656    [INFO][1]                [00000000-0034-0000-7038ea7934000000]-79ea3840-00000034

I would be curious to see if the other person that had this issue was also missing the new Microsoft Network Provider filter. I can't find the other instance though to compare logs.