Can you explain it more. What is "the right module" ? I have 2 dvb card, one nova-s and one nova-t. with szap i can use my nova-t. With vdr no success, i have "unavailable channel" when i switch to dvb-t channel.<br>
Plz help...<br><br><div class="gmail_quote">2008/11/15 Tony Houghton <span dir="ltr"><<a href="mailto:h@realh.co.uk">h@realh.co.uk</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sat, 15 Nov 2008 19:48:16 +0000<br>
Tony Houghton <<a href="mailto:h@realh.co.uk">h@realh.co.uk</a>> wrote:<br>
<br>
> Nice theory, but ti doesn't work in practice for me. With just the DVB-T<br>
> channels in channels.conf (I haven't got the DVB-S card working yet) and<br>
> the DVB-S card present I get "Channel unavailable" on every single<br>
> channel. Without the DVB-S card present VDR can use the DVB-T card.<br>
><br>
> Could it be a clash because both cards have a Philips SAA7146 chip<br>
> (they're both Hauppauge WinTV Nova PCI models)? If so, this problem only<br>
> arises if you try to open both cards at once, or it's unique to VDR,<br>
> because other dvb utils such as scan, tzap and dvbstream do work on the<br>
> DVB-T card when the DVB-S card is present.<br>
<br>
</div>OK, it seems that it was the problem with the DVB-S card that was<br>
blocking the DVB-T card too. Once I got the right module installed for<br>
the DVB-S's frontend VDR could use the DVB-T card properly.<br>
<div><div></div><div class="Wj3C7c"><br>
--<br>
TH * <a href="http://www.realh.co.uk" target="_blank">http://www.realh.co.uk</a><br>
<br>
_______________________________________________<br>
vdr mailing list<br>
<a href="mailto:vdr@linuxtv.org">vdr@linuxtv.org</a><br>
<a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr" target="_blank">http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a><br>
</div></div></blockquote></div><br>