Skip to contentSkip to conversation

HVR 4000 and DVB-API

DISCUSSION Dominique Michel 2 participants 4 messages Sep 24, 2012 – Sep 26, 2012 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

The WinTV HVR-4000-HD is a multi-tuners TV card with 2 dvb tuners. It look like its driver doesn't have been updated to the new DVB-API.

The problem I get with dvr is than vdr only seam to recognize and use the first tuner of my Hauppauge WinTV HVR-4000-HD. The devices are in /dev/dvb/adapter0:

# ls /dev/dvb/adapter0
demux0  demux1  dvr0  dvr1  frontend0  frontend1  net0  net1

frontend0 is the dvb-s tuner and frontedn1 is the dvb-t/c tuner, and I want to be able to use both of them. It is a hardware limitation in that card (among other) that make not possible to use those 2 tuners at the same time.

When starting vdr, the only error message I get at the console is, when I make udev to create symlinks like /dev/dvb/adapter1/*0
to /dev/dvb/adapter0/*1:

* VDR errors from /var/log/messages:
* ERROR: /dev/dvb/adapter1/frontend0: Device or resource busy

I can use mplayer instead of vdr. It work with the symiliks with "mplayer dvb://2@", and without the symlinks by acceding directly the adapter0/drv1 device after tuning with tzap. When trying to access one of the dvb-t channels from shmclient, it tell me "Channel not available".

vdr holds an opened handle on the frontend during its running time. Since the DVB-S frontend is the first one, DVB-T does not work. Some months ago the linux-media DVB-API was extended so multiple delivery systems can be accessed through one frontend, if they are mutually exclusive. Sadly the driver for the HVR 4000 was forgotten.

I don't want to buy another TV card or a TV set. So, can I hope than, in the reasonably near future, someone on this list will get some time to fix and update the HVR 4000 driver?

Dominique

Signature · 1 line
"We have the heroes we deserve."
#1 lore raw
Quoted 2 lines · Dominique Michel

The WinTV HVR-4000-HD is a multi-tuners TV card with 2 dvb tuners. It look like its driver doesn't have been updated to the new DVB-API.

Multi-standard frontends required DVB API version 5.5. That is found in kernel versions 3.2 and later. So you might need to update the kernel. If you already have, then well, you need to get someone to update the driver.

Also the application needs to be updated to support DVBv5.5 too. I don't know which versions of VDR support multi-standard frontends, if any as yet.

Signature · 2 lines
Rémi Denis-Courmont
http://www.remlab.net/
#2 lore raw

Le Tue, 25 Sep 2012 22:27:55 +0300,
"Rémi Denis-Courmont" <[email protected]> a écrit :

Thanks for the answer.

Quoted 9 lines · Dominique Michel
Quoted 3 lines

The WinTV HVR-4000-HD is a multi-tuners TV card with 2 dvb tuners. It look like its driver doesn't have been updated to the new DVB-API.

Multi-standard frontends required DVB API version 5.5. That is found in kernel versions 3.2 and later. So you might need to update the kernel. If you already have, then well, you need to get someone to update the driver.

I have kernel 3.4.5 with the in-kernel dvb driver, so it must be OK. I just checked the kernel config, and it seam OK too. But just to be sure, do you know if it is some specific kernel option that need to be enabled in order to get the DVB API version 5.5, or is it the only one that is in the kernel?

Quoted 5 lines

Also the application needs to be updated to support DVBv5.5 too. I don't know which versions of VDR support multi-standard frontends, if any as yet.

In the main time, I will ask on the vdr forum. vdr-1.6.0 here, the last stable version.

Signature · 1 line
"We have the heroes we deserve."
#3 lore raw
Quoted 11 lines · Dominique Michel

Le Tue, 25 Sep 2012 22:27:55 +0300,
"Rémi Denis-Courmont" <[email protected]> a écrit :

Thanks for the answer.

Quoted 5 lines · Dominique Michel
Quoted 3 lines

The WinTV HVR-4000-HD is a multi-tuners TV card with 2 dvb tuners. It look like its driver doesn't have been updated to the new DVB-API.

Quoted 6 lines
Quoted 4 lines

Multi-standard frontends required DVB API version 5.5. That is found in kernel versions 3.2 and later. So you might need to update the kernel. If you already have, then well, you need to get someone to update the driver.

I have kernel 3.4.5 with the in-kernel dvb driver, so it must be OK.

I get 2 frontends, so the driver was not updated in order to use only 1 frontend and calls like DTV_ENUM_DELSYS and FE_SET_PROPERTY / DTV_DELIVERY_SYSTEM.

The driver is cx88_dvb from Chris Pascoe and Gerd Knorr.

Quoted 6 lines
Quoted 4 lines

Also the application needs to be updated to support DVBv5.5 too. I don't know which versions of VDR support multi-standard frontends, if any as yet.

In the main time, I will ask on the vdr forum. vdr-1.6.0 here, the last stable version.

vdr >= 1.7.23 is needed too.

Signature · 1 line
"We have the heroes we deserve."