On Sun, Feb 27, 2005 at 02:57:24PM +0100, Reinhard Nissl wrote:

Hi,

I'm pleased to announce maintenance release 0.7.2:

http://home.vr-web.de/~rnissl/vdr-xine-0.7.2.tgz

Great,

I have compiled it with last xine CVS and live view is really perfect !!!

I got the problem with playing recordings : with vdr-1.3.21 and vdr-1.3.22 is saccading (and vdr tooks about 40% of my amd64@3000 CPU which I think is rather very much, playing the vdr files with VDR take about 2% of the CPU).

If I use one of my two FF cards (with xawtv) the playing is perfectly smooth also.

Is there an option which can change anything for it ?

I am using kernel 2.6.11-rc5 and I got same result with pre-empt on or off, the HD is an SATA one.

I got the same behaviour with xine CVS or recommended version. I compil xine-lib with :

./autogen.sh --with-xvmc-lib=XvMCNVIDIA --with-xxmc-lib=XvMCNVIDIA \ --enable-static-xv && make && make install

My system is gentoo based (but vdr and xine are not ebuilds ones).

Thank for any hint one could provide me ;-)

Hi,

Grégoire Favre wrote:

I got the problem with playing recordings : with vdr-1.3.21 and vdr-1.3.22 is saccading (and vdr tooks about 40% of my amd64@3000 CPU which I think is rather very much, playing the vdr files with VDR take

^^^ xine?

about 2% of the CPU).

If I use one of my two FF cards (with xawtv) the playing is perfectly smooth also.

Is there an option which can change anything for it ?

I fear no.

I am using kernel 2.6.11-rc5 and I got same result with pre-empt on or off, the HD is an SATA one.

What about kernel 2.6.10? I wanted to wait for 2.6.11 but it looks like I should try 2.6.11-rc5 tomorrow ;-)

I got the same behaviour with xine CVS or recommended version. I compil xine-lib with :

./autogen.sh --with-xvmc-lib=XvMCNVIDIA --with-xxmc-lib=XvMCNVIDIA \ --enable-static-xv && make && make install

My system is gentoo based (but vdr and xine are not ebuilds ones).

I'm setting up a similar system on an EPIA board. Maybe I'll experience the same problem tomorrow evening?!

BTW: how did you configure your system? Do you have NPTL compiled in? I don't have it compiled in.

Bye.

-----Original Message----- From: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of Grégoire Favre

I also still compil my glibc without NPTL due to VDR (I have also removed UTF-8 for VDR) but I am not completely sure whether NPTL is still incompatible with VDR ?

Yep, it still has problems with NPTL. My default glibc (and everything else compiled on my system is compiled for NPTL, but I've a second version with LinuxThreads installed with a different prefix (configure --prefix=/usr/i686-glibc-linuxthreads when installing glibc.) Be careful not to overwrite your normal glibc with a different threading version or everything will break (including your shell!)

You also need a version of gcc copied into an alternate path (eg: cp -R /usr/lib/gcc/i686-pc-linux-gnu /usr/lib/gcc/i686-glibc-linuxthreads on my system) and the specs file in this directory altered to point to your NPTL version of ld-linux.so.2

I then compile and run VDR under a separate user which has its environment set to pass the following flags to gcc/g++:

-specs=/usr/lib/gcc/i686-glibc-linuxthreads/3.4.3/specs -nostdinc -I/usr/i686-glibc-linuxthreads/include -I/usr/lib/gcc/i686-glibc-linuxthreads/3.4.3/include -I/usr/include

And also: LD_LIBRARY_PATH=/usr/i686-glibc-linuxthreads/lib

That way anything compiled, linked and ran under that account uses LinuxThreads, everything else on my system uses NPTL.

Basically I followed http://commmunity.linux.com/howtos/Glibc2-HOWTO-4.shtml but made the change to the specs file and the LD_LIBRARY_PATH instead of altering any of the original libraries - i.e. skip step 4.2 and do the last bit of 4.3 a different way.

Chris