VDR User user.vdr@gmail.com writes:

On Sat, Apr 16, 2011 at 7:28 AM, syrius.ml@no-log.org wrote:

...

I'm now running one vdr instance with 4 dvb devices. One device is crashing quite often and I haven't find a way to automatically detect when it's crashed. (vdr used to issues "unknown picture type message in the past)

If you're not seeing anything useful to your VDR log to determine if the card has crashed, you may want to look at dmesg to see if something in there could be used.

Some years ago vdr was reporting the bad picture types when they occured. Now i've got no means to detects them on the server (neither in vdr logs nor in kernel messages)

vdr-sxfe output complains it can't demultiplex the stream, but that won't work when I'm away and nobody's watching tv. That won't prevent vdr from using the bad card.

My question still remains :) I don't mind patching vdr (changing getdevice or something else). If there's no existing patch or plugin, could you give me some input on what to change to prevent vdr from using one card for recordings and epg scans ?

TIA.

Klaus Schmidinger Klaus.Schmidinger@tvdr.de writes:

You could start by patching the function

cDevice *cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView)

ok thanks, that's what i thought.

But wouldn't it be better to just replace that faulty device altogether?

it's a dvb-ttpci rev1.5 card, i'll try the full-ts mod. I haven't planned to buy a new card yet, I'd rather patch and get dirty with vdr :-)

VDR User user.vdr@gmail.com writes:

On Sun, Apr 17, 2011 at 2:36 AM, syrius.ml@no-log.org wrote:

...

vdr-sxfe output complains it can't demultiplex the stream, but that won't work when I'm away and nobody's watching tv. That won't prevent vdr from using the bad card.

If the vdr-sxfe log gives you useful text for this, why can't you simply write a script that runs in the background and checks for such text every X seconds. If the text is found, it can do whatever you normally do to fix the problem.

I do something similar to detect xine crashes and it works fine. Although my preference would be the "buffer usage: 100%" crash would be fixed once and for all. ;) But that's another issue..

Thanks for your answer, but you should reckon that checking vdr-sxfe won't help preventing vdr from using a crashed card for the timed recordings.

I could do something similar if the driver was reporting that the card had crashed, and thanks to the dynamite patch I could remove the device, reload the driver and re-insert it.

I'm going to patch getdevice so that the faulty card is only used for live view.

Hi,

Am 16.04.2011 16:28, schrieb syrius.ml@no-log.org:

...

I'm now running one vdr instance with 4 dvb devices. One device is crashing quite often and I haven't find a way to automatically detect when it's crashed. (vdr used to issues "unknown picture type message in the past)

I'd like to prevent vdr from using it for recordings. Do you know of any plugin or patch that help achieving this ?

Ideally I'd love to be able to set priorities and properties to devices. Something like: device #1: can_record, can_do_epg_scan, can_do_liveview, devprio=100 device #2: can_record, can_do_epg_scan, can_do_liveview, devprio=90 device #3: can_do_liveview, devprio=10

Is there a way for plugins to alter *cDevice::GetDevice behavior ? Are there any plans on that matter ?

Please modify the attached plugin, telling that device 3 doesn't provide any transponder.

Would this also work if only a CAM device has crashed? I have multiple DVB-C cards each with their own CAM. Occasionally the CAM either crashes to "CAM Ready" state (rather than "Alphacrypt" in the CAM menu) or just fails to respond - either way, the CAM needs often multiple RESETS from the CAM menu.