Hauppauge WinTV CI Module support?

[dman_lfc]

Error log:

2008-09-28 22:46:00.781250 [10]: dvb: Failed to add bda receiver: Hauppauge Nova USB2 DVB-T TV Receiver. Is it in use?

Some other prgram is using your DVB-T BDA device & not releasing it.

DMAN

[jigsjdg]

DMAN,
Saw that too, but there isn't any other application running that could be using the BDA device other than TVServer.
If I swap the T-USB2 for my T-Stick and restart the TVServer service, there's no error and I can watch all channels fine (incl. scrambled ones).
The error comes back when I then swap the T-STick for the T-USB2 back again and restart the TVserver.

One would expect the T-Stick to be blocked as well if another app is using the BDA devices, no?
It appears as if the TVServer thinks it's blocked, while it isn't... Hence the post

Regards,
-Jigs

[dman_lfc]

TVServer only thinks it's blocked becuase it cannot add the device's filter to the graph - which is quite reasonable.
If your OS/drivers etc report such, there is not much we can do. You have to fix that issue, it's not a TVServer bug.

DMAN

[jigsjdg]

Tested it on a new machine; only the OS (Win XP, SP3) installed on it (no anti virus, firewall yet).
Used he Nova-T-USB2 Hauppauge's driver, no WinTV CI module or drivers, installed RC2, then SVN#20339 (regular procedure) and I get the same error.
Then tried it with the T-Stick: no error; everything worked fine. I then tried the T-USB2 again and the problem reoccured.

I always stopped/started the TVServer service when switching tuners (which oddly enough can't be stopped the normal way either when the T-USB2 is attached; only by killing the process tree from the Task Manager. Stopping/starting it was no problem when the T-Stick was hooked up)

I then installed the WinTV 6 application and that could use either tuner without problems.

Now I'm quite sure there is no application claiming the BDA Device but the TVServer.

This would lead to think the problem is located in the TVserver code and related to the Nova T-USB2...
Could be simple though, maybe an accidentally mixed up set or missing params when checking the availability? Alledgedly the T-USB2 had a different chipset than the T-Stick, so the driver could behave differently than expected...

[dman_lfc]

I see your problem the Hauppauge Nova USB2 DVB-T TV Receiver filter is called twice hence the lock.
The driver is reporting that it's a BDA Source & Receiver filter.
Also that BDA Source filter doesn't output the required pin Major & SubTypes.
This could also be why your device is unsupported by Hauppauge with the WinTV-CI
Tsk Tsk, bad Hauppauge...

We maybe able to work around this.
PM me your email address and I'll send you a patched DLL to try.

DMAN

[jigsjdg]

Tested the patched DLL and this is what I found:

Setup 1
1x T-USB2
1x CI Module

FTA works now, but the CI module isn't added to the graph correctly. It is discovered and inited, but scrambled channels remain what they are: scrambled
See: setup1log.zip

Tried removing the T-Stick card from the TVServer Config screen and restarted the TVService. Now it's not able to start timeshifting at all. Error.log shows it's not able to create graph.
See: setup1-2ndlog.zip

Then unplugged the CI Module. Unmapped the CI-Module from the T-USB2 and restarted the service. Now FTA channels are shown correctly again.

Fiddling with some checkboxes and restarting the service, it seems that whenever the CI-Module is mapped to the T-USB2 in the WinTV CI tab, the T-USB2 fails to produce a graph...


Setup 2
1x T-USB2, explicitly not paired to the Ci Module
1x T-Stick
1x CI Module, paired to the T-Stick (in both the cards->edit window and WinTV-CI tab)

Mapped the T-USB2 to only FTA channels and the T-Sticks for all channels (FTA+Scrambled).
It was not possible to make combinations for similar channels on both tuners, so all channels (incl. FTA) were shown by the T-Stick only (higher priority, unable to change the priority of the T-USB2).

Then mapped the T-Stick to only scrambled channels and the T-USB2 to only the FTA channels. Scrambled channels worked fine through the T-Stick but tuning to the FTA channels (and thus the T-USB2) gave the same error as before: BDA device in use...

See: setup2log.zip

Tried this twice, exact same outcome each time. In this setup it's actually only posisble to use the T-USB2 as a remote receiver (as that's working better on the T-USB2 than the T-Stick...)

[dman_lfc]

Emailed you a new patch - should work now

DMAN

[jigsjdg]

Originally Posted by dman_lfc

Emailed you a new patch - should work now
DMAN

It did.... eventually... and only for a little while...

Tried these scenarios:

Setup 1
1x T-USB2
1x CI Module

The CI Module is configured to service the T-USB2 device in both the card properties and the WinTV CI tab.
Starting the TVService in this scenario gave an error.log straight away - 'Unable to start graph'. Changing channels to first a scrambled one and then to a FTA channel (called 'Nederland 1'), both resulted in the same error.

See: Setup1.log.zip

Setup 2
1x T-USB2
1x CI Module

The CI Module is set in the WinTV CI tab to service another device than the hooked-up T-USB2. In the card properties window, it still is checked it has a CAM available.
Restarted the TVService and tuned into a scrambled channel. For obvious reasons this didn't work and a clear error message was displayed (Channel is scrambled). FTA tuning was no problem

See: setup2.log.zip

But....
Playing with the settings and fiddling around a bit with checkboxes and restarting the TVService every now and then, it suddenly started working!?!?!?!?! I could now watch scrambled channels with the T-USB2 + CI Module

The odd thing is: it's not reproduceable. Continuing to fiddle with the settings didn't breakup the ability to use the CI module with the T-USB2. Unless the code in the patched library is self-learning and recoding itself on the fly, I got no explanation.

However, I then stopped the TVService, disconnected the T-USB2, hooked up the T-Stick and restarted the TVService and all hell broke loose on the error.log file. It quickly grew to > 4MB.
And in no way it was possible to make the thing work again (while it did before) and changing prefs and props in the TVServer Configuration didn't help a bit; error.log kept growing rapidly and it wouldn't ever work

See: setup3.log.zip

Then I hooked up the T-USB2 again, paired it back to the CI Module: same result as Setup 1... unable to start graph for scrambled and FTA channels.

Tried the settings from Setup 2 again: FTA channels are received okay, scrambled channels produce a neat 'Unable to tune - Channel is scrambled'

Trying to fiddle again with the settings, but the CI support for the T-USB2 never came back (log files identical to the ones for Setup 1)
Continue to fiddle with settings for the T-Stick also never gave back the CI support for it..
See: Setup4.log.zip

And the strangest thing is that even with the original DLL, it is not possible anymore to get the T-Stick to function properly with the CI module anymore either...
See: Setup5.log.zip