[MPlayer-users] can't use dual core

[Henry Garcia]

On 4/19/07, Vladimir Mosgalin <mosgalin at vm10124.spb.edu> wrote:
>
> Hi Henry Garcia!
>
> On 2007.04.19 at 13:16:29 -0400, Henry Garcia wrote next:
>
> > -lavdopts threads=2
> >
> > That works for decoding with lavc on linux. Helps a little, not much.
>
> Are you sure it ever helps at all? It doesn't seem that to me, at least
> when decoding h264 and mpeg4. Haven't tested wmv3 and mpeg2, but I doubt
> anything will change.


Maybe it's my imagination. I feel better though. Actually, using  the  table
of processess  (top) from a console, I made a few comparisons, and it seems
to cut down the processor usage about 5 - 6 % that's decoding an ffmpeg4
file. But it shows up more on my system because I'm using 'slower' PIII 800
Mhz processors.

> Decoding for X264 you have to compile the x264 source code yourself  and
>
> Huh? mplayer can't decode using x264! Maybe x264 supports decoding, but
> mplayer can use only ffh264 and some windows codecs to decode h264
> streams.


Sorry,  h264. The svn code I
download<http://www.videolan.org/developers/x264.html>comes back in an
x264 folder, so it catches me off guard. And that should be
encoding, not decoding. My bad. You're right. I don't believe mplayer is set
up to use more than 1 thread on decoding h264 files. I see a marginal
increase in efficiency on 'decoding' mpeg4 files using the -lavdopts
threads= . But someone had posted previously that that doesn't work on h264
encoded files.

> x264. And then you should read the manual on how to use the threads when
> > encoding. Decoding using the threads is very efficient using threads.
>
> When encoding or when decoding?? Decoding using multiple threads /may/
> be efficient, but it doesn't happen automatically, it should be
> programmed (which can be hard to impossible). With ffmpeg, apparently it
> isn't. And decoding using x264 is impossible too, at least with
> mplayer..


encoding. As I said above. Encoding I see about 95 % use of both CPUS on a
dual SMP Pentium III system, compared to only 95 % on 1 cpu when using the
threads option. Still takes about 8 - 9 hours to encode a DVD. There is a
threads=auto or autodetect that I used last time. It works pretty good. But
from what I've read, some guys recommend--in general--have twice as many
threads as CPUS (e.g. 4 threads for 2 CPUS) on the motherboard.

--
>
> Vladimir
> _______________________________________________
> MPlayer-users mailing list
> MPlayer-users at mplayerhq.hu
> http://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
>