Hauppauge 2250 Opinions wanted

[donschjr]

At least I'm getting somewhere but what I don't understand is why if the older drivers work, won't the more recent ones. Why put out drivers that go backwards for so many?

I have to use the older drivers with my 1600's or qam doesn't work with comcast cable. I thought it was because of a bad update but I recently swapped motherboards so I did a reformat and the newer drivers still wouldn't work. I had to do a hwclear and install the older drivers I have on a backup disk they are 3.4d1. Hard to understand but that's the only way they will work.

[mian]

Ordered from newegg. I imagine it will come Tuesday or Wednesday. Thanks for all the input guys.

[sub]

An updated set of HVR-22xx pre-release drivers can be found here: http://www.gbpvr.com/090107_22xx_7.5.25....elease.zip

Release notes:

This driver contains general ATSC and QAM improvements. Please remember that this is a PRE-RELEASE driver and has not been fully qualified.


Driver Release 7.5.25.27007.PreRelease (1/7/09)
* Fix bug which caused major problems for QAM (and ATSC to a lesser extent) if the other tuner was tuning/running Analog.
* INF Cleanup.

Driver Release 7.5.12.26364.PreRelease (12/29/08)
* Fix QAM demodulation which was accidentally broken in 7.5.6.26354.PreRelease. That's why we call them PreReleases.

Driver Release 7.5.12.26359.PreRelease (12/24/08)
* Appropriate CIRCoInstaller Support in INF for Vista and later

Driver Release 7.5.12.26354.PreRelease (12/19/08)
* ATSC/QAM tuner sensitivity improvements.

Driver Release 7.5.12.26353.PreRelease (12/18/08)
* Initial ATSC tuner sensitivity improvements. Will likely need more work.

Driver Release 7.5.12.26345.PreRelease (12/10/08)
* Firmware and driver updates improve IR reliablilty.

Driver Release 7.5.6.26322.PreRelease (11/17/08)
* 64Bit OS "greater than 4G" memory issues resolved (black/green screen issues).
* Support for "EnableAutoOffset" reg patch.
This improves situation for Australian users whose signals are re-broadcast on non-centered frequencies
but whose streams report the original (way off) frequency.
* Failure on "First Tune" resolved.
* Support for the hcwWilt_RegisterAdapterObject_ registry patches.
The "Std" version fixes a Microsoft Bluescreen on some 64Bit [Dell and potentially other] machines which bluescreen under some circumstances.
This is NOT a Hauppauge bug and unfortunately we are presently powerless to detect this situation dynamically.
But this registry patch will resolve the issue.
* Thanks to so many for patient endurance in waiting for the resolution of these issues.

Driver Release 7.3.28.26288.PreRelease (10/14/08)
* TDA10048 SNR fixes and efficiency improvements.
* Fiji and Win7 default to AllowQAM_Powertoy key ON.
* Undo experimental fix for 'greater than 4G' memory issue (which was not effective). Will re-visit this shortly.

..snip...

[whurlston]

Driver Release 7.5.12.26364.PreRelease (12/29/08)
* Fix QAM demodulation which was accidentally broken in 7.5.6.26354.PreRelease. That's why we call them PreReleases.

I'll have to double check the version I tried. I thought this was the version I tried that wouldn't tune any QAM but I could be wrong.

[whurlston]

Yup, QAM is tunable again with these latest prerelease drivers. Thanks sub.

[whurlston]

Finally, when you have time, try back to back and dual recordings with the analog side of the 2250 and see if you have any problems. With older drivers I get blue screens (not BSD's) of short files and also see blue screens when switching channels.

I figured out this problem. It seems that The Hauppauge analog tv tuner driver is not interpreting channel frequencies properly (cable channel 4 for the US is one of the problem channels). It can be fixed by modifying the tuning spaces in your registry. I would only do this if the 2250 is the only tuner you have in your machine (or possibly other Hauppauge devices as well). I can't do the registry mod because if I do, my VistaView tuner will not tune properly.

sub, do you think you would be able to ping your Hauppauge contacts on this issue?

Channels 2, 3, 5 and 6 tune to the correct frequencies but as you can see from the attached pic, channel 4 has a 1.75Mhz offset applied to it so it tunes the wrong frequency (The ViXS is tuned to the correct frequency). I haven't looked at all the channels to see which ones have the problem, but I can if they need me to do so.

[sub]

Ok, but I'll email them.

[whurlston]

Ok, but I'll email them.

Thanks. I did actually mean "ping" as let them know somehow. It wasn't a typo for "ring".

[pcostanza]

Stupid question Will, how do you get to the tuner properties screen? I'm not at a computer now to test this out but am curious and will try later tonite.
Thanks for the info.

[whurlston]

I used Monograms GraphStudio (GraphEdit will work as well). Just select "Graph"->"Insert Filter", select "WDM Streaming TV Tuners", then choose the analog tuner you want. Right click the filter to get the properties. You don't need to build a complete graph to just check the frequencies that it's using.

The video frequency should match the frequencies produced by the center channel setting of the qam.ini manager.