Latest downloads from Intel in Sound Card. Sort by: last update. Wistron Intel SST OED Audio Driver 10.29.0.4548 for Windows 10 Vibranium Update 64-bit 318 downloads. Sound Card Intel. Windows 10 64 bit. Jan 8th 2021, 02:42 GMT. Wistron Intel SST. You generally want a sound card with signal-to-noise ratio over 100dB, but the best sound cards are in the 124dB range, which is a significant improvement. Channels - A lot of decent, budget-friendly sound cards typically support 5.1 channel audio, but you can spend a little more to get one that can handle 7.1 surround sound.

Warning: This page has been locked and archived on September 27, 2010. The official documentation for this card can be found at WinTV-PVR-500. This page remains as there is significant information herein not included in the official documentation. Please migrate any such information to the proper location.

• 3Troubleshoot Tips
• 4Common problems and solutions

The Hauppauge PVR-500 is PCI-based video tuner card which features hardware-accellerated video and audio compression. Technically the card is functionally identical to two PVR-150 cards on their own PCI bridge in one socket, and requiring only one coaxial connection for both tuners due to an internal signal splitter.

The card was marketed almost exclusively at OEMs and system builders and may or may not feature an 'MCE' designation in it's packaging. While there remains only one catalog number for the NTSC version of this card, Hauppauge did make several slightly different revisions of both NTSC and PAL/SECAM models of the PVR-500.

There were at least 3 different tuners used in the various revisions of the PVR-500. Some say that Philips tuner inside the older models has a better quality.

• Hauppauge WinTV-PVR 500 type A - Philips FQ1216AME MK4 TV tuner
• Hauppauge WinTV-PVR 500 type B - Philips FQ1236A MK4 TV tuner
• Hauppauge WinTV-PVR 500 type C - Samsung TCPG 6121P30A TV tuner

One notable exception to the apparent 'two of everything' behind this card, only the first tuner's FM tuner is usable for recieving terrestrial FM broadcast radio. For obvious reasons if your revision of the card supports an IR reciever or transmitter, there will only be one of each. Additionally, the US version of the card has a dbx-TV stereo audio decoder, while the European version of the card has a Nicam stereo audio decoder. As this card records OTA (over-the-air) analog video it is technically obsolete in the United States, however there exist separate PAL and NTSC versions of this card. Be sure the one you obtain is the correct one for your region.

All known versions of the PVR-150 are handled by the same version of the IVTV driver, now a part of the Video4Linux subsystem found in the 2.6.x Linux kernels.

Note: Hauppauge no longer ships any of the analog only (PVR) cards due to pressure from FCC.

The IVTV project developed a driver for this and the other Hauppauge PVR-xx0 cards which has become a part of the Video4Linux project and is now incorporated into the normal Linux kernel.

You will need a 2.6.x kernel (2.6.22 or newer recommended) to make this card work properly.

Installation guides for IVTV

-Generic Howto on ivtvdriver.org (don't forget the ivtv firmware)

Distribution specific guides

-openSUSE 10.2 mythTV wiki page

Check the IVTV console output with dmesg

The output of the `dmesg` command should look like the following (used `egrep` to filter IVTV messages only)

Check your IVTV version

To check what version is installed, issue the command:

Your output should look something like:

Check on http://ivtvdriver.org if you have the correct version for your kernel/hardware.

Check video devices

8.) Check if the video devices are available to the system:

Your output should look something like this example:

Here is what each device corresponds to in this case:

Tuner unit #1: - For your info

Tuner unit #2: - For your info

mythtv-setup, define 2 x PVR150

Select new Capture Card and configure the first card as a hardware MPEG-2 device like the PVR150 (Remember the PVR-500 is dual PVR-150's so you will need to configure two capture cards. The two cards will have the same tuner (which may be called tuner0 or tuner1, depending on your version of mythtv), but different devices (e.g. /dev/video0 and /dev/video1).

If you are lost; here are some screenshots of mythtv-setup for a PVR-500 in the Netherlands.

Driver refuses to load for mysterious reasons

Under certain memory configurations on 32-bit platforms, using this card's driver and some other drivers (usually but not exclusively nVidia's proprietary driver) at the same time requires more of a particular type of address space allocated than the kernel will allocate by default. If you experience the driver refusing to load for no obvious reason, check the output of `dmesg`. If you see either of the two following messages appear, you will need to go to Common Problem: vmalloc too small to learn how to apply a very small kernel configuration change which requires one reboot.

The messages to look for:

Kernel Recommendations

You need a 2.6.x kernel to make this card work properly. The drivers which work with the 2.4 kernel, even patched, are old and can no longer be expected to work reliably with MythTV 0.22 or newer. Using a kernel 2.6.29 or newer is highly recommended as this brings the kernel driver up to speed with the last release of the userspace tools (ivtv 0.4.0). Reports that you need to compile ivtv yourself outside the kernel tree can be considered old/obsolete information, as the ivtv driver itself completed the move into the kernel around version 2.6.26.

Spontaneous Reboots

Do not attempt to enable pre-emptive kernel locks in your kernel configuration--the ivtv modules do not get along with them and will cause spontaneous reboots.

Signal Strength Warning

Your cable feed usually only has enough drive power for 2 or 3 TV sets. If you're driving a large number of devices, you may need an RF Amplifier to boost signal strength. Conversely, your house cable may be supplying too much power to the PVR 500. Ivtv developers have noted that the Samsung tuners used in later PVR 500s are rather sensitive and will show a grainy picture if supplied with too high a signal level. In this case you must reduce signal strength by either inserting a 'pad' (a resistor) between the PVR and the cable, or if your house has a cable amplifier, by reducing the gain on the amplifier.

Outdated Repository

Additionally, installing current firmware and PVR150/500 specific audio firmware from the ATrpms repo using Jarod's:

does not provide you with the latest and greatest recommended firmware as the folks at ivtvdriver.org suggest.

While most of the people will ignore the ivtv warnings displayed by using:

related to buggy firmware... it becomes a big problem when you use the PVR500 in conjunction with the PVR350. (Presumably this happens with the use of PVR150 and PVR250s too, but I can't confirm that.)

Symptons include loss of audio on both the PVR500 tuners and inability to change channels. The PVR350(s) will work fine though. Follow the ivtvdriver.org people's advice and download, extract, and install the recommended firmware.

Motherboard Incompatibility

Those of you with the ASUS A8V board will be disappointed to know that there appears to be no way to get this board to work with a PVR-500 if you are using the AGP port. The PVR-500 has its own PCI bridge and the AGP port on the motherboard is also on a PCI bridge, and the second PCI bridge fatally confuses the BIOS when it goes to initialize the hardware for booting after the system inventory screen. The recommended (and only known) workaround is simply to replace your AGP video card with a PCI video card. One might also trade in the PVR-500 for a pair of PVR-150's, but since the PVR-500 costs more than a new motherboard that doesn't make much financial sense (cheaper to buy a different mainboard). Some other ASUS A8V-xx models are also affected by this bug, but can be made to work with a BIOS update. For other uses the ASUS A8V is a fairly nice board, and the PVR-500 is a fairly nice card, the board is just flawed in a way that makes it impossible to use anything with its own PCI bridge.

Audio Instability

There appear to be well-known and repeatable audio quality problems (everywhere you google) about Hauppauge PVR-xxx cards and MythTv. From weeks of Googling for help and testing combinations of IVTV drivers, Myth versions, kernel versions, hardware settings etc., I've come to the conclusion that Myth does not cleanly set (and reset) the audio channel on channel change, or system startup. ivtvctrl -q0 -d0, ivtvctrl -q0 -d1 repeated a couple of times temporarily corrects the audio problems (until next channel change). The problems may be timing-related in the API between MythTv and IVTV. I will be looking into the source to investigate the API issues between IVTV and MythTv. I'll post results. Currently running MythTV 0.20, ivtv 0.4.7, kernel (Ubuntu Dapper) 2.6.15-27-amd64-generic, PVR-500, Nvidia GeForce etc. No dmesg problems reported, no logged mythtv problems, no logged ivtv problems (ivtvctrl -D 99). To the software things look okay - to the listener, audio is clobbered.

More recent versions of ivtvctrl do not provide for the '-q X' option, and running the above commands will therefore return the usage screen and do nothing. The functionality has been moved to the v4l2-ctl program. A workaround that has been successful in some cases is to set the audio source to one where there is no audio, and then set it back to the source where the audio actually is. Assuming that the video capture device is /dev/video2 the following code would set the audio source to 0 and then back to 1:

As of ivtv-utils 1.2.0, the command is now --set-audio-input=0

As of this writing, the latest iteration of my channel changer is to change the channel on the STB and immediately change the audio input to one where there is no sound, and a few seconds later come along and change the audio input back to one where there the sound exists. Here is a sample perl script that does this with the directv.pl script. Of course adding logging, debugging, and error checking is a good idea. (The reason for the 'fork' is to let MythTV believe the channel is tuned, and then 'turn on' the sound once MythTV is capturing the feed and the set top box has actually tuned the channel.)

Unreasonably low latency

The following files in /var/log may contain a message 'Unreasonably low latency' from ivtv:

If you find such messages you should probably read the page on PCI Latency

Hauppauge Driver Download

No sound on first recording

Hauppauge Sound Cards & Media Devices Driver Download Windows 7

I had the problem that the first time mythtv tunes to a channel (live-tv and recording) sound is not working. Changing channels fixed the sound. I had this problem with ivtv 0.4.1 and 0.4.2. After some help from the mailing list, I found out that executing

fixes the sound. I don't know what this command does. However, I had to manually issue this each time I tuned the first time with a tuner. If I execute ivtvctl a second time, I get a sound hickup. So only execute this command once if a tuner is recording. To ease my life, I created this script:

Hauppauge Sound Cards & Media Devices Driver Download Windows 10

Only one coax input

Despite having two TV tuners, the PVR-500 has only one coax TV input. The card has two coax connectors, but only one feeds both TV tuners, using an internal splitter; the other allows connection of an FM radio antenna. Thus, the PVR-500 will allow recording two programs via coax from the same underlying source, but will not support two independent coax video sources. For instance, you cannot attach two cable boxes via coax and record independent programs; you must connect at least one cable box via RCA cables.

Hauppauge Video Capture Device