Channel Detection Anomolies

[scaesare]

(this could go either here or the HDHomeRun HW forum, I think...)

I have recently moved homes and just re-installed my Silicon Dust HDHomerun FLEX Duo, and am attempting to reconfigure NEXTPvr (updated to v. 7.0.3.250920w/ updated NShared.dll, see below)  on Windows Server 2016.

I have the latest version (v. 20250815) running on the server as well.

I did a channel channel scan, and found 15 channels on both the HDHomeRun Config app, and in NextPVR for the two HDHomeRun device tuners.

I subsequently re-pointed my antenna, and now have slightly stronger signal strength on the initial channels, and can tune 3 more for a total of 18 in the HDHomeRun config app, and they play in the HDHomeRun. However, now when scanning in NextPVR, I detect half a dozen less channels (all the 3.X ones that have the Big 3 networks locally) than I initially did.  I've-readjusted and scanned to no avail, and can't get those channels to re-detect on HDHomeRun devices.

What's interesting is that the devices are also detected as ATSC tuners, and scanning there DOES detect the missing channels.

So. I am unsure why they are not detectable now on the HDHomeRun devices in NextPVR, when they were initially. I admittedly am unsure of the value of using the HDHR vs ATSC devices. I also have no cleared the existing HDHR channel lineup, out of fer of losing those six 3.X channels it initially detected.

(on another thread I saw a link providing an updated NShared.dll from the upcoming 7.0.4 build, and installed that, and unsure it's made any difference.

Any thoughts appreciated. Logs attached.

[mvallevand]

When you use hdhr mode you get the value from the Silicondust app scan, perhaps you didn't save after scanning.

Martin

[scaesare]

When you use hdhr mode you get the value from the Silicondust app scan, perhaps you didn't save after scanning.

Martin

I did, several times.

Just to be sure, I just now logged back on to the server running NextPVR and ran the HDHR Config GUI, and the channel lineup had the channels in question, so it had saved them from the detection yesterday. I then just re-scanned channels for the HDHR device in NextPVR, and it doesn't find them.

I haven't saved the new scan results in NextPVR, as I still have the channels in question listed as somehow they were detected initially, and I don't want to lose them.

As a sanity check, I just selected one of the channels in question in my NextPVR Kodi client, and am watching as I type, so it's obviously there and working.

So, the HDR Config app sees them. The HDHR TV app can watch them. NextPVR can find them as ATSC. It once found them as HDHR channels, and those previously dectted channels obviously work and are viewable via NextPVR.

The HDHR config and setup apps have all been closed and reopened to verify the previously detected channels were saved.

I can't figure out why they can't be detected as HDHR device channels now...

Incidentally, NextPVR v. 7.0.3.250920 was listed as available, so I upgraded. No change.

For completeness, attached is a screen shot with the HDHR Config app channel lineup running on the NextPVR server next to the results of an NextPVR HDHR scan.

[mvallevand]

I am away so not looking at logs with free wifi but you need to pick either HDHR mode or ATSC and stick with one.  . There are many reasons ATSC mode but ensure you have the latest Silicondust setup to use the NextPVR mode driver if you must use it.

If HDHR is not being discovere that is likely firewall or VPN related or you need to click rescan.

Martin

[scaesare]

I am away so not looking at logs with free wifi but you need to pick either HDHR mode or ATSC and stick with one.  . There are many reasons ATSC mode but ensure you have the latest Silicondust setup to use the NextPVR mode driver if you must use it.

If HDHR is not being discovere that is likely firewall or VPN related or you need to click rescan.

Martin

- Deleted the ATSC channels, re-scanning the HDR devices, still cannot find the channels in question (the 3.x ones).

- Latest Silicon Dust drivers installed on same server NextPVR is running on. HDHR Setup app has "BDA Compatabiliy Mode: NextPVR" set (see screenshot)

- SiliconDust hardware and NextPVR on same LAN subnet with no FW (host or otherwise)or other devices between them. The toplogy hasn't changed in the 48 hours since NextPVR was originally able to detect the channels.

-Note that in attached screen shot the HDHR Setup app that sees the channels is on the same server the NextPVR service is running on.


Thanks for chiming in with ideas... I am flummoxed.

[mvallevand]

If you untick them does that change anything?

[scaesare]

If you untick them does that change anything?

I'll try that, but unsure where you mean? 

There are tick marks next to the channels currently found in the NextPVR Setting/Channels page, I tried unticking them there, and re-scanning in the Settings/Devices/HDHR page, no change in detected channels.

Unless you mean somewhere else?

(Incidentally, I also found that by holding down CTRL you can disable devices. Did that and diasbled the ATSC & QAM tuner devices, leaving only HDHR... no change)

[mvallevand]

The yellow stars that are checked.

[scaesare]

The yellow stars that are checked.

Oh, those are just "favorites" in the HDHR Config GUI app. Nonetheless, I de-selected them and rescanned in NPVR, no deal.

I appreciate you slogging thru this...

(Incidentally, restarted the NPVR service as well, no change)

[mvallevand]

I meant check the ones you want but I lost Internet, I think only favourites are imported.

Martin