ffmpeg win64

[Sirber]

Using the latest build from here (http://ffmpeg.zeranoe.com/builds/), using 4 or 0 threads, ffmpeg uses only 38% CPU on first pass, while the x86 version uses ~95%. Both 32-bit and 64-bit builds come with pthread support. Is there some issues with 64bit?

Both ffmpeg are launched and monitored from a 32bit app.

CPU: Intel i3 540

[edit]

First pass uses ~33% CPU.
Second pass uses 80%+ CPU.

[LoRd_MuldeR]

Sure the 64-Bit binary has multi-threaded decoders (aka "FFmpeg-MT") enabled?

If not, this could be the bottleneck with very "fast" x264 settings, as used in the first pass of a 2-Pass encode, even if libx264 itself has multi-threading enabled.

AFAIK FFmpeg-MT has been merged recently and thus should be enabled in all builds now. But one never knows ;)

[Sirber]

the author's site doesn't say.

ffmpeg version git-N-30558-ge844abc, Copyright (c) 2000-2011 the FFmpeg develope
rs
built on Jun 5 2011 08:25:07 with gcc 4.5.3
configuration: --disable-static --enable-shared --enable-gpl --enable-version3
--enable-memalign-hack --enable-runtime-cpudetect --enable-avisynth --enable-bz
lib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enab
le-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable
-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-
libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --e
nable-zlib --disable-outdev=sdl --pkg-config=pkg-config
libavutil 51. 4. 0 / 51. 4. 0
libavcodec 53. 6. 1 / 53. 6. 1
libavformat 53. 2. 0 / 53. 2. 0
libavdevice 53. 1. 1 / 53. 1. 1
libavfilter 2. 12. 0 / 2. 12. 0
libswscale 0. 14. 1 / 0. 14. 1
libpostproc 51. 2. 0 / 51. 2. 0

[Zeranoe]

The builds come with pthread support.

ffmpeg-mt was merged with FFmpeg some time ago.

use -threads 0 or -threads # to use the multicore pthread support.