Hi Remy,
...About long process, older ffmpeg was single thread only while the latest one I suggested to give it try is multi-thread and under my system which has 4 enabled CPU core ( I also tried it using the 4 additional virtual core ), it works well and conversion is mutch faster with the latest ffmpeg suggested build...
Let me explain better, the long time it takes to re-encode my videos is due to several reasons:
1) MJPGs produced by my DSLR (Pentax K5) are big...we are talking on the order of 1.5-2gig for just a couple of minutes
2) since I can not use your app with multiple CPU cores enabled, I shut off all but one, then encoding happens in a "single thread" fashion since all other CPU cores are effectively disabled
3) I have previously used ffmpeg-os2-r26099, which is multi-thread enabled (it was a Dave Yeo drop)...so if I do the conversion outside of your app (command line) I am able to crunch through the data much faster as the work is done in parallel
I did download and install your recommended ffmpeg-os2-r2_1_5-Fourier version...haven't gotten a chance to try it out yet though.
Here is an idea I've been investigating to get around my app freeze situation. I could configure the application start cmd file to shut off all cores and run in a single-core mode. When the time comes to actually start the encoding operation if there was a way for your process to tie-in to a user defined "prep cmd step" I could then re-enable all the cores and really let the machine fly through the process. Since your app builds the final ffmpeg command on-the-fly I'm wondering if there is a way for me to do this?
So here is an example of what I'm talking about:
=== START ===
/* auto generated program by FFMPEGCA to execute ffmpeg in start using pipe */
Parse arg copy_metadata
ff_inputfile="I:\Movies\Family\Amelia - Baby Boots 2.MPG"
ff_inputfile='"'||ff_inputfile ||'"'
ff_outfile="G:\HOME\.ffmpegca\Amelia - Baby Boots 2.mp4"
Out_AVmap=" -map 0.1 -map 0.0"
more_map=""
ff_outfile='"'||ff_outfile||'"'
ffmpeg_prms=' -i '||ff_inputfile||' '||Out_AVmap||' -vcodec libx264 -b 1400k -r 29.97 -qmin 2 -qmax 35 -async 3'
/* --- x264 preset used : external --- */
ffmpeg_prms=ffmpeg_prms||' -vpre hq'
ffmpeg_prms=ffmpeg_prms||' -ar 44100 -acodec ac3 -ab 192k -vol 256 -ac 2'
ffmpeg_prms=ffmpeg_prms||' '||copy_metadata||' '||ff_outfile||' '||more_map
==> BEFORE ffmpeg.exe kicks off below I'd re-enable the CPU cores'G:\util\misc\priority.exe 1 3 G:\APPS\MULTIMEDIA\ffmpeg\bin\ffmpeg.exe -y '||ffmpeg_prms||' 2>\pipe\ffmpegca_122'
==> AFTER ffmpeg.exe finishes above I'd disable the CPU cores=== END ===
...any chance for this?