plugin deployment
local (client) VDR remote (server) VDR
remotetimers svdrpservice access for client IP granted in svdrphosts.conf  
remoteosd svdrposd
peer peer (optional)
femon femon

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.

Plugin svdrpservice

svdrpservice > README > HISTORY
2013-06-07 > vdr-svdrpservice-1.0.0.tgz
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.

Plugin remotetimers

remotetimers > README > HISTORY
2015-07-29 > vdr-remotetimers-1.0.2.tgz
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.

Additional features:

Plugin remoteosd

remoteosd > README > HISTORY
2013-06-07 > vdr-remoteosd-1.0.0.tgz
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:

Requirements remote (server) VDR: So you will need to download all three plugins and install them in the right place!



Plugin svdrposd (formerly svdrpext)

svdrposd > README > HISTORY
2013-06-07 > vdr-svdrposd-1.0.0.tgz
2011-08-01 > vdr-svdrposd-0.1.1.tgz (VDR < 1.7.36)

Publishes the OSD menu via SVDRP. Server-side counterpart of remoteosd.

Plugin peer

2013-08-12 > vdr-peer-0.0.1.tgz

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:

Plugin epgsync

epgsync > README > HISTORY
2014-04-11 > vdr-epgsync-1.0.1.tgz
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 >

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...