HVR-2250 & SageTV 7 clear QAM issue

[gcamp0730]

I am running Windows 7 64-bit and have an HVR-2250. I've tried both 27323 and 28162 drivers (running hwclear.exe each time). I've tried both Sage 7.0.11 and 7.0.12 and I have been unable to get Sage to properly detect my clear QAM channels. If I use the Hauppauge WinTV 7 and 28162 drivers I can see all the channels I should.

I always select the digital tuner, and then cable. I have tried selecting a provider for the EPG guide and sometimes not. I have performed both a Full Scan and an Update Scan. In all cases some channels are found, but they have strange call signs insted of ASCII text.

What is interesting is that if I watch several channels with WinTV 7 and then load Sage 7.0.12 and perform a channel scan it will find the proper channels and be able to tune them. However, after a reboot the channels will not appear.

This is a clean installation of the OS as well as Sage, etc.

Any suggestions on what I could try next?

[aflat]

I don't have this issue, but there is an update that talks about QAM and the beta, check the last post of this thread. No clue if it will help.

http://forums.sagetv.com/forums/showthread.php?t=49685

[gcamp0730]

Originally Posted by aflat

I don't have this issue, but there is an update that talks about QAM and the beta, check the last post of this thread. No clue if it will help.

http://forums.sagetv.com/forums/showthread.php?t=49685

Good point. I forgot to mention that when I was running 7.0.12 I was using the updated DShowCapture.dll from that post.

Also, UAC is set at default, but I have Sage installed under E:\SageTV so I don't believe that's an issue.

[gcamp0730]

I've just loaded Windows 7 x86 and I will try the same combinations as above to see if there is any difference. If not, I'll try trusty XP and see how that goes.....

[TwistedMelon]

There's also a thread about analog tuning on the HVR-2250.

Under Win7 x64 with a Sage 7.0.11 installation migrated from WinXP (no hardware changes), I get repeated errors on one of the tuners of one of the HVR-2250 boards in my system (there are 2 of them).

After doing some board swapping and rebooting, Sage is unable to tune any channels on either HVR-2250. One board is doing dual duty with QAM and analog and the other is set up for ATSC OTA.

I've also tried the new dll without help. There's definitely an issue with these boards and the latest betas and it doesn't seem specific to 7.0.12

I'm running the June 2010 Hauppauge drivers and haven't yet tried rolling those back. It might be a conflict with those, but I won't have the chance to do any further testing until the weekend.

[gcamp0730]

Originally Posted by gcamp0730

I've just loaded Windows 7 x86 and I will try the same combinations as above to see if there is any difference. If not, I'll try trusty XP and see how that goes.....

I did not see any difference with Windows 7 x86, but I did not try XP yet. I submitted a bug and have sent some detailed log files to the beta support team. I'll post here when I have some feedback.

[walts81]

I was running 7.0.10 on WHS using HVR-2250 with no issues. I've since nuked the OS and switched back to Win7 x86 and installed Sage 7.0.12 but now it can no longer detect any clear QAM channels. I've tried the updated dll but still no go.

- Josh

[gcamp0730]

Originally Posted by walts81

I was running 7.0.10 on WHS using HVR-2250 with no issues. I've since nuked the OS and switched back to Win7 x86 and installed Sage 7.0.12 but now it can no longer detect any clear QAM channels. I've tried the updated dll but still no go.

- Josh

Interesting. I tried going back to 7.0.11, but I didn't try 7.0.10. I'll give that a shot and see how that works with my setup.

[gcamp0730]

Originally Posted by gcamp0730

Interesting. I tried going back to 7.0.11, but I didn't try 7.0.10. I'll give that a shot and see how that works with my setup.

Well, with my setup anyway, rolling back to 7.0.10 didn't make any difference. But I'm on Win7 versus WHS, so that could have something to do with it as well.

[rrhorer]

Originally Posted by gcamp0730

Also, UAC is set at default, but I have Sage installed under E:\SageTV so I don't believe that's an issue.

When I first installed on new OS (Window 7 x32), I tried installing outside of the default Program Files location. Firewire would never work. I even turned UAC off; and it still would not work until I re-installed SageTV to the default location. If I were you, I would try: (1) turning UAC off - the virtual store is only one of the "security" measures that create grief on an HTPC setup and (2) re-install SageTV to its default location (uninstall first). And, you will still need the dll. Digital tuning on my HVR 2250 quit working until the dll was installed.

[gcamp0730]

Originally Posted by rrhorer

When I first installed on new OS (Window 7 x32), I tried installing outside of the default Program Files location. Firewire would never work. I even turned UAC off; and it still would not work until I re-installed SageTV to the default location. If I were you, I would try: (1) turning UAC off - the virtual store is only one of the "security" measures that create grief on an HTPC setup and (2) re-install SageTV to its default location (uninstall first). And, you will still need the dll. Digital tuning on my HVR 2250 quit working until the dll was installed.

I wish I could report that all is well. However, installing into the default location and turning off UAC had no better results.

[gcamp0730]

Turns out my cable company (Suddenlink) is broadcasting in a format that was confusing Sage. An updated TSSplitter.ax file fixed my problem.

Even though the url indicates the file is for v7.0.13, I used this on v7.0.12 with success. I have since upgraded to v7.0.13 and everything still works. Yeah!

[bnh]

i had issues with the 2250 as well, but thought i should report here that i appear to be good to go with both QAM and analog.

Driver: 7.6.27.27323, dated 11/19/2009
Windows 7 Home Premium (64-bit), 8 GB ram

One thing to note: While i was testing Sage7 in various configurations on the same server as Sage6, I did have issues when the *.ax file locations were not updated in the registry and continued to use sage6 filters (prolly my fault for not correctly backing out/reinstalling). I discovered this by dumping the locations of all the filters using a codec diagnostic tool and found stuff like this:

Description: SageTV MPEG Audio Decoder
File name: c:\sagetv7\common\legacy\stvmcdsmpeg.ax
CLSID: {ECB07A30-FF4E-441A-AF6A-D46A36A29F7E}
Merit: 00600000 = MERIT_NORMAL
Status: broken
Reason: File not found

I ended up manually fixing those and resolved all the tuning and playback issues that i encountered. Certainly wasn't a 2250 nor Sage problem, but hope this helps someone.

[TwistedMelon]

Can you guys that now have the HVR-2250 working properly update to the latest release drivers from June of this year? It would be great to have confirmation that these are also working.

I'm about to put my Win7 drive back into my system and start checking all this again myself.

Does anyone have a link for the November 2009 Hauppauge drivers?

[TwistedMelon]

After installing 7.0.12 and updating the dshowcapture and tssplitter files, I now seem to have QAM and Analog cabe working properly. But, as I had originally found, "tuner #3" which is on my second HVR-2250 fails to initialize most of the time.

The issue is always with this tuner number, even if I swap the cards around, meaning it's not specific to the card, but rather the enumerated tuner number depending on bus scan order. The issue only happens with Windows 7 and does not ever happen with my XP installation.

Going to update to 7.0.14 and if I can find the older Hauppauge drvers I'll give those a shot too.

[TwistedMelon]

I've updated to 7.0.14 and have also done a rescan of the channels on most of the tuners with good (expected) results. So far no more capture device failure messages and I can tune every channel I've tried from my lineup.

Currently in the process of rescanning QAM channels. I did notice the last time I did this with one of the v7 betas that scanning QAM takes a lot longer than I remember. It's over 10 seconds per channel right now. Is this what everyone else is seeing?

UPDATE: HVR-2250 ATSC tuners still fail repeatedly - took a couple of hours for the first failure to show up. The good news is that analog and QAM seem to work fine on the other tuner. For now it's back to WinXP though. I did get to test the two different driver releases with no difference noted between them as far as this issue goes, so I've submitted a bug report.

[gcamp0730]

Originally Posted by TwistedMelon

Currently in the process of rescanning QAM channels. I did notice the last time I did this with one of the v7 betas that scanning QAM takes a lot longer than I remember. It's over 10 seconds per channel right now. Is this what everyone else is seeing?

That's about what I see on my system. An interesting note - during initial setup it takes only a few seconds per channel but no QAM channels are found. After exiting Sage and restarting Sage (no reboot of the PC) the second attempt takes ~10s per channel and QAM channels are found.

Originally Posted by TwistedMelon

UPDATE: HVR-2250 ATSC tuners still fail repeatedly - took a couple of hours for the first failure to show up. The good news is that analog and QAM seem to work fine on the other tuner. For now it's back to WinXP though. I did get to test the two different driver releases with no difference noted between them as far as this issue goes, so I've submitted a bug report.

Does that mean that v7.0.14 works fine under XP?

I've only got one tuner in my box (HVR-2250), but as of late the channels in the middle (i.e. 2-20 work, 21-47 don't, 48-126 work) will not tune in any more. I've tried rescanning and the channels are found, but when I try to tune to them I get "No Signal". I'm going to submit another bug report.

[TwistedMelon]

7.0.14 seems to be working fine under WinXP for me, yes. Using the latest HVR drivers from this June. I've installed 7.0.14 to a new path and then copied the Wiz.bin and properties files from the older installation. I had to do a channel scan for every tuner for it to be able to tune into any QAM or ATSC channels. After those rescans everything seems solid.

Win7 x64 is still a NO-GO.

[gcamp0730]

I found a solution to my problem. Apparently when I performed channel scans on the tuners, each tuner came up with a different list of channels. Tuner 0 found the low and high channels, but nothing in the middle. Tuner 1 found everything except for one.

So I copied the file "Hauppauge WinTV-7164 Analog Capture-1-QAM.frq" to "Hauppauge WinTV-7164 Analog Capture-0-QAM.frq" (copied 1 to 0) and now I can tune in to the channels that were previously listed as "No Signal".

Still don't understand how two tuners on the same cable would find different channels.

In any case, sounds like your problem with tuner #3 on the second HVR-2250 is different from the problem I had.

[tmar89]

I am using the 7.0.15 and did a clean install under Windows 7 32bit and when I choose one of my 2250 QAM tuners, I get an error in Sage but then I am able to continue and scan, but find no channels. Works fine in WinTV and BTV.