1.36 Hauppauge WinTV-NOVA-S2 DiSEqC (1 Viewer)

[AberDino]

Sorry my bad, please try again.

The DLL seems to have disappeared from your original post?

 

[Pablik]

The DLL seems to have disappeared from your original post?

Oh, geez... The file is back now.

 

[AberDino]

OK, so I now see a SendDiSEqCCommand after the TuneRequest, but unfortunately it has not made a difference, see log attached.

Did you see this post? It suggests to send the diseqc command just after the initial successful graphrun. Same suggestion here.

In my log file, I found it interesting to see the device is detected as a "PCTV 292e/461e BDA 28179 TVTuner", i.e. not Hauppauge ("Hauppauge: DVB-S card NOT found!") but a "generic" BDA tuner: "GenericBDASiSEqC capable card found!". As a result, it might not apply any Hauppauge specific diseqc instructions / sequences?

 

[Pablik]

In my log file, I found it interesting to see the device is detected as a "PCTV 292e/461e BDA 28179 TVTuner", i.e. not Hauppauge ("Hauppauge: DVB-S card NOT found!") but a "generic" BDA tuner: "GenericBDASiSEqC capable card found!". As a result, it might not apply any Hauppauge specific diseqc instructions / sequences?

Hmm.. I see in the code that hauppague uses specific sequence.
You might be right. I'll try to prepare a new dll ...

 

[Pablik]

The Hauppauge tunner is detected via KSProperty with specific guid. It's not detected with your tunner. I'm out of ideas.
You can try to contact Hauppauge support.

 

[AberDino]

Had a look online, and it turns out the PCTV product line was part of Pinnacle Systems, which in 2008 ended up with Hauppauge. I suspect that's why it has a different KSProperty guid.

The same product is on the Hauppauge website twice; here and here (mine is the WinTV-NOVA-S2). I suspect the products look different on the outside, but are identical on the inside. The USB vendor ID is 2013, which is PCTV Systems. The Hauppauge USB vendor ID is 2040. It also turns out there are multiple revisions of the same product, I've seen references to device IDs 0258 (B6H9), 0461 (B8H9) and 0462 (BBH9), but there might well be more. Mine's the newest 0462, with the Montage M88DS3103C demodulator.

So, although I started this post thinking I had a Hauppauge product, it is in fact a PCTV Systems product, which changes things completely. I suppose it's not unusual for companies to do so.

I will get in touch with Hauppauge support to see if they have any suggestions. Thanks @Pablik for helping out!

 

[Pablik]

Just one thing: from the BVN TV request I can see that both modulation and fec is not set. BVN uses QPSK, 5/6 fec. Can you try manually add these params to the channel?

 

[AberDino]

Just one thing: from the BVN TV request I can see that both modulation and fec is not set. BVN uses QPSK, 5/6 fec. Can you try manually add these params to the channel?

Hi @Pablik, see attached, it does not make a difference. Note that, for some reason, I've never had to populate that data, apart from when I scan DVB-S2 transponders, in which case I need to pre-populate the modulation type before I scan the transponder, at least with the TBS devices.

 

[AberDino]

Brief update... Hauppauge support responded quickly, stating that the "driver for all of our product confirm to the BDA format". Not sure what that means, but to test that, I downloaded a copy of Capture4Me, and indeed, it switches LNBs without any issues with minimal configuration (just set DiSEqC to 1.x A/B/C/D and select the satellites from the drop-down). I have asked that if the Hauppauge technical team have any pointers as to how we could get this to work in MP, to let me know.

This makes me wonder, and please correct me if I am wrong, with TVE3 and TVE3.5 no longer being developed, and it looks like the same applies to TVMosaic Community Edition (last release 2021), what does the future look like for DVB-T/S/C support in MP?