Hauppauge HVR1600

[zaphod7501]

I am, of course, attempting the impossible, but I'm beta testing a dual tuner card. SHS supplied a bda.ini and a direct.ini file that we hoped would work. The ATSC tuner does work and I can record with it. (using GB-PVR) The Cyberlink muxer (once I found out what it was and why I needed it) is OK for SD ATSC (480p) but does a terrible job on 720p and 1080i.

The card has a Conexant CX23418 so it is supposed to use hardware encoding for the analog tuner, unlike the HVR-950 and other hybrid cards. When I use the GB-PVR "Tuning Assistant" I can select the "Hauppauge HVR 1600 (analog)" and it will tune channels but Configuration does not detect the tuner and attempting manual selection and recording results in an error because GB-PVR could not find the crossbar filter. (but filtercheck does show it)

The native application works OK with the tuner (WinTV2000)

I've zipped the bda.ini, direct.ini, filtercheck.log, and GB....native.log from a failed the recording, and the inf for the card's installation.

Any help would be appreciated. I realize that this could be really hard and possibly fruitless.

[sub]

The ATSC tuner does work and I can record with it. (using GB-PVR) The Cyberlink muxer (once I found out what it was and why I needed it) is OK for SD ATSC (480p) but does a terrible job on 720p and 1080i.

Yes, this seems to be the general consensus from ATSC users. It works much better for DVB users. The Microsoft DVR-MS mux seems to do best job with ATSC.

[sub]

The card has a Conexant CX23418 so it is supposed to use hardware encoding for the analog tuner, unlike the HVR-950 and other hybrid cards. When I use the GB-PVR "Tuning Assistant" I can select the "Hauppauge HVR 1600 (analog)" and it will tune channels but Configuration does not detect the tuner and attempting manual selection and recording results in an error because GB-PVR could not find the crossbar filter. (but filtercheck does show it)

The native application works OK with the tuner (WinTV2000)

I've zipped the bda.ini, direct.ini, filtercheck.log, and GB....native.log from a failed the recording, and the inf for the card's installation.

Any help would be appreciated. I realize that this could be really hard and possibly fruitless.

I think you've just set the device number incorrectly.

Both your BDA capture source and Direct Recording source capture sources should be setup as device #1. You currently have the Direct Recording source capture source set as device #2, which is not being found in your machine.

[zaphod7501]

I also have a Hauppauge PVR250, which had been set to device #1. Should I change it to #2 or put them all at #1? I am brand new to GB-PVR, previously a WinTvCap user exclusively.

Edit: That has the HVR analog working. Am I going to have trouble with the PVR250 coexisting? As you might see from the log, I also have a MyHD MDP-130 and use an old Hollywood Plus card for DVDs. If I were to install the hacked directshow filters for the Hollywood Card (Sash's) would it be detected as an X-Card for setup?

Edit2: And thanks very much for your assistance.

[sub]

Edit: That has the HVR analog working.

Cool.

I also have a Hauppauge PVR250, which had been set to device #1. Should I change it to #2 or put them all at #1? I am brand new to GB-PVR, previously a WinTvCap user exclusively.

You only need to increase the device number if the devices use the same filter names. In these case, the HVR1600 and PVR250 use different names, so both are device #1.

and use an old Hollywood Plus card for DVDs. If I were to install the hacked directshow filters for the Hollywood Card (Sash's) would it be detected as an X-Card for setup?

To be honest I dont know. I dont even know if it works with the real X-Card any more. Its been at least a year since I had mine in my machine and tried it. Its effectively not supported anymore.

[zaphod7501]

Thanks again. I use the Hollywood for converting PAL to NTSC (and the reverse) and for real-time re-encoding using an S-Video loop back to the PVR250. That's why the 250 is still in the machine. The HVR1600 won't do PAL on the line inputs like all the previous Hauppauge cards (at least we haven't figured out how).

Anyone know the wiring diagram of the IR Blaster/Receiver? SHS and I got the cards but no IR cable. I'm an electronic tech so I can build one if I knew how they were wired but I don't have one to check out and I'm not very comfortable with messing with the card itself. (kind of limited availability)

Time to start reading all the old posts here. A lot of my initial questions were answered before I asked but I hadn't gotten to anything about how the device numbers and filters worked yet. I thought it was time to log in and I thought you might be interested to hear more about the new Hauppauge card.

I don't think I could get the DVR-MS mux to work on Windows 2000 sp4.

[sub]

I don't think I could get the DVR-MS mux to work on Windows 2000 sp4.

I seem to remember reading that it was possible, by copying a couple of DLLs of XP Pro, then registering them. I dont remember the details though. I seem to remember reading about this on the MyHTPC forums in relation to the GotTV app. GotTV later turned into GotAllMedia, so you might find some info at http://www.gallm.com

[zaphod7501]

WOW!
I installed the hotfix from MS (KB810243) (along with a copy of sbeio.dll) for DVR-MS files and set GB-PVR to use the DVR-MS mux. The hotfix dll's will register in Windows 2000. (and 2003 server if the various threads are correct).

CPU usage dropped to a maximum of 5% from as much as 70% with the Cyberlink mux and the files seem perfect. (1080i, 720p, or 480p) This means the card can perform background recording with almost no CPU load using GB-PVR.

I have also been able to record with both tuners simultaneously (actually three tuners; the two in the HVR1600 and my PVR250).

[sub]

Cool - glad you've got it working (though I've never heard of anyone get more than a few percent CPU with the Cyberlink mux)

[zaphod7501]

I noticed in the new release that you included the settings for the HVR1600 but they are the original ones that SHS had sent me. He corrected some errors later and the ones that were working were a little different.

The analog tuner in the direct.ini that SHS supplied was using "INIT_MODE=ECPPP" but in your new version it is "INIT_MODE=ECP" which matches most of the other analog Hauppauge cards. I have no idea which is correct on this.

The settings in bda.ini that would match filtercheck.exe should be
PIN_CAPTURE_IN=Mpeg2 Transport
PIN_CAPTURE_OUT=Mpeg2 Transport
Rather than Input0 and Output1. I don't know if either setting makes a difference in normal operation however.