Hi, Since you're using two different drivers, have you tried the module parameter "adapter_nr"? Then you will be able to make the DVB-C card always adapter0 and the others 1-4. See "modinfo <driver>". Lars. Am 18.08.2013 19:27, schrieb Brian-Imap: > On 8/15/2013 9:08 PM, Brian-Imap wrote: >> On 8/15/2013 5:58 PM, Arthur wrote: >>> 15.08.2013 18:37, Brian-Imap kirjutas: >>>> On 8/14/2013 10:16 PM, Arthur wrote: >>>>> 14.08.2013 19:01, Brian-Imap kirjutas: >>>>>> On 8/11/2013 11:43 AM, Brian-Imap wrote: >>>>>>> On 8/8/2013 10:22 PM, Lars Hanisch wrote: >>>>>>>> Am 08.08.2013 16:23, schrieb Brian-Imap: >>>>>>>>> On 8/7/2013 9:58 PM, Lars Hanisch wrote: >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Am 07.08.2013 21:04, schrieb Brian-Imap: >>>>>>>>>>> Hi, >>>>>>>>>>> I now a have a 4 Tuner Cine S2 setup that I want to run with 3 >>>>>>>>>>> cables, I want to keep the fourth cable for a test VDR. >>>>>>>>>>> Reading about this I only see how to do it together with the >>>>>>>>>>> Dynamite Plugin, is that correct that I must use that >>>>>>>>>>> Plugin to get it to work for VDR? >>>>>>>>>>> >>>>>>>>>>> I am currently running a plain VDR setup on Ubuntu, with very few >>>>>>>>>>> plugins and had no need for the Dynamite Plugin >>>>>>>>>>> up till now. >>>>>>>>>> You don't really need dynamite. If you want to omit the fourth >>>>>>>>>> tuner (in kernel count order), you can start vdr with >>>>>>>>>> the -D parameter (see vdr --help). >>>>>>>>>> >>>>>>>>>> vdr -D0 -D1 -D2 <other parameters as usual> >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Lars. >>>>>>>>>> >>>>>>>>>>> Cheers Brian >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> vdr mailing list >>>>>>>>>>> vdr@xxxxxxxxxxx >>>>>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> vdr mailing list >>>>>>>>>> vdr@xxxxxxxxxxx >>>>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>>>>>> Hi Lars, >>>>>>>>> >>>>>>>>> OK I knew about this, but I thought that the Card/Tuners numbers >>>>>>>>> could change >>>>>>>>> from boot to boot. Are you saying that they will not change? >>>>>>>> If it's one bridge with 4 tuners, I doubt their order will change. >>>>>>>> >>>>>>>> You may want to read about "device bonding", where you split one >>>>>>>> cable on two tuners so they share polarisation and >>>>>>>> band, but may be tuned to different transponders. >>>>>>>> >>>>>>>> But I'm a cable user, I don't know much about it, just that there >>>>>>>> are some people out there who use it successfully. :) >>>>>>>> >>>>>>>> Regards, >>>>>>>> Lars. >>>>>>>> >>>>>>>>> Cheers Brian >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> vdr mailing list >>>>>>>>> vdr@xxxxxxxxxxx >>>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> vdr mailing list >>>>>>>> vdr@xxxxxxxxxxx >>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>>>>> >>>>>>> Hi, >>>>>>> thanks for the tips, unfotunately I ended up needing to keep using a >>>>>>> FF Card for a short while. >>>>>>> >>>>>>> So I followed the CT tip and added a TT C-2300 Cable FF card that is >>>>>>> not connected to cable at all. >>>>>>> That part seems to work really well. >>>>>>> >>>>>>> Using the -D parameter in VDR I limited VDR to using the first 4 DVB >>>>>>> Devices and this is what it gave me: >>>>>>> >>>>>>> Aug 11 11:09:31 localhost vdr: [936] frontend 0/0 provides >>>>>>> DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard") >>>>>>> Aug 11 11:09:31 localhost vdr: [936] frontend 1/0 provides DVB-C with >>>>>>> QAM16,QAM32,QAM64,QAM128,QAM256 ("ST STV0297 DVB-C") >>>>>>> Aug 11 11:09:31 localhost vdr: [936] frontend 2/0 provides >>>>>>> DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard") >>>>>>> Aug 11 11:09:31 localhost vdr: [936] frontend 4/0 provides >>>>>>> DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard") >>>>>>> >>>>>>> So tuners 1-3 of the Cine S2 and Duoflex are now in use. DBV device 1 >>>>>>> provides nothing but MPEG output. >>>>>>> >>>>>>> I guess I'll keep an eye on the DVB device ordering for a while to see >>>>>>> how it goes. >>>>>>> >>>>>>> Cheers Brian >>>>>>> _______________________________________________ >>>>>>> vdr mailing list >>>>>>> vdr@xxxxxxxxxxx >>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>>>> >>>>>> Hi, >>>>>> well the DVB device numbering is not consistent: >>>>>> >>>>>> "VDR-Test-Cellar(SDA2): 15:25 [995] frontend 3/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 15:25 [995] frontend 2/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 15:25 [995] frontend 1/0 provides DVB-C with >>>>>> QAM16,QAM32,QAM64,QAM128,QAM256 (""ST STV0297 DVB" >>>>>> "VDR-Test-Cellar(SDA2): 15:25 [995] frontend 0/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> >>>>>> "VDR-Test-Cellar(SDA2): 05:10 [1018] frontend 3/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 05:10 [1018] frontend 2/0 provides DVB-C with >>>>>> QAM16,QAM32,QAM64,QAM128,QAM256 (""ST STV0297 DV" >>>>>> "VDR-Test-Cellar(SDA2): 05:10 [1018] frontend 1/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 05:10 [1018] frontend 0/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> >>>>>> "VDR-Test-Cellar(SDA2): 06:52 [1080] frontend 3/0 provides DVB-C with >>>>>> QAM16,QAM32,QAM64,QAM128,QAM256 (""ST STV0297 DV" >>>>>> "VDR-Test-Cellar(SDA2): 06:52 [1080] frontend 2/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 06:52 [1080] frontend 1/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 06:52 [1080] frontend 0/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> >>>>>> "VDR-Test-Cellar(SDA2): 19:16 [1015] frontend 3/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 19:16 [1015] frontend 2/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> "VDR-Test-Cellar(SDA2): 19:16 [1015] frontend 1/0 provides DVB-C with >>>>>> QAM16,QAM32,QAM64,QAM128,QAM256 (""ST STV0297 DV" >>>>>> "VDR-Test-Cellar(SDA2): 19:16 [1015] frontend 0/0 provides >>>>>> DVB-S,DVB-S2,DSS with QPSK (""STV090x Multistandard"")" >>>>>> >>>>>> Up till now it has not been a problem, the one without a cable must be >>>>>> 4/0. Still I am wondering if this can be controlled? >>>>>> Before VDR start unload the DVB drivers, then load DVBTTPCI first and >>>>>> give it a short delay and then load DDBridge maybe? >>>>>> Still, then is it then guaranteed that DDBridge will number its 4 tuners >>>>>> correctly? >>>>>> >>>>>> Cheers Brian >>>>>> >>>>> >>>>> Do you tried udev rules for controlling multiple DVB device numbering? >>>>> >>>>> br, >>>>> Arthur >>>>> >>>>> >>>>> _______________________________________________ >>>>> vdr mailing list >>>>> vdr@xxxxxxxxxxx >>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>>>> >>>> Arthur, >>>> No. Please tell me how? >>>> Cheers Brian >>>> >>>> >>> >>> At the moment I don't use it, but I found it from my archive. >>> Attached file has been placed in the /etc/udev/rules.d folder in my Slackware PC. >>> >>> br, >>> Arthur >>> >>> >>> >>> _______________________________________________ >>> vdr mailing list >>> vdr@xxxxxxxxxxx >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> Arthur, thanks very much >> >> I'll only get around to trying it at the weekend though. >> >> Cheers >> >> >> >> _______________________________________________ >> vdr mailing list >> vdr@xxxxxxxxxxx >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi, > so I tried to look for some kind of info to help me identify the tuners, this is the most interesting bit I guess: > > VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter1/frontend0 --attribute-walk > looking at device '/devices/pci0000:00/0000:00:0d.0/0000:02:00.0/dvb/dvb1.frontend0': > KERNEL=="dvb1.frontend0" > SUBSYSTEM=="dvb" > DRIVER=="" > > VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter0/frontend0 --attribute-walk > looking at device '/devices/pci0000:00/0000:00:0d.0/0000:02:00.0/dvb/dvb0.frontend0': > KERNEL=="dvb0.frontend0" > SUBSYSTEM=="dvb" > DRIVER=="" > > VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter2/frontend0 --attribute-walk > looking at device '/devices/pci0000:00/0000:00:0d.0/0000:02:00.0/dvb/dvb2.frontend0': > KERNEL=="dvb2.frontend0" > SUBSYSTEM=="dvb" > DRIVER=="" > > VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter3/frontend0 --attribute-walk > looking at device '/devices/pci0000:00/0000:00:06.0/0000:01:06.0/dvb/dvb3.frontend0': > KERNEL=="dvb3.frontend0" > SUBSYSTEM=="dvb" > DRIVER=="" > > VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter4/frontend0 --attribute-walk > looking at device '/devices/pci0000:00/0000:00:0d.0/0000:02:00.0/dvb/dvb4.frontend0': > KERNEL=="dvb4.frontend0" > SUBSYSTEM=="dvb" > DRIVER=="" > > At the moment I cannot find anything to identify the 4 Tuners on the Cine S2, the FF on 01:06 is easy. > I got hit by tuning problems a few days ago as the tuner without a cable was given FE3/0. The FF got FE4/0 > at that time. I'm wondering if the DDBridge driver will always number in the correct order. > > So I guess I'll try to make the FF FE0/0, and hope that the DDBRidge driver will do the rest. > > Cheers Brian > > > > > > > _______________________________________________ > vdr mailing list > vdr@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
