HVR-1600 install kills PVR-500 content?

[anotherjack]

Having just rebuilt my PVR system from a motherboard crash, I decided to go ahead and just install v1.08 and reconfigure. I now face a couple of problems that have me seriously perplexed.

First, after installing and configuring my PVR-500 card, I tested it and everything was OK. Once I onstalled my HVR-1600 and configured [i]just the analog side[/u], all of my channels come up as nothing but static. the EPG updates properly and all shows up corrctly in the EPG, but when trying to go to live tv, nothin'. Removing the card and capture source restores the channels.

Next, I decided to go ahead and try to configure the QAM side of the 1600, but found that when I went to the BDA configuration for that tuner, even though I selected the QAM option in the dropdown, the "Type" box on the BDA config screen stays stubbornly at "ATSC". I've verified that the proper drivers are installed and that my card is of the proper model to support QAM, but cannot figure out why the BDA config doesn't agree.

As an aside, both cards were working under 99.12, including both the ATSC and analog sides of the 1600.

Hauppauge beta drivers ver. 1.62.25129.0
PVR-500MCE / HVR-1600
GBPVR 1.08
Athlon 64 3000+
ATI 9800 Pro AGP
VIA 8T800 Pro chipset with latest 4-in-1 drivers
WinXP SP2
Installed patched NativeUtils.dll and QAM.ini

Any help would be appreciated. Log files attached.

[sub]

Next, I decided to go ahead and try to configure the QAM side of the 1600, but found that when I went to the BDA configuration for that tuner, even though I selected the QAM option in the dropdown, the "Type" box on the BDA config screen stays stubbornly at "ATSC". I've verified that the proper drivers are installed and that my card is of the proper model to support QAM, but cannot figure out why the BDA config doesn't agree.

Actual, this is normal. Ignoring Dishnetwork and couple IPTV companies, all digital TV in the US is ATSC. The ATSC signals are modulated either using 8-VSB for terrestrial reception via antenna, or QAM for reception via digital cable.

[anotherjack]

Actual, this is normal. Ignoring Dishnetwork and couple IPTV companies, all digital TV in the US is ATSC. The ATSC signals are modulated either using 8-VSB for terrestrial reception via antenna, or QAM for reception via digital cable.

Thanks for the quick reply, Sub. I'm on Cox cable and I know (based on reports from friends) that they have unencrypted QAM feeds. That's what I'm trying to get, since I'm kinda "fringe-y" for antenna where I live. I figured it would at least TRY to go to QAM during the config when I picked HVR-1600 (QAM) from the dropdown. Any ideas on the "everything's static" issue when the 1600 is installed?

Jack

[sub]

Does the Hauppauge WinTV app find your QAM channels?

Any ideas on the "everything's static" issue when the 1600 is installed?

Actually, it'd probably be worth checking the analog side of the 1600 while you're in WinTV. If it works there, then we should definitely be able to get it work 'static-less' in GB-PVR.

[anotherjack]

Does the Hauppauge WinTV app find your QAM channels?

Actually, it'd probably be worth checking the analog side of the 1600 while you're in WinTV. If it works there, then we should definitely be able to get it work 'static-less' in GB-PVR.

OK, we need a laphead: emoticon here. Figured out the "static" issue. When I had the old motherboard, I had a splitter to feed the PVR-500 card and the analog side of the HVR-1600, with a cheap dipole feeding the ATSC side of the 1600. When I decided to try out the QAM (still not working - more on that in a bit) aspect, I simply moved the coax from the analog side of the 1600 to the ATSC connector - not connecting anything to the analog, since I had never used the analog side except for initial testing. The PVR-500 had two tuners, and that was all I ever used. However, when I moved the cards to the new motherboard, I had to swap their PCI positions due to onboard connector issues. This put the 1600 closer to the AGP slot than the 500, and lower in the PCI INT# range of the motherboard than the 500. I can only assume that this makes GBPVR look at the the 1600 as the "lower numbered card #1" in when looking for a tuner to use. No antenna on the "first analog tuner" means static when attempting to watch live TV in analog mode. Q.E.D. Duh. Insert laphead: here.

On to the QAM problem. Even though it insists on thinking the QAM side of the 1600 is ATSC, I still show multiple channels showing up when I click the "map to channels" button. I can't actually look at them, but they show up in that module. All listed as "595245.11 Unknown (000(AC3))" or some variant with the numeric prefix changing and/or the "(AC3)" being present as the only differences.

My best guess is that I'm a moron, but would love to be proved wrong.. ;-)

jack

[sub]

OK, we need a laphead: emoticon here. Figured out the "static" issue. When I had the old motherboard, I had a splitter to feed the PVR-500 card and the analog side of the HVR-1600, with a cheap dipole feeding the ATSC side of the 1600. When I decided to try out the QAM (still not working - more on that in a bit) aspect, I simply moved the coax from the analog side of the 1600 to the ATSC connector - not connecting anything to the analog, since I had never used the analog side except for initial testing. The PVR-500 had two tuners, and that was all I ever used. However, when I moved the cards to the new motherboard, I had to swap their PCI positions due to onboard connector issues. This put the 1600 closer to the AGP slot than the 500, and lower in the PCI INT# range of the motherboard than the 500. I can only assume that this makes GBPVR look at the the 1600 as the "lower numbered card #1" in when looking for a tuner to use. No antenna on the "first analog tuner" means static when attempting to watch live TV in analog mode. Q.E.D. Duh. Insert laphead: here.

No worries, I suspected this was something dumb

On to the QAM problem. Even though it insists on thinking the QAM side of the 1600 is ATSC

as I said above, it is ATSC, which can be modulated using 8-VSB or or QAM.

I still show multiple channels showing up when I click the "map to channels" button. I can't actually look at them, but they show up in that module. All listed as "595245.11 Unknown (000(AC3))" or some variant with the numeric prefix changing and/or the "(AC3)" being present as the only differences.

Can you watch these channels with the Hauppauge WinTV software

[anotherjack]

No worries, I suspected this was something dumb

as I said above, it is ATSC, which can be modulated using 8-VSB or or QAM.

Can you watch these channels with the Hauppauge WinTV software

OK, for some reason, I thought that there was a fundamental difference between ATSC and QAM, hence the need for including support for it and the new dropdown selection...? Not trying to belabor the point, just trying to understand. I rescanned the DT channels and was eventually able to get the preview to work, so the second point appears to be moot now.

Thanks for the help, Sub.

[sub]

OK, for some reason, I thought that there was a fundamental difference between ATSC and QAM, hence the need for including support for it and the new dropdown selection...? Not trying to belabor the point, just trying to understand.

No worries the terminology surrounding this is usually misused. I do it myself in places, just because I know people are looking for "QAM" when they thinking about digital cable.

ATSC is the digital TV standard. QAM is just a modulation technique for carrying the signal on the wire, which BTW is also used DVB-C/T etc.

I rescanned the DT channels and was eventually able to get the preview to work, so the second point appears to be moot now.

Great.