Community maintained VDR projects

Finally I managed to add some items to the OSD for controlling dynamite.

With your remote control you can now:

• list the attached devices
• scan for new DVB devices (search pattern /dev/dvb/adapter*/frontend*)
• detach a device
• lock/unlock a device
• switch a device to idle

There are two new udev device properties which can be used by dynamite to control which devices should be attached and which not.

To keep /dev/dvb/adapter2/frontend* from being attach to every vdr instance:

ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}=="2", ENV{dynamite_attach}="no" 

This would attach /dev/dvb/adapter2/frontend* to the vdr with the instance id "1" and all other frontends to the vdr instance "0":

ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}=="2", ENV{dynamite_instanceid}="1" 
ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}!="2", ENV{dynamite_instanceid}="0" 

To bridge gaps in the numbering of the dvb adapters dynamite uses udev to scan for dvb frontends at startup.
This ensures that every frontend will be found even if they are /dev/dvb/adapter1, /dev/dvb/adapter5 and /dev/dvb/adapter7.

New version of markad released

A new release of vdr-plugin-dvdswitch

More details at: http://projects.vdr-developer.org/projects/plg-dvdswitch/wiki

Changes :

• Read name of volume to prefill OSD-Entry with filename
  Fill OSD-field with capitalize volume name
• Improve menu to read images
• Rename image was'nt possible
• used posix functions to parse commandline, create symbolic links, parse mountpoint
• Improve handle of error messages
• Update translations
  Add italian translation (Support #490)
• refactoring MenuSetup
  Allow localized character at title of image menu
• remove some unused code, typecast ...

Initial release of xmltv2vdr

Please read the README included or http://vdr-wiki.de/wiki/index.php/Xmltv2vdr-plugin

New version of markad released

What it should do
set device to idle
=> device close all its handles
=> device is ignored by epg-scan
=> any receiver/timer etc. will reactivate the device

Issues

• dvbdevice doesn't close its ca, only frontend and demux are closed till now
• no automatism for setting a device into idle mode

(patch of vdr is modified)

add to your setup.conf:

dynamite.GetTSTimeoutHandler = /path/to/program

This program will be called with the devpath of the detached device as an argument.

You can replace this argument with the value of the udev-device-property "dynamite_timeout_handler_arg":

ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_DEVICE_TYPE}=="frontend", ENV{dynamite_timeout}="5", ENV{dynamite_timeout_handler_arg}="%k"

In this example "%k" expand to "dvb0.frontend0" for the first dvb-device.

What is missing:
dynamite doesn't enumerate the udev-device-properties of the device at startup, so "dynamite_timeout_handler_arg" onyl works for devices attached by the udev-monitor.

it's on the todo list...

New version of markad released

version 0.1.9 is available; graphlcd now supports the SPAN plugin and (remote)control via SVDRP.

download: http://projects.vdr-developer.org/projects/graphlcd/files