---

Hej NG
Hvorfor er det lige, at Divx hakker sådan i XMMS, det er lidt
trættende, da jeg kørte Win98 var der ikke nogen problemer, men når jeg
afspiller i XMMS, hakker det sådan, som at det svarer til et slags
slideshow, hvilket er mindre fedt

Min maskine er en PII - 400MHz med 128 Ram og GNOME 1.4, skal jeg have
mere RAM i maskinen, for at det kører flydende..? avi-xmms og avifile
er selvfølgelig installeret

Venlig hilsen
René

---

> Hvorfor er det lige, at Divx hakker sådan i XMMS, det er lidt
> trættende, da jeg kørte Win98 var der ikke nogen problemer, men når jeg
> afspiller i XMMS, hakker det sådan, som at det svarer til et slags
> slideshow, hvilket er mindre fedt
>
> Min maskine er en PII - 400MHz med 128 Ram og GNOME 1.4, skal jeg have
> mere RAM i maskinen, for at det kører flydende..? avi-xmms og avifile
> er selvfølgelig installeret

Jeg erindrer at have hørt om manglende MMX understøttelse i DivX under
linux, så systemravende skulle være noget højere.

Mvh Lasse

---

Det hjælper ofte at compile den form for applikationer selv, da de
ofte laver nogle små tricks til netop at udnytte din HW konfiguration

/Lars
"Rene Nielsen" <total@filrt.dk> wrote in message
news:9e61ib$90c$1@sunsite.dk...
> Hej NG
> Hvorfor er det lige, at Divx hakker sådan i XMMS, det er lidt
> trættende, da jeg kørte Win98 var der ikke nogen problemer, men når jeg
> afspiller i XMMS, hakker det sådan, som at det svarer til et slags
> slideshow, hvilket er mindre fedt
>
> Min maskine er en PII - 400MHz med 128 Ram og GNOME 1.4, skal jeg have
> mere RAM i maskinen, for at det kører flydende..? avi-xmms og avifile
> er selvfølgelig installeret
>
> Venlig hilsen
> René

---

Rene Nielsen wrote:

> Min maskine er en PII - 400MHz med 128 Ram og GNOME 1.4, skal jeg have
> mere RAM i maskinen, for at det kører flydende..? avi-xmms og avifile
> er selvfølgelig installeret

Hvordan i alverden har du fået avifile til at virke? Jeg kan ikke finde
ud
af at kompilere det.

-> Michael Knudsen

---

Michael Knudsen wrote:


> Hvordan i alverden har du fået avifile til at virke? Jeg kan ikke finde
> ud
> af at kompilere det.

Måske et klogt hoved kunne sige mig, hvad jeg skal stille op med dette:

[root@localhost avifile-0.53.5]# ./configure
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for c++... c++
checking whether the C++ compiler (c++ ) works... yes
checking whether the C++ compiler (c++ ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries...
yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for objdir... .libs
creating libtool
checking for dlopen in -ldl... yes
checking for pthreads... -lpthread yes
checking for ANSI C header files... yes
checking for fcntl.h... yes
checking for limits.h... yes
checking for malloc.h... yes
checking for sys/ioctl.h... yes
checking for sys/time.h... yes
checking for unistd.h... yes
checking for working const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for 8-bit clean memcmp... yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking return type of signal handlers... void
checking for vprintf... yes
checking for ftime... yes
checking for gettimeofday... yes
checking for strdup... yes
checking for strstr... yes
checking for X... configure: error: Can't find X includes. Please check
your installation and add the correct paths!

På forhånd 10^{noget stort} tak!

-> Michael Knudsen

---

Den Sun, 20 May 2001 23:09:05 +0200 skrev Michael Knudsen:
>Michael Knudsen wrote:
>
>
>> Hvordan i alverden har du fået avifile til at virke? Jeg kan ikke finde
>> ud
>> af at kompilere det.
>
>Måske et klogt hoved kunne sige mig, hvad jeg skal stille op med dette:
>
>checking for strstr... yes
>checking for X... configure: error: Can't find X includes. Please check
>your installation and add the correct paths!

Prøv at installere X includes...

(På SuSE ligger de i xdevel3.rpm)

Mvh
Kent
--
http://www.celebrityshine.com/~kfr/ - nu med Elgo-billeder

---

Kent Friis wrote:

> Prøv at installere X includes...
>
> (På SuSE ligger de i xdevel3.rpm)

Så langt så godt.....nu sker følgende:

[root@localhost avifile-0.53.5]# ./configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for c++... (cached) c++
checking whether the C++ compiler (c++ ) works... yes
checking whether the C++ compiler (c++ ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking for ranlib... (cached) ranlib
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries...
yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for objdir... .libs
creating libtool
checking for dlopen in -ldl... (cached) yes
checking for pthreads... -lpthread yes
checking for ANSI C header files... (cached) yes
checking for fcntl.h... (cached) yes
checking for limits.h... (cached) yes
checking for malloc.h... (cached) yes
checking for sys/ioctl.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for working const... (cached) yes
checking for inline... (cached) inline
checking whether time.h and sys/time.h may both be included... (cached)
yes
checking whether gcc needs -traditional... (cached) no
checking for 8-bit clean memcmp... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... (cached) yes
checking for working mmap... (cached) yes
checking return type of signal handlers... (cached) void
checking for vprintf... (cached) yes
checking for ftime... (cached) yes
checking for gettimeofday... (cached) yes
checking for strdup... (cached) yes
checking for strstr... (cached) yes
checking for X... (cached) libraries /usr/X11R6/lib, headers
/usr/X11R6/include
checking for Qt... (cached) libraries /usr/lib/qt2/lib, headers
/usr/lib/qt2/include
checking for moc... (cached) /usr/lib/qt2/bin/moc
checking for uic... (cached) /usr/bin/uic
checking whether we like this Qt installation... checking for
/usr/lib/qt2/include/qvariant.h... (cached) yes
checking whether to build QtVidcap... checking for
/usr/lib/qt2/include/qtable.h... (cached) yes
checking for XF86DGAQueryExtension in -lXxf86dga... (cached) yes
checking for XF86VidModeSwitchMode in -lXxf86vm... (cached) yes
checking for sdl-config... (cached) no
checking for SDL - version >= 1.1.3... no
*** The sdl-config script installed by SDL could not be found
*** If SDL was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the SDL_CONFIG environment variable to the
*** full path to sdl-config.
checking whether to build ac3 decoder module... no
creating ./config.status
creating ./Makefile
creating lib/Makefile
creating lib/loader/Makefile
creating lib/videocodec/Makefile
creating lib/audiodecoder/Makefile
creating lib/videocodec/Makefile
creating lib/avifile/Makefile
creating lib/aviplay/Makefile
creating player/Makefile
creating lib/audioencoder/Makefile
creating lib/audioencoder/lame3.70/Makefile
creating lib/audiodecoder/mpeg/Makefile
creating samples/Makefile
creating samples/avitest/Makefile
creating samples/benchmark/Makefile
creating samples/extractor/Makefile
creating samples/qtvidcap/Makefile
creating include/Makefile
creating include/wine/Makefile
creating bin/Makefile
creating samples/qtrecompress/Makefile
creating avifile-config
creating avifile.spec
creating lib/videocodec/DirectShow/Makefile
creating include/config.h
include/config.h is unchanged

---

Michael Knudsen <knudsen@imf.au.dk> writes:

> checking for sdl-config... (cached) no
> checking for SDL - version >= 1.1.3... no
> *** The sdl-config script installed by SDL could not be found
> *** If SDL was installed in PREFIX, make sure PREFIX/bin is in
> *** your path, or set the SDL_CONFIG environment variable to the
> *** full path to sdl-config.

Installerer SDL?

-- Ole M

---

---

"Rasmus B. Hansen" wrote:


> > checking for SDL - version >= 1.1.3... no
> > *** The sdl-config script installed by SDL could not be found
> > *** If SDL was installed in PREFIX, make sure PREFIX/bin is in
> > *** your path, or set the SDL_CONFIG environment variable to the
> > *** full path to sdl-config.
>
> Du skal vel bare have installeret SDL og SDL-devel (eller hvad pakkerne nu
> hedder på din distro).

Nu har jeg installeret alle pakker, som hedder noget med SDL....jeg får
stadig
den samme meddelelse. Det virker, som om ./configure ikke kan finde SDL.
Hvordan
mon man kan råde bod på det?

-> Michael Knudsen

---

On Mon, 21 May 2001 10:08:57 +0200,
Michael Knudsen <knudsen@imf.au.dk> wrote:

>"Rasmus B. Hansen" wrote:
>
>
>> > checking for SDL - version >= 1.1.3... no
>> > *** The sdl-config script installed by SDL could not be found
>> > *** If SDL was installed in PREFIX, make sure PREFIX/bin is in
>> > *** your path, or set the SDL_CONFIG environment variable to the
>> > *** full path to sdl-config.
>>
>> Du skal vel bare have installeret SDL og SDL-devel (eller hvad pakkerne nu
>> hedder på din distro).
>
>Nu har jeg installeret alle pakker, som hedder noget med SDL....jeg får
>stadig
>den samme meddelelse. Det virker, som om ./configure ikke kan finde SDL.
>Hvordan
>mon man kan råde bod på det?

SVJH (og dette er jeg altså slet ikke sikker på) er der en cache-fil der
skal slettes, hvorefter man kan køre configure igen. Prøv evt at slette
directoriet og prøv igen.

--
Anders Bo Rasmussen mailto:fuzz01@spamfilter.dk
Frimestervej 42 1.tv http://www.fuzz.dk
2400 Kbh. NV
Denmark

---

---

On Sat, 19 May 2001 16:56:28 +0200, Rene Nielsen <total@filrt.dk> wrote:

> Hvorfor er det lige, at Divx hakker sådan i XMMS, det er lidt
> trættende, da jeg kørte Win98 var der ikke nogen problemer, men når jeg
> afspiller i XMMS, hakker det sådan, som at det svarer til et slags
> slideshow, hvilket er mindre fedt

Det boostede min Divx-afspilning helt vildt at kompilere MTRR-support i kernen.

CONFIG_MTRR=y


--
Aagren

please sign http://www.libranet.com/petition.html

---

Lasse Aagren wrote:

> Det boostede min Divx-afspilning helt vildt at kompilere MTRR-support i kernen.
>
> CONFIG_MTRR=y

Har du nogen ide om _hvorfor_???

--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
http://bigfoot.com/~thunderbear

---

On Mon, 21 May 2001 20:48:29 +0200, Thorbjørn Ravn Andersen
<thunderbear@bigfoot.com> wrote:
>> Det boostede min Divx-afspilning helt vildt at kompilere MTRR-support i
>> kernen. CONFIG_MTRR=y
>
> Har du nogen ide om _hvorfor_???

Jep: Fra hjælpen til kerneopsætning til CONFIG_MTRR:

<SNIP>
On Intel P6 family processors (Pentium Pro, Pentium II and later) the Memory
Type Range Registers (MTRRs) may be used to control processor access to
memory ranges. This is most useful if you have a video (VGA) card on a PCI
or AGP bus. Enabling write-combining allows bus write transfers to be
combined into a larger transfer before bursting over the PCI/AGP bus. This
can increase performance of image write operations 2.5 times or more. Saying
Y here creates a /proc/mtrr file which may be used to manipulate your
processor's MTRRs. Typically the X server should use this.
</SNIP>




--
Aagren

please sign http://www.libranet.com/petition.html

---