[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, channel updates etc.. just call vdr-sxfe host and you're in the game. Downside: Multiple connected clients at the same time get the same programme, OSD, etc. [skippy/hanging video for adapting to the different client speeds, OSD sizing issues for different client resolutions] Is there an equivalent solution which I read to be a more recent/better supported alternative? AFAIK softhddevice is similar to xineliboutput but lacks remote features, behaves like xineliboutput with --local=sxfe --noremote, but I could be wrong. This doesn't look like a viable alternative to my current network architecture. 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. Is there any other thin-client streaming solution with native VDR OSD available? Any other suggestions? Thanks, - Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
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 also don't want to have a complete vdr environment running, for only watching TV on my laptops or any other remote station. Thanks, Günter --- Am 14.04.2015 um 08:59 schrieb Matthias Wächter: 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, channel updates etc.. just call vdr-sxfe host and you're in the game. Downside: Multiple connected clients at the same time get the same programme, OSD, etc. [skippy/hanging video for adapting to the different client speeds, OSD sizing issues for different client resolutions] Is there an equivalent solution which I read to be a more recent/better supported alternative? AFAIK softhddevice is similar to xineliboutput but lacks remote features, behaves like xineliboutput with --local=sxfe --noremote, but I could be wrong. This doesn't look like a viable alternative to my current network architecture. 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. Is there any other thin-client streaming solution with native VDR OSD available? Any other suggestions? Thanks, - Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- This message was scanned by ESVA and is believed to be clean. Click here to report this message as spam. http://esva.nk-hosting.de:10080/cgi-bin/learn-msg.cgi?id=D68AC160087.AB80D -- This message was scanned by ESVA and is believed to be clean. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
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 on the clients and connect to a streamdev-server on the main vdr. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
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 streamdev. use softhddevice + vdr + streamdev-client on the clients and connect to a streamdev-server on the main vdr. Gerald Well, that works so far, but it is not an effective substitute for the functionality of vdr-sxfe, at least not for what I use it mainly. All functions run on the remote machine, and only the screen is transferred to the local machine. -Günter -- This message was scanned by ESVA and is believed to be clean. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
