Thomas Schmidt <[EMAIL PROTECTED]> writes: > Yes, i am aware of the streamdev-plugin, we have inofficial packages > of this plugin (and many other plugins) allready in our repositories: > > http://svn.debian.org/wsvn/pkg-vdr-dvb/vdr/?rev=0&sc=0 > http://www.e-tobi.net/wsvn/vdr-pkg/?rev=0&sc=0
Thanks. I've co'ed the svn repository and compiled the streamdev plugins. > It is planned to integrate a lot of these plugins in the official > archive but i guess most of this work will be done when vdr 1.4 is > stable. ;-) Let me do some beta test ;-) > I guess you installed the plugin manually, so both plugins are > installed, but you just need the -server plugin? Yes. I will need the -client plugin for a second instance of vdr that will be started from a X session with softdevice plugin. > Well, i think it is much more user-friendly when every plugin which is > installed is loaded by default, This makes sense for most plugin. But other plugin do not make sense for a daemon instance of vdr. For instance, softdevice plugin needs a X server to connect to and a daemon is not started from a X session. So loading softdevice plugin by default in *daemon* mode may be confusing to user (and it may break the daemon). > you can disable certain plugins, in > your case a line like the following would be sufficient: > > -streamdev-client > > I hope this will solve your problem, so i can close this bug! :) It does solve my problem, so you can close this bug. Still, I'm somewhat worried about ease of use for some plugins, but I concede that it can be ironed out later when vdr and most plugins have somewhat stabilized ;-) HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]