thank you Moritz !
anyway, even with -threads 0
x265 [info]: Thread pool created using 24 threadsx265 [info]: Slices
: 1x265 [info]: frame threads / pool features : 5 /
wpp(5 rows)
I see with top command between 400% - 500% CPU on ffmpeg ... I was expected
like 2400% or 24 ffmpeg workers with 100%
where am I wring again ??
as for my last email, I write it with yahoo email web interface, I guess it's
not fully compatible with the list managing software. Sorry
RegardsFred
Le Lundi 10 avril 2017 12h20, Moritz Barsnick <[email protected]> a écrit :
On Mon, Apr 10, 2017 at 09:58:59 +0000, fred fred wrote:
> I have tried all possible ways to use all my 16 cpus (x2 threads) to encode
> with libx265, but each time it fails...
> -pools, --pools, -p, --numa-* ... and so on are not recognise at all
Those are x265 options (of the command line tool), not ffmpeg+libx265
options.
First, please try ffmpeg's own "-threads 16" option. That should do the
right thing for you.
If you need to directly use those pool options of libx265, use a special
ffmpeg option:
"-x265-params pools=8" (or something similar)
Also observe the info ffmpeg's libx265 encoder outputs when beginning
to encode, e.g.:
> x265 [info]: Thread pool created using 4 threads
> x265 [info]: frame threads / pool features : 2 / wpp(4 rows)
BTW, your email's formatting is terribly broken:
http://ffmpeg.org/pipermail/ffmpeg-user/2017-April/035824.html
Cheers,
Moritz
_______________________________________________
ffmpeg-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
