Thanks for your answer, the intention with my "hack" was only to differ between the two different cards since they were listed with the same name in the Device Manager and in the TV server configuration.
Since the orignal poster got things working with a Twinhan and a Terratec card, which actually uses the same driver, that is, MtsBDA.sys. I suppose the driver is relased as a reference driver from the chipset manufacturer. I assumed that the driver actually supports multiple devices.
If we take a look at the tv.log above, we'll try to find a Capture BDA Receiver.
Quote:
2008-07-15 23:47:04.145033 [13]: dvb:AddAndConnectBDABoardFilters
2008-07-15 23:47:04.145033 [13]: dvb: find bda tuner
2008-07-15 23:47:04.145033 [13]: dvb: -DTV-DVB Mantis DVBC BDA Receiver
2008-07-15 23:47:04.145033 [13]: dvb: -DTV-DVB Mantis DVBC BDA Receiver
2008-07-15 23:47:04.160658 [13]: dvb: Render [Network provider]->[Tuner] OK
2008-07-15 23:47:04.176283 [13]: dvb: Find BDA receiver
2008-07-15 23:47:04.176283 [13]: dvb: -DTV-DVB Mantis DVBC Capture BDA Receiver
2008-07-15 23:47:04.191908 [13]: dvb: Render [Tuner]->[Capture] AOK
2008-07-15 23:47:04.191908 [13]: dvb: WinTv CI module not detected.
2008-07-15 23:47:04.191908 [13]: dvb: Render [capture]->[inftee]
2008-07-15 23:47:04.191908 [13]: dvb: OK
|
I assume there will be a corresponding Capture BDA receiver for every BDA receiver. In my case, first my DVB-S Capture BDA Receiver is checked, and then the 1st DVB-T Capture BDA Receiver. It looks like we will always get a hit on the 1st DVB-T Capture BDA Receiver even though we are using the 2nd DVB-T card.
Another example is if card1 is timeshifting and a scan is started on card2, I'll get an unable to start graph in the logs. I guess that is due to the fact that card1 is not idle.