Re: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Hi. after being away 7 month from VDR development Have a nice new year and welcome back! :) I'm pleased to announce release 0.9.0. I guess it's = 1.7.3 only because I gave it a quick whirl with vdr 1.7.2 and all I got were lot's of errors like: Jan 13 09:48:25 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:26 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:27 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:28 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:29 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:30 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:31 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:32 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:32 vdr: [15269] ERROR: driver buffer overflow on device As vdr 1.7.3 is not yet ready for general consumption :) I guess I'll have to stay with vdr 1.7.1 and xineliboutput for the time being even though I really would like to get HD up and running once and for all. Actually it is a pity that no software output device solution gets added to vdr itself because that would usually mean it just works, no matter what vdr version one tries... :-( Thanks for your great work, btw! Best regards, matthias. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
Klaus Schmidinger wrote: [...] Ok, then let's have another id for this... What about an id which can be set in the config-file? Should be the easiest thing to implement. Olli ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
Hi, with vdr 1.7.3 I had no directory display in the pictures-plugin and crashes in dvdswitch, while it initially scanned the defined base directory for DVD-Images. I found, that with the LARGEFILE options I had to change cReadDir accordingly to use dirent64 and readdir64_r (tools.h, tools.c) Those Plugins, using cReadDir like pictures, epgsearch, dvdswitch then also had to change dirent to dirent64. With these changes the plugins are working again (Base system is Debian etch). Regards Johann ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput - front ends not detected?
Hi I'm trying to install xineliboutput on a EPIA SP13000, but am getting the following error: [r...@freddy xineliboutput-1.0.3]# make install Makefile:68: Makefile:69: xine-lib not detected ! frontends will not be compiled. Makefile:70: Makefile:170: libextractor not found. make: Nothing to be done for `install'. [r...@freddy xineliboutput-1.0.3]# rpm -qa | grep xine xine-0.99.5-5.fc10.i386 xine-lib-1.1.15-3.fc10.i386 xine-lib-pulseaudio-1.1.15-3.fc10.i386 totem-xine-2.24.3-1.fc10.i386 What am I missing? Thanks Simon ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput - front ends not detected?
Simon Baxter schrieb: Hi I'm trying to install xineliboutput on a EPIA SP13000, but am getting the following error: [r...@freddy xineliboutput-1.0.3]# make install Makefile:68: Makefile:69: xine-lib not detected ! frontends will not be compiled. Makefile:70: Makefile:170: libextractor not found. make: Nothing to be done for `install'. [r...@freddy xineliboutput-1.0.3]# rpm -qa | grep xine xine-0.99.5-5.fc10.i386 xine-lib-1.1.15-3.fc10.i386 xine-lib-pulseaudio-1.1.15-3.fc10.i386 totem-xine-2.24.3-1.fc10.i386 What am I missing? libextractor?!?!?! And probably the xine development libraries too... Regards, Helge. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput - front ends not detected?
On Tue, Jan 13, 2009 at 10:08 PM, Simon Baxter linu...@nzbaxters.com wrote: Hi I'm trying to install xineliboutput on a EPIA SP13000, but am getting the following error: [r...@freddy xineliboutput-1.0.3]# make install Makefile:68: Makefile:69: xine-lib not detected ! frontends will not be compiled. Makefile:70: Makefile:170: libextractor not found. make: Nothing to be done for `install'. [r...@freddy xineliboutput-1.0.3]# rpm -qa | grep xine xine-0.99.5-5.fc10.i386 xine-lib-1.1.15-3.fc10.i386 xine-lib-pulseaudio-1.1.15-3.fc10.i386 totem-xine-2.24.3-1.fc10.i386 What am I missing? Thanks Simon ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr You missed devel package of xine-lib. In debian it is libxine-dev, in fedora it may be something like xine-lib-devel ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Reinhard Nissl schrieb: Hi, Well, vdr-xine-0.9.0 should be compatible till VDR-1.2.x. Hi, I tried with vdr-1.6.0.2 and got messages trying to connect or so, but never a connect. I used the added xine-lib (+ patch) and -ui under Suse 11.1. vdr-xine-0.8.2 works well. As I have no X I use fbxine. Joerg ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] why the VDR-PC can't auto run runvdr?
My VDR system run on xorg without KDE. cp init.d.runvdr.Debian /etc/init.d/runvdr chmod a+x /etc/init.d/runvdr cp runvdr /usr/bin/runvdr chmod a+x /usr/bin/runvdr cp runvdr.conf.example /etc/runvdr.conf ln -s /etc/init.d/runvdr /etc/rc2.d/S99runvdr runvdr.conf:--# Fire up own X server as output deviceXSERVER=/usr/bin/X -nolisten tcp -config /etc/X11/xorg-runvdr.conf :0-- when I start the VDR-PC,The Screen displays: /usr/bin/runvdr:line 576: 4515 Segmentation fault waiting for X server to shut downPID=4515RET=139VDR died within 10 seconds, this happened 6 time(s).Terminating because VDR died 6 times in a row quickly at wed Jan 14 06:51:28 CST 2009Sending 1 processes the TERM signal.terminated. /usr/bin/runvdr:line 576: 4515 Segmentation fault-# Act as a proxy for calling VDR, from within X sessionif [ -n $XSERVERPROXY ] ; theneval $VDRCMD PID=$!echo PID $PID $XSERVERPROXY wait $PID #line 576: 4515 Segmentation fault echo RET $? $XSERVERPROXYexit 0fi - But after I logined the vdr-pc.r...@vdr:/etc/inti.d/runvdr startthe VDR-PC run X at first, next run vdr is OK. why the VDR-PC can't auto run runvdr，but after I logined the VDR-PC,press the command:/etc/inti.d/runvdr start，the vdr running is OK? _ 微软地图率先推出跨城市多点驾车路线查询！ http://ditu.live.com/?form=MRAHABrtp=pos.30.454167_116.308611_%E5%A4%AA%E6%B9%96__~pos.29.554046_115.983427_%E5%BA%90%E5%B1%B1__~pos.29.116111_110.478889_%E5%BC%A0%E5%AE%B6%E7%95%8C__rtop=0~0~0encType=1___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] why the VDR-PC can't auto run runvdr?
On 14 Jan 2009, at 11:48, LinHai wrote: why the VDR-PC can't auto run runvdr，but after I logined the VDR- PC,press the command:/etc/inti.d/runvdr start，the vdr running is OK? Probably some environment variables are not set. Try putting this line in your script and compare the output with when running as a real user; set /tmp/env You probably just need to have environment settings for USER, HOME and PATH set properly. -- Torgeir Veimo torg...@pobox.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
