[vdr] [Announce] remotetimers-0.1.5

2011-04-18 Thread Frank Schmirler 
Hi there,

remotetimers-0.1.5 is available from http://vdr.schmirler.de. Older versions
no longer compile with VDR 1.7.18.

Changelog:
- Always update help keys when changing user filter in recordings menu
- Fixed wrong help keys in recordings menu when user filter is active
- The "red" key to open a recordings directory didn't work
- No longer using cRecordingInfo::Read(FILE) in VDR 1.7.3+. It's going to
be a private member in VDR 1.7.18
- Added Slovak translation (thanks to Milan Hrala)

Have fun,
Frank

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] preventing vdr from using a device torecord

2011-04-18 Thread Simon Baxter 

Hi,

Am 16.04.2011 16:28, schrieb syrius...@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.





___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr