Alexw alexw@undercover.mine.nu writes:

I an using xineliboutput through network in udp without any issue. Switching between channels is fine even better than xine plugin. By the way I am running both xine and xineliboutput plugins at the same time on the VDR side and a xine library patched with xine plugin + network and the xineliboutput input plugin. I have no conflict at all and both are usable (not at the same time ;-)

For xine plugin: xine --auto-play=q --no-splash --deinterlace --post vdr -A alsa vdr-socket:/<vdr-ip>#demux:mpeg_pes

With xineliboutput"

vdr-sxfe --verbose --video xv --post tvtime xvdr:udp://<vdr-ip> <-- working fine, xvmc not osd,no control and xxmc control ok, osd bad color space

xine -V xxmc "xvdr://<vdr-ip>:37890#nocache;demux:mpeg_block" <-- picture, sound but no control, no OSD and --stdctl does not help

lucky you. I'm not kidding when I'm saying it's segfaulting all the time. (the frontend) I'll try to gdb it later. btw i'm using xine-{lib,ui} from yesterday cvs head.

anyway working osd and control are required features for us. (the woman indoor is going to laugh at me if i sacrifice features and nice osd for a 1/100 second difference when zapping) ;-)

Alexw alexw@undercover.mine.nu writes:

I an using xineliboutput through network in udp without any issue. Switching between channels is fine even better than xine plugin. By the way I am running both xine and xineliboutput plugins at the same time on the VDR side and a xine library patched with xine plugin + network and the xineliboutput input plugin. I have no conflict at all and both are usable (not at the same time ;-)

For xine plugin: xine --auto-play=q --no-splash --deinterlace --post vdr -A alsa vdr-socket:/<vdr-ip>#demux:mpeg_pes

With xineliboutput"

vdr-sxfe --verbose --video xv --post tvtime xvdr:udp://<vdr-ip> <-- working fine, xvmc not osd,no control and xxmc control ok, osd bad color space

xine -V xxmc "xvdr://<vdr-ip>:37890#nocache;demux:mpeg_block" <-- picture, sound but no control, no OSD and --stdctl does not help

hi,

I've been able to use it correctly (without the segfaults) . I was using vdr-xine-0.7.9 patches on top of xine-lib and it was working correctly. (neither vdr-xine + network patch btw). I went back to 0.7.7 and it's now ok. The only way i can run both plugins is to put xineliboutput first in the command line. But in that case watching tv with xine vdr-socket:/ doesn't work.

unfortunatly since I use freevo the xineliboutput plugin can't replace vdr-xine. Freevo controls vdr thru xine --stdctl and vdr-xine. (the --lirc option won't help in that case)

I just hope next vdr-xine will have the same kind of network possibilities. (Even if I haven't tried with xineliboutput, the ability to connect several network players is very nice and i would use it a lot)

BTW, vdr-xine + network-patch users, Am I the only one to have buffering issues with latest vdr-xine (Version > 0.7.7) ? here it was rebuffering a lot, the video was jerky (and sound desynchronised) and on vdr side buffer usage was always increasing up to 100%. (i've downgraded to vdr-0.7.7 to fix thoses issues)

Talking about vdr-xine and xineliboutput, has anybody considered writing a xine input plugin for streamdev ? I dream up of a magic streamdev plugin that does smart multicast diffusion and xine/mplayer/whatever clients able to watch differents channels (from different transponders when there're several dvb cards)

That would be nice, wouldn't it ? :) since vdr has been very nicely written i guess it's not a big deal to consider multi-{networked or not networked}-display now :)