Re: AW: [vdr] Xineliboutput with DirectFB
On Thursday 02 November 2006 21:44, Tony Houghton wrote: > Another good reason to use xineliboutput instead of softdevice is that > xine is much better at A/V sync than softdevice IME. I got interested in this and tried things out. Neither xine nor xineliboutput plugins are working. The df_xine works, but I can't find the xine plugin pipes anywhere. Coudn't find a way to turn up verbosity as to see where it fails either. Also tried the xineliboutput, there I have some garbled mess on the TV screen. Apparently there is an option video.device.directfb_layer_id that supposedly allows selecting the layer manually, since the automatic selection doesn't pick the correct one for the Matrox card. It doesn't seem to work, at least the same way it works with df_xine. Ah well. -- -jaakko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput letterbox & mplayer problems
When I use vdr-xine, I start it with "xine --fullscreen --hide-gui -V xv -A alsa -D --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes" for xine use this -P"xineliboutput --primary --local=none --remote=37890" -P"xineliboutput --primary --local=sxfe --remote=none" I'm getting video/audio slips when playing back VDR recordings every 2-3 minutes. The console shows: video_out: throwing away image with pts 124350653 because it's too old (diff : 29229). video_out: throwing away image with pts 124359662 because it's too old (diff : 20220). video_out: throwing away image with pts 23516102 because it's too old (diff : 25112). video_out: throwing away image with pts 23525111 because it's too old (diff : 16103). 200 frames delivered, 17 frames skipped, 3 frames discarded any ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput letterbox & mplayer problems
I get a letterbox window in the middle of the gnome screen. So I tried: -P'xineliboutput --fullscreen --local=sxfe --video=xxmc --audio=alsa --remote=none' ... When I use vdr-xine, I start it with "xine --fullscreen --hide-gui -V xv -A alsa -D --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes" for xine use this -P"xineliboutput --primary --local=none --remote=37890" -P"xineliboutput --primary --local=sxfe --remote=none" plus Udo's suggestion on the options hidden in plugin config works great! What a sweet plugin! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr_remote 0.4
Hello all, I´d like to announce the release of vdr_remote 0.4. vdr_remote is a graphical cross-platform remote control utility. It offers a remote control like interface and can be controlled by keyboard input. Project homepage: http://sourceforge.net/projects/vdr-remote-app vdr_remote can be downloaded as: - Source Code - Windows binary (Win98 and up, Win95 might work) - MacOSX binary (10.4 and up) - SuSE 10.1 rpms (these aren´t tested, please post your experiences) with kind regards Peter Marquardt ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput letterbox & mplayer problems
> I get a letterbox window in the middle of the gnome screen. So I tried: > -P'xineliboutput --fullscreen --local=sxfe --video=xxmc --audio=alsa > --remote=none' ... When I use vdr-xine, I start it with > "xine --fullscreen --hide-gui -V xv -A alsa -D --post vdr_video --post > vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes" for xine use this -P"xineliboutput --primary --local=none --remote=37890" xine "xvdr:tcp://127.0.0.1:37890#nocache;demux:mpeg_block" # for tcp xine "xvdr:udp://127.0.0.1:37890#nocache;demux:mpeg_block" # for udp -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput letterbox & mplayer problems
Simon Baxter wrote: If I start the plugin with : vdr -P"xineliboutput --local=sxfe --video=xv --audio=alsa --remote=none" I get a letterbox window in the middle of the gnome screen. So I tried: -P'xineliboutput --fullscreen --local=sxfe --video=xxmc --audio=alsa --remote=none' This gives me the same as above, but with black borders filling the screen. Still a much smaller picture than the full screen I get with vdr-xine. There are some display options hidden in setup-> plugins-> xineliboutput-> local fronted, and some more under video. Playing with these fixed all problems I had. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] channels.conf keeps falling back to old version
hi list i have a strange phaenomenum here. i kill vdr, edit the channels.conf with a texteditor, start vdr again and vdr reads the new channels file correctly. after some time (minutes) vdr automagically switches back to it's former channels.conf file and overwrites the new (edited) file. i have no idea why. i use vdr-1.4.3-1 w/ bigpatch. plugins (all latest versions): control dvd dvdselect epgsearch extrecmenu mp3ng remote pls help! ;) regards j.schoeller ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput letterbox & mplayer problems
I've been trying xineliboutput for the first time - looks like it will solve all sorts of problems I've been having, if I can get over these ones Problem number 1: If I start the plugin with : vdr -P"xineliboutput --local=sxfe --video=xv --audio=alsa --remote=none" I get a letterbox window in the middle of the gnome screen. So I tried: -P'xineliboutput --fullscreen --local=sxfe --video=xxmc --audio=alsa --remote=none' This gives me the same as above, but with black borders filling the screen. Still a much smaller picture than the full screen I get with vdr-xine. Also, when I change channels (PVR with pvrinput plugin) the various channel scaling leaves parts of the picture around the new "letterbox" image. How do I set scaling? When I use vdr-xine, I start it with "xine --fullscreen --hide-gui -V xv -A alsa -D --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes" Problem number 2: I have been using the mplayer plugin to play divx/xvid/mpeg movies. It's rather clumsy though, as I need to kill xine and restart after (scripted) to free up the xxmc/xvmc resources. When I try and play an avi file with xineliboutput, I get stuttering video and loads of the following: bad_frame [mpeg4 @ 0x125b4e4]header damaged What does work well, which I'm VERY pleased with, is DVD playback. I've had a long standing problem with intermittant audio stuttering - which seems to be resolved with xineliboutput! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev client & server contention
"Simon Baxter" <[EMAIL PROTECTED]> writes: I've been trying all the available modes in the streamdev-server to find the one that suits my needs best. I have 2 VDRs, a server and a client. Ideally, I'd like them both to be able to change channel - and when the transponders need to change, one will just force the other to change as well. This is sort of possible with the"Client may suspend" set to "offer", but has some problems. Do you really need two vdr running ? Would vdr-xineliboutput help ? You could have several frontends watching the same channel. (and every frontent can change the channel) Wow, thanks for the suggestion. I've not looked at that one... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr exit codes?
JikJikMan wrote: > Hi all, > > Does VDR had exit codes? I mean, how could I find what is the cause of > VDR exit? > > For example, I want to know is the VDR exit for storage failure, driver > failure, timers.conf failure or any thing else. > > It is because I wrote a script for restarting my system when vdr exits, > but I want to prevent this for errors that are persistent, like hard > disk failure, or timers.conf file failure. Those are explained in the vdr(1) man-page. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr exit codes?
Hi all, Does VDR had exit codes? I mean, how could I find what is the cause of VDR exit? For example, I want to know is the VDR exit for storage failure, driver failure, timers.conf failure or any thing else. It is because I wrote a script for restarting my system when vdr exits, but I want to prevent this for errors that are persistent, like hard disk failure, or timers.conf file failure. Thanks. J. Anderson. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev client & server contention
"Simon Baxter" <[EMAIL PROTECTED]> writes: > I've been trying all the available modes in the streamdev-server to > find the one that suits my needs best. > > I have 2 VDRs, a server and a client. Ideally, I'd like them both to > be able to change channel - and when the transponders need to change, > one will just force the other to change as well. This is sort of > possible with the"Client may suspend" set to "offer", but has some > problems. Do you really need two vdr running ? Would vdr-xineliboutput help ? You could have several frontends watching the same channel. (and every frontent can change the channel) -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
