[vdr] from xineliboutput to ... perhaps softhdddevice?

Hi, I am currently using xineliboutput, and I'm using it with --local=none everywhere so I can attach and detach from anywhere in the LAN, even from the PC VDR is running on. It's working quite nicely this way. Upside: No local configuration on any PC, no concurrency issues with timers,

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

Hi, I'm in the same situation, and most of my friends, using vdr the same way, too. The only software, I currently know which works similar, is VOMP client/server. It is also independant and could be run standalone on Linux and Windows. But it is IMHO only a worst-case-replacement for sxfe. I

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice + vdr + streamdev-client

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

Am 14.04.2015 um 09:56 schrieb Gerald Dachs: Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with