|local (client) VDR||remote (server) VDR|
|remotetimers||svdrpservice||access for client IP granted in svdrphosts.conf|
With the streamdev plugin it is easy to build up a client/server environment with VDR. While VDR-to-VDR streaming works like a charm, there's not a lot the client can do on the server. The plugins on this page are the missing pieces to a powerful multi-VDR environment.
Please carefully check the deployment matrix on the right. It shows dependencies between plugins, whether the plugin needs to be installed on the client or server VDR and additional requirements.
|2008-09-25||vdr-svdrpservice-0.0.4.tgz (VDR < 1.7.36)|
This plugin offers SVDRP connections as a service to other plugins. Instead of implementing the same SVDRP connectivity stuff over and over again, all of my client side plugins use svdrpservice. So it is even possible to share a single SVDRP connection among multiple plugins on the same client.
There's no reason to load this plugin if no other plugin relies on it. If you are a developer and your plugin needs connections to a remote SVDRP server, you might want to take a closer look at it.
|2012-06-27||vdr-remotetimers-0.1.7.tgz (VDR < 1.7.36)|
Allows you to add/edit/delete timers on the local (client) VDR and a remote (server) VDR. Even moving timers between the two VDRs is possible. The plugin has its own implementations of the Schedule and Timer menus, since 0.1.0 also of the Recordings menu. All of them are feature extended copies of VDR's original menus.
Remotetimers requires plugin svdrpservice.
- Multiuser support: Individual user IDs can be assigned to timers and (since 0.1.0) recordings. Recordings inherit the user IDs of the timer. The timer and recodings lists can be filtered by user ID. Deleting an item will then just clear the user's ID in the timer or recording. Clearing the last user ID will actually delete the timer or recording.
- Edit recordings menu allows you to rename recordings and change priority or lifetime (since 0.1.0)
- Move recording to different filesystem in the background (since 0.1.4)
- Server-side cutting of recordings (since 0.1.0)
- Patch for redirecting instant recordings to the server (since 0.1.0)
- Show available disk space of the actual filesystem for recording subdirectories on different mounts (since 0.1.2)
- Show epgsearch conflicts in timers menu (since 1.0.1)
- Progress bars in the "What's on now?" menu (since 0.1.0)
- Swap key bindings of "Ok" and "Blue" in "What's on" menus (since 0.1.1)
- Custom EPG times in addition to "Now" and "Next" in "Schedule" menu (since 1.0.1)
- Show size and length of recording in "Edit recording" and "Recording info" menus (since 0.1.2)
- Automatic update of recordings list when server's recordings are mounted as a subdirectory of the local video directory (since 0.1.0) or when local video directory is mounted/unmounted (since 0.1.1)
- Backport of VDR 1.7.12's folders.conf for easy subdirectory selection in "Edit timer" and "Edit recording" menus (since 0.1.3)
- Support for MainMenuHooks patch. The VDR mainmenus can be replaced by remotetimers' counterparts
|2011-09-20||vdr-remoteosd-0.1.1.tgz (VDR < 1.7.36)|
Allows your (client) VDR to operate the menu of a remote (server) VDR. You can e.g. edit timers and channels, run commands from the commands menu or change the setup of the remote VDR. Especially if you are running a headless streaming server somewhere in the cellar, this plugin comes in handy.
Requirements local (client) VDR:
- plugin remoteosd
- plugin svdrpservice
- plugin svdrposd (or it's predecessor svdrpext)
- Plugin asks for confirmation if remote menu is already in use
- To make it easier to distingues the local and the remote menu, the server IP is prepended to every remote menu title and message. In the plugin setup you can even select a different color theme for the remote menu
- Support for MainMenuHooks patch. You can replace the local "Schedule" and "Timers" menu by the corresponding remote menu. Please apply remoteosd-readconfig.diff if you want to use this feature. Otherwise the setting will be lost every time you restart VDR.
- OSD menu pops up on the server. There's no concurrent access
- Limitations of VDR status interface apply (e.g. no event title/subtitle). Just text, no graphics (like e.g. femon output)
Plugin svdrposd (formerly svdrpext)
|2011-08-01||vdr-svdrposd-0.1.1.tgz (VDR < 1.7.36)|
Publishes the OSD menu via SVDRP. Server-side counterpart of remoteosd.
Add this plugin if you don't have a client/server environment (i.e. all recordings done on one server) but rather peer-to-peer (multiple VDRs, all with their own DVB cards). But also for the client/server guys the plugin might include some handy features.
The requirements of this plugin heavily depend on the features you want to use. To use all features, you would have to grant SVDRP access for all peers and install the plugins peer, remotetimers, remoteosd, svdrposd and svdrpservice on all peers. Check the README for the exact requirements by feature.
After you've added all peer VDR in the plugin setup, the plugin can do the following things:
- Add/edit/remove timers on local and peer VDR or move timers between them (using remotetimers-plugin)
- Access menu of peer (using remoteosd-plugin)
- Send an OSD message to peer
- Show device status of peer
- Get notified next time replay finishes on peer
- Send a Wake-on-LAN magic packet to peer
|2010-04-19||vdr-epgsync-0.0.4.tgz (VDR < 1.7.36)|
Imports the EPG of an other VDR. It is implemented as a separate thread and you can select either a quick but resource consuming or a slow operation mode. The later allows you to share the SVDRP connection with other local plugins, so you can e.g. still use the remoteosd plugin while syncing.
Since epgsync-0.0.3 it is possible to limit the import to a specific channel type (DVB-C/S/T, analog) and to lookup channels by name instead of ID. You could e.g. copy the EPG of DVB channels to their analog counterparts.
You have to install plugin svdrpservice >= 0.0.2 along with epgsync.
Femon SVDRP extension
Running a headless streaming server and worried about how to monitor the signal quality? Since 1.1.0 femon is able to retrieve the frontend status remotely via SVDRP. You can download the plugin at http://www.saunalahti.fi/~rahrenbe/vdr/femon/.
Simply install the new femon on both, client and server. On the client you will also need the svdrpservice plugin >= 0.0.2. Finally enable the SVDRP feature in the femon setup on the client. It's a good idea to install the dummydevice plugin >= 1.0.1 on the server, unless you have some output device attached.
Thanks to Rolf Ahrenberg for integrating my patches into femon. Keep on with the great work!
All software on this site is licensed GPL. There's absolutely no warranty. Don't blame me if your girl friend misses her daily soap...