How to get HDHR QAM working with v6.2

[Conejo]

Originally Posted by egeller

I wrestled with opening ports. Every time I restarted the service, SageTVService was selecting a different set of UDP ports for the two HDHR tuners.

I finally discovered an operator error. I had put an exception in the firewall for SageTV and SageTVServiceControl, but not the SageTVService (not sure what I was thinking when I created THAT exception, I must have been looking at it cross-eyed).

I added the SageTVService to the exception list and was able to restart SageTV and SageTVService without having to open up any UDP ports. I'm cautiously optimistic that I won't need to address any more port issues.

Yeppers, since I hadn't stopped and started the service I didn't see this problem. Adding the 'SageTVService' using the Exceptions -> Add Program|Browse option solved it.

I'll edit my second post to update this. -c

[Conejo]

Interesting...
Just lost a bunch of my San Francisco stations. But all my other QAM channels are were coming in fine.
I was about to tear apart my system looking for a driver error when I decided to double-check the remap and view the channel. All the lost stations are on the 255Mhz carrier frequency (QAM 29). Checked the HDHR Gui and there's no signal level at that frequency.

Stupid Comcast must be doing something on that carrier frequency.
I almost tore my system apart for nothing. Glad I checked for a source signal first.

Sorry for the multiple posts. Oh look, a squirrel!

[Polypro]

Originally Posted by Yooper

I am so confused at this point.....!

I see posts on ports, remapping, scanning, and a lot of other suggestions. Some report that these things work, and others have no luck.

All I know is that my HDHR does not work, neither does the QAM on my 1600 - although I can see video on both boards using the vender software, not Sage.

These things worked in previous versions.... Not in 6.2.7 and the latest HDHR software.

I think I will wait for the next release....

As far as the HVR1600, have you added the newer dshowcapture.dll that was posted? Aparrently that allows the 1600 to scan properly in 6.2.7

P

[Yooper]

I'm making a little progress.

O got some of the HDHR channels working using the 3 digit remap numbers. I remapped the channels that worked before using the channel editor numbers, but on 2 of the 4 channels actually work.

I haven't done any more work on the QAM channels on the 1600 card.

[Crashless]

I was able to get my new HDHR running with clear QAM last night with relative ease on my Vista server.

Here's how I did it:

I used the Setup Utility and went to the 'lineup' tab and ran the channel editor's 'Scan' function which took FOREVER (15 minutes+) but eventually found a bunch of channels that I was able to view using VNC.

I then went down this list and only enabled the channels I wanted (there are a lot of foreign language channels in my area) and used the 'Zap2It' guide to figure out which channels were which call letters and changed the 'UNKNOWN' to that particular call letter. (ie: KTTVDT, KCBSDT etc) I also changed the drop-down menu for each channel I enabled to 'normal'.

After I finished that, I hit save and quit the program and the manager utility, and went and found a lineup.xml file in the C:\Program Data\SiliconDust\HDHR\ folder and opened it.

Then I started SageTV. I added the first tuner, (it looked like the one highlighted in an earlier post, and didn't have an IP in the name) selected 'turn CableTV' and used the 'Digital Tuner'.

Then I selected a different channel lineup than I was currently using (from an adjacent city), disabled all channels and found the digital channels (mine were listed in the 600's of this particular lineup.) I selected 'remap' and changed the physical channel number (NOT LOGICAL) to match the <RemapTrigger></RemapTrigger> number from the lineup.xml file. Only the channels you enabled in the channel editor will have this field, and it begins with the number 2 and goes up from there.

You should now be able to hit 'View' and see a preview of that channel. Be sure to enable that channel. (it will have a green dot next to it.)

Repeat that process for each of your QAM channels and then finish the channel setup. Then all you need to do is setup the second tuner and select the same channel lineup that you did the first time and all the channels should already be remapped, hit 'done' and have a beer!

Update: I did have an issue with "The Today Show" this morning, it was playing at double speed...hmmm...everything does seem to be tuning correctly though, so I think for the purposes of this thread, this solution worked for me.

[clmolnar]

Originally Posted by Yooper

I'm making a little progress.

O got some of the HDHR channels working using the 3 digit remap numbers. I remapped the channels that worked before using the channel editor numbers, but on 2 of the 4 channels actually work.

I haven't done any more work on the QAM channels on the 1600 card.

I had a similar problem. Only 2 of my 7 channels worked using the n-n-n remap. Switching to only the first number fixed my problem.

[mangriotis]

Originally Posted by Crashless

I was able to get my new HDHR running with clear QAM last night with relative ease on my Vista server.

Thanks Crashless... this worked perfectly, once I re-read that I was re-mapping the Sage channels rather than changing the .xml file. (I am using the 20070907beta1 program).

Now if I can fix this timeline stuff and the (maybe related) FF/REW skipping issues... we're golden.

[gplasky]

I also posted this over at SiliconDust and wonder if anyone else experiences this.

With the latest beta of Sage and HDHR I am getting the following results. I did the channel editor in HDHR and it did pull some station names. Going into Sage I can now remap to the n-n-n number and it works fine.

A side effect of the new update is Sage also discovers the stations on its own. It adds them to the channel guide in the form of:
80-1- -[2-80-1]
and enables it on its own. It doesn't see this channel as being
235 WMYD-DT [2-80-1]
from the dowloaded channel guide thru Sage.
Thus I end up with both channels being in the guide. Of course I went in and disabled the 80-1 channel for now so I only have one occurence of the channel.

Should this be working a little different than what I am seeing? My thoughts are it should work one way or the other but not both.

Gerry

Just curious if I'm the only one.

Gerry

[carlgar]

The above is what I always saw when I did a scan in Sage. Do you now have Silicondust*.frq files? If so I suspect that is why the n-n-n type values now work. If you want to eliminate the 80-1- -[2-80-1] channel just remap to their default logical channels.

[gplasky]

Got you. I did scan for the channels and let it create a frq file. That is when I first saw the channels. So I can just do a logical remap and be fine. I'll do that. It would be nice if it saw that on its own to elimate one more step.

Gerry

EDIT: So remapping those to their default logical channels caused it to NOT work with the n-n-n scheme. I had to go back to the single number for the enabled channels.

[Keenan]

IIRC that's what I saw in the Sage lineup as well when I loaded 20070830. I haven't updated beyond that yet.

[carlgar]

Originally Posted by gplasky

EDIT: So remapping those to their default logical channels caused it to NOT work with the n-n-n scheme. I had to go back to the single number for the enabled channels.

That is interesting. I don't recall what order I did things but remapping those back to their logical channels is usually one of the first thing I do.
I was really convinced that it was related to the *.frq files. Do your *.frq files still exists?

[gplasky]

Yes-frq file is still there. I thought I had deleted it earlier but before my previous post I checked and it was still there. Now before I changed the other ones to the default logical mapping I had just disbled them in the lineup and left them there. I then took one of the full mappings (235 WMYD-DT) and remapped it with the 2-80-1 and it worked. At least that is what I observed.


Gerry

[carlgar]

If you still have a *.frq for each of your Homerun tuner then you are probably correct. However, if you only have a *.frq for some of your tuners, then the n-n-n would only work on those tuners and not all of them. This could explain why some people see it only working on some stations.

[kevine]

I have different problem. Anyone ran into this?

I confirmed the channel changes work in the HDHR Manager and see Sage tuning the channel but Sage reports no signal after about 20 seconds. The signal meter on the other hand reports 90-100% each time.

I tried the mmc/dshow_cap change.
I tried the program_stream option.
I tried uninstalling and reinstalling
I tried backup of lineup.xml, delete original, rescan.

Using Beta3 drivers and SageTV RC3.

Thanks for your help.

XP Pro
InterVideo codec
HVR-1600 works fine

[gplasky]

How do you have your channels remapped in Sage? For me only the first number works, not the n-n-n number scheme.

Gerry

[kevine]

Originally Posted by gplasky

How do you have your channels remapped in Sage? For me only the first number works, not the n-n-n number scheme.

Gerry

Gerry, Thanks. I did read your post. I guess I should have mentioned that too. Yeah, I tried x-y-z, x, y-z. Nothing.

[Yooper]

I've installed the 6.2.8 SagetTv and the beta3 HDHR software.

I scanned the channels using the HDHR channel editor, identified and enabled the channels that I wanted. I then saved and exited.

I then went into SageTV and setup the HDHR. I let it scan for the channels and then I remapped the correct program to this channel. I did not do any physical remaps.

All of my HDHR channels now work - first time in at least 2 weeks.

[kevine]

That did not work for me. I chose an another provider that services my area (Digital Cable) so that I would not interfere with the mappings of the 1600. Scanned and found nothing.

[Yooper]

My HDHR is connected to my video server directly thru a dedicated network card. I wonder if that makes any difference.

Since the software is all new versions, there is probably a completely different set of parameters that influence success!

We begin anew for the search for these new parameters.