HDHR/digital tuning in v6.5 & later

[technazz]

Originally Posted by Opus4

In v6.4.5, did you just try to change the lineup for the existing source, then? I can see that not working if you had previously set up QAM on the HDHR using the old method of selecting Antenna for the tuning option. I should probably update the instructions to say to remove the old HDHR source if coming from the old setup style. Maybe you could just do a full reconfigure w/o first removing it, unless that is what you tried.

Yes I had a working setup with the Antenna option. I was able to change it to cable in the Source details. I shut down and restarted but that didnt work until I removed the source, restarted sage and added it again.

Originally Posted by Opus4

The HDHR scan creates the .scn file & SageTV's scan uses the info in that file to create the .frq file. So, if there is no scn file, SageTV's scan won't work properly for QAM on the HDHR in Windows.

You can, however, copy the scn file for one HDHR tuner (or other QAM tuner) to the scn file for another tuner & continue form there. That was a tip I was going to add, based on feedback I've seen.

- Andy

Yes the tip would have saved me a few minutes and a couple of hair pulls!

Thanks

Technazz

[taylork]

Posting this for folks who might be having issues working w/ this beta, the new DLL and the new STV...

I finally got around to installing on my primary machine last night and I had to add "QAM" to the sage.properties file as mentioned here.

[Opus4]

Originally Posted by taylork

Posting this for folks who might be having issues working w/ this beta, the new DLL and the new STV...

I finally got around to installing on my primary machine last night and I had to add "QAM" to the sage.properties file as mentioned here.

While I don't believe that property setting will actually hurt anything, I still say it shouldn't be needed & if you need to make that change, then something may not have been updated correctly. After updating the DLL, SageTV must be restarted & that is one possible cause of this. Another is to make sure the DLL is in the proper location -- if it isn't replacing an existing file, then it isn't being put into the correct directory: <SageTV install path>\SageTV is the correct location on the SageTV server PC.

But, updating the DLL will not be needed after the next SageTV version is released because all of SageTV's files will be up to date after that.

- Andy

[Conejo]

Originally Posted by taylork

I had to add "QAM" to the sage.properties file as mentioned here.

On my last test install, I removed "QAM" from my properties files (I even set some properties to ATSC and ANTENNA to verify they'd get updated) then installed the latest .dll and used SageTV to download the STV. Everything worked like Andy said, no need to add the "QAM" line.

I've encountered a couple of instances during test setups where I've needed to stop/shutdown SageTV and restart for everything to work, but that's been it.

[jbuszkie]

GRrr.. I believe I followed all the instructions and my scan within sage isn't working. It's like it's not seeing the SCN file (which I confirmed was there...)

Anythoughts on how I should procede..

The channel scan starts at 0 and then slowly goes to 1 then 2 and I never let it go past 10 but that's been about 5 minutes already...

Jim

[Opus4]

SageTV's scans for the HDHR tuners shouldn't take that long.

What version of the HDHR software are you using?

In the HDHR Setup program's Tuner tab, is it configured for SageTV? You said the scn file is getting created... have you double checked its timestamp & is it in the SageTV directory where sage.properties is? Check the scn file's contents -- does it contain anything?

If upgrading from a previous version of SageTV, have you removed the configured source before trying to reconfigure it? Did you run the new version of SageTV before running the HDHR setup program?

Depending on some of those things, I may want to see the debug logs and scn/frq files.

- Andy

[jbuszkie]

Originally Posted by Opus4

SageTV's scans for the HDHR tuners shouldn't take that long.

What version of the HDHR software are you using?

The latest from 7/23

Originally Posted by Opus4

In the HDHR Setup program's Tuner tab, is it configured for SageTV? You said the scn file is getting created... have you double checked its timestamp & is it in the SageTV directory where sage.properties is? Check the scn file's contents -- does it contain anything?

Yeah.. It looks like it has all the stuff I just setup.. and it's in the right spot.

Originally Posted by Opus4

If upgrading from a previous version of SageTV, have you removed the configured source before trying to reconfigure it? Did you run the new version of SageTV before running the HDHR setup program?

This was a fresh install of 6.4.5 I did run it with older HDHR software...but I upgraded the HDHR. I have removed the source many times.. I even tried to delete the .frq file.
I also manually removed the encoder info from the propertied file.
Still it doesn't seem to find the SCN file is my guess..

Jim

[Opus4]

Originally Posted by jbuszkie

The latest from 7/23

I haven't used that version myself.

This was a fresh install of 6.4.5

But, did you run the new version of SageTV before running the HDHR's setup program? SageTV has to be run before the HDHR app so the HDHR app can determine the SageTV version in use.

If you provide the logs & scn files, I'll see if I notice anything. Be sure to add the logging property to sage.properties and sageclient.properties, if using service mode... or for whatever client UI you are using for the SageTV setup process.

- Andy

[Grasshopper]

Originally Posted by jbuszkie

The latest from 7/23


Yeah.. It looks like it has all the stuff I just setup.. and it's in the right spot.

This was a fresh install of 6.4.5 I did run it with older HDHR software...but I upgraded the HDHR. I have removed the source many times.. I even tried to delete the .frq file.
I also manually removed the encoder info from the propertied file.
Still it doesn't seem to find the SCN file is my guess..

Jim

I'm in the exact same situation.

Don

[jbuszkie]

Here is the log and the SCN file..

I even uninstalled Sage and reinstalled sage. (and updated the STV and the DLL file..) IT still takes forever with the scan.

Thanks,

Jim

[Opus4]

By any chance, did you have the native log enabled too? If not, could you enable that, then retry the HDHR setup in SageTV? Thanks.

To enable native.log: create an empty file named "NATIVE_LOG.ENABLE" in the SageTV directory, then restart SageTV & "native.log" will then be created.

It does seem to be ignoring the scn file, but if it is in the correct directory, I don't know why that would happen. I think I'll have to pass these files on to someone else.

Oh, and you could always try that QAM property setting mentioned a few posts before yours. If that solves it, something weird is going on.

- Andy

[jbuszkie]

That did it...

the native log clued me in...

07/24/2008 00:08:10 Can't open 'Silicondust HDHomeRun Tuner 10140C90-0-0-QAM-scn' to load scan data for tuner.

It seems like it wanted -scn file.. and HDHR names it .scn.
I renamed the .scn file to -scn and it worked! Someone put a '-' instead of a period '.' in the sage software.. or the HDHR guys put a '.' where you guys were expecting a "-" So who's fault is it?

Damn that's a lot faster when it used the scn file! I actually let it finish the slow scan and it took ~30-40 minutes.. The SCN file was about 30 sec!

[Opus4]

Originally Posted by jbuszkie

the native log clued me in...

07/24/2008 00:08:10 Can't open 'Silicondust HDHomeRun Tuner 10140C90-0-0-QAM-scn' to load scan data for tuner.

It seems like it wanted -scn file.. and HDHR names it .scn.
I renamed the .scn file to -scn and it worked!

Thanks for the info -- that's not what the file has been named, so I'll pass it along.

Keep a copy of the file that ends in .scn in that dir, because that is what it should be & the next update will probably find it that way.

- Andy

[Conejo]

In the Tuner setup, make sure you've selected 'Antenna' for use with ATSC.scn files; 'Cable' for use with the QAM.scn files.

Sage will attempt to do a 'live scan' then the associated .scn files are missing. This won't work with QAM lineups.

[edit] nevermind. Ya know, I read that entire file and didn't catch that. I even stared at it for 2 minutes and didn't know why it was skipping it.

[Opus4]

BTW: the DLL file in the first post has been updated so that it looks for the ".scn" file again. I haven't had a chance to try it, so if there are issues, let me know.

- Andy

[Crunch]

What a mess up.

I did a quick update yesterday over the top of my old system.. and was happy. Decided with the non beta release from Silicondust today to do a clean install. Started at 7pm its now 2am.

Got to the scan in SageTV and hit a wall all night. Yesterday the scan took less than a minute.. now it has been running for nearly an hour... Logged on and I see the . - issue.

Someone messed up.

Anyone thinking of an install, I would hold off

I just changed my filenames from . to - and back to a 30 second scan but not all the channels are showing and I need some sleep.

This will go down as the biggest stuffup I have had with my HDHR and SageTv in two years.

Edit
So how often has the DLL file been changed? Is that the cause of this problem??
What files do i use to do my next install??

[Crunch]

fresh install at 7am this morning same issue

[Grasshopper]

I spent about 5 hours last night trying to get the new HDHR software/firmware to work with the new Sage beta, and experienced the same failures as the others above. Woke up this morning and read the new posts about replacing the .scn with -scn files. Duped the files and renamed them, and Sage found all the channels with a (fast) scan. That's the good news.

Here's the bad news. The channel lineup that I used to set up the HDHR tuners was the same one that I'd used from the previous configuration of the HDHR's, and had all of the manual channel remappings from before. So the channel scan was successful, but all of the channels were mis-mapped. I had to go through the list and manually remap all of them.

It works, but it's not exactly an improvement in ease of installation. Is there any way to avoid that remapping process?

[Opus4]

Originally Posted by Crunch

fresh install at 7am this morning same issue

What's the same issue? The current DLL should be looking for the .scn file again. If it isn't, then it still needs to be fixed.

If you mean that some channels aren't tuning, then contact support for follow-up on that.

Originally Posted by Grasshopper

Here's the bad news. The channel lineup that I used to set up the HDHR tuners was the same one that I'd used from the previous configuration of the HDHR's, and had all of the manual channel remappings from before. So the channel scan was successful, but all of the channels were mis-mapped. I had to go through the list and manually remap all of them.

It works, but it's not exactly an improvement in ease of installation. Is there any way to avoid that remapping process?

What was mapped incorrectly? The physical channel number or the logical number? i.e.: were they not tuning properly, or were they just at the wrong channel number in the guide? The physical number should be correct; it may be possible that existing logical remaps are being used so that what looks like your preferences don't get changed.

- Andy

[Grasshopper]

The physical channel numbers were incorrect. I reentered all of them manually, referring to the -scn file written by the HDHR.