[vdr] Hauppauge WinTV NOVA-T USB2 with vdr?!

[Laz]

Hi,

Has anyone managed to get vdr to work with a Hauppauge WinTV NOVA-T USB2? I'm 
trying to add one to an existing system with a PCI DVB-T card and it just 
keeps on restarting because it cannot get a signal from the USB device which 
hotplug sets to /dev/dvb/adaptor0. Hotplug loads the firmware and all looks 
good.

There are issues with the filter timeout on these devices (see 
http://www.linuxtv.org/pipermail/linux-dvb/2005-May/001738.html). If I use 
'scan' from dvb-apps, all I get is the initial transponder. If I add a '-5' 
option to extend the filter timeout, I get a full listing of all the 
available transponders.

If I use softdevice for output, I never actually see any video, just a series 
of 'reconfiguring layer' messages, which I think is a sign of no MPEG stream. 
If I run with just streamdev-server, I can switch channels with using SVDRP 
but it seems to switch between transponders just a little bit too quickly for 
my liking, i.e. as if it isn't actually switching it! In fact, if I try 'scan 
-c' to scan the currently tuned transponder, I get:

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
dumping lists (0 services)
Done.

Which looks like it isn't tuned to anything (doing the same for the PCI card 
gives an instant list of channels).

Has anyone sorted this one out? Is it a problem with filter timeout on tuning 
or something else? What's the easiest way of testing to see if it is actually 
streaming data (once tuned with tzap) to discount that option? I would 
usually use dvbstream but that fails for this device, I think because of the 
timeout problem again (saw references to this in the linux-dvb mailing list). 
Would changing PMT_SCAN_TIMEOUT in pat.c help me here?

For reference:
$ tzap "BBC ONE"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/laz/.tzap/channels.conf'
tuning to 722166670 Hz
video pid 0x0258, audio pid 0x0259
status 1f | signal 0700 | snr 0000 | ber 001fffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal ff3f | snr 0001 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0703 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK

Which carries on spewing out the last line for ever. 

I'm a tad worried about the signal 0000 bit! Maybe it is actually tuning but 
then not outputting a dvb stream. It's been a while since I've had to resort 
to dvb-apps because vdr has pretty much 'just worked' with my PCI cards!

This is with DVB drivers form a 2.6.12.5 kernel and vdr-1.3.36.

Cheers,

Laz