1 |
On 09/23/2011 12:54 AM, Mick wrote: |
2 |
> On Thursday 22 Sep 2011 09:15:42 Nikos Chantziaras wrote: |
3 |
>> On 09/22/2011 12:58 AM, Mick wrote: |
4 |
>>> On Wednesday 21 Sep 2011 09:19:39 Sebastian Beßler wrote: |
5 |
>>>>> Does mplayer2 work with smplayer or kmplayer? |
6 |
>>>> |
7 |
>>>> I use mplayer2 with smplayer for a few month now and everything works |
8 |
>>>> just fine for me. |
9 |
>>> |
10 |
>>> Any idea when ffmpeg-mt might make it to the main portage tree? |
11 |
>> |
12 |
>> It's already in the tree. Both ffmpeg as well as libav now have it. |
13 |
> |
14 |
> Sorry I can't see a USE flag or ffmpeg-mt package in portage: |
15 |
> |
16 |
> $ eix -l ffmpeg | grep mt |
17 |
> $ |
18 |
> |
19 |
> or are you saying that the code has been merged in the vanilla ffmpeg and |
20 |
> libav without the need for a USE flag? |
21 |
|
22 |
ffmpeg-mt is not a "package". It's the name of the git branch the code |
23 |
was in. That code was merged into the fmmpeg and libav projects. That |
24 |
means that ffmpeg and libav now do multi-threading. |
25 |
|
26 |
Furthermore, the "threads" USE flag does *not* control this. You get |
27 |
multi-threading regardless of that flag. "threads" only controls |
28 |
another type of multi-threading that was there since a long time now, |
29 |
but doesn't perform well. It would split decoding of each frame into |
30 |
multiple threads, and the CPU cores would not start decoding again until |
31 |
the whole frame was finished. The speed-up you get by this is minimal. |
32 |
"Real" multithreading, meaning the code from the ffmpeg-mt branch |
33 |
which allows every CPU core to fully decode its own video frame, cannot |
34 |
be controlled by a USE flag. |
35 |
|
36 |
To verify if multi-threading works for you, simply play an h264 video |
37 |
file in mplayer2 (using "-lavdopts threads=N", where N is the number of |
38 |
CPU cores in your system) and use something like "top" or "htop" to |
39 |
check CPU load of each core. |