Scan channel info

[VCR58]

When I perform a channel scan on a HDHR QAM tuner I see this which is correct but is not enough for me to to identify the station and edit the channel for the guide. What is missing is the tune frequency which is present in the HDHR setup gui. V4 includes tune freq info when I do a channel scan. ATSC tuner scans are not a problem since it always identifies the channel.

So, would it be possible to include the tune frequency somehow when a channel scan is done in v5?

v5 channel scan QAM tuner
[ATTACHMENT NOT FOUND]

HDHR setup gui of QAM tuner
[ATTACHMENT NOT FOUND]

[sub]

What does http://<hdhr-address>/lineup.xml from your hdhr return? ie, does it have anything useful that could be included?

Ultimately with QAM we're pretty limited because there is minimal information known. If the lineup.xml contains "CH85-9" or similar, I could make the channel names default to "Unknown CH85-9" if that would help?

[VCR58]

What does http://<hdhr-address>/lineup.xml from your hdhr return? ie, does it have anything useful that could be included?

Ultimately with QAM we're pretty limited because there is minimal information known. If the lineup.xml contains "CH85-9" or similar, I could make the channel names default to "Unknown CH85-9" if that would help?

Everything in the lineup.xml is shown in v5 so no help there.

Does the channel scan in v5 actually do a scan or does it just use the info provided in lineup.xml after HDHR does a scan? When v4 does a scan it looks like this...

[ATTACHMENT NOT FOUND]

[BrettB]

Everything in the lineup.xml is shown in v5 so no help there.

Does the channel scan in v5 actually do a scan or does it just use the info provided in lineup.xml after HDHR does a scan? When v4 does a scan it looks like this...

In v5 (and in some cases in v4), NPVR gets HDHR channels from the info in the lineup.xml coming from the HDHR's scan. (There is some support for legacy HDHRs which don't support the lineup.xml via BDA drives in Windows, but I'm not sure that's fully implemented in v5 yet. And I don't think that there is a way to force it to use that--it will only fall back to that method if the HDHR doesn't support the lineup.xml method.)

So you do want to get you channels scanned correctly in the HDHR Config before you try to setup the device in NPVR. We no longer have clear QAM cable channels here, so I haven't tried an HDHR with QAM. I'm thinking that since SD has their own guide service (for use with their app, etc.), their config probably has some way to specify/match that up. I'd suggest trying out some things in the HDHR Config and/or checking SiliconDust's forums for instructions on setting up QAM to see if you can find anything.

[VCR58]

Ok thanks for the suggestions.

I may abandon the QAM cable setup altogether and just go with OTA.

[mvallevand]

With a qam tuner that is not an HDHR you do get the frequencies in linux but that is not much help I still need to manually figure out what they are since they don't map to the stb channels that relocate them

Martin

[VCR58]

Ok I found something that I overlooked before. I can actually do both types of scans depending on which device I select.

Here are the tuners I currently have listed in the "Devices" page.

HDHR--HDHomeRun 10493842-0
HDHR--HDHomeRun 10493842-1
ATSC--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-0)
QAM--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-0)
ATSC--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-1)
QAM--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-1)

If I chick on the one called "HDHR--HDHomeRun 10493842-0" and do a scan, I get the Guide drop down menu with my SD lineups listed.

If I click on the one called "QAM--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-0)" and do a scan I get the drop down menu with the options for scanning physical channels like in v4.
So, here is what I see now.

[ATTACHMENT NOT FOUND]

[sub]

If I click on the one called "QAM--LocalRecorder (Silicondust HDHomeRun Tuner 10493842-0)" and do a scan I get the drop down menu with the options for scanning physical channels like in v4.
So, here is what I see now.

Yep, that's pretty much the same as how v4 did it.