On Sun, 20 May 2007, Alasdair Campbell wrote:

Is this a known problem or is there something more I need to configure
for my specific setup?

Yes, it's a known problem reported only in xineliboutput setups: somehow "cDevice::ActualDevice()->CardIndex()" returns invalid values. I cannot reproduce this error in my FF card setup, so I'm just blaming xineliboutput for messing up VDR's devices and haven't had any efforts to debug it further. :)


vdr mailing list

Reply via email to