[FFmpeg-user] New options -preset and -tune for x264 encoding

[Baptiste Coudurier]

On 04/19/2011 03:09 PM, Baptiste Coudurier wrote:
> Hi Sean,
> 
> On 04/19/2011 03:05 PM, sean darcy wrote:
>> On 04/19/2011 03:27 PM, Baptiste Coudurier wrote:
>>> Hi,
>>>
>>> On 04/19/2011 08:56 AM, sean darcy wrote:
>>>> On 04/16/2011 08:10 PM, Baptiste Coudurier wrote:
>>>>> Hi everyone,
>>>>>
>>>>> Latest git has now added 2 new options for libx264 encoding:
>>>>> -preset<preset>
>>>>> -tune<tune>
>>>>>
>>>>> These options are directly mapped to internal tune and presets within
>>>>> libx264. The old presets files have been removed, please use the new
>>>>> options.
>>>>>
>>>>> Best regards.
>>>>>
>>>> How do these new presets work with 2 passes?
>>>>
>>>> For instance, I have a script that used:
>>>>
>>>> -pass 1 -vpre slow_firstpass
>>>>
>>>> -pass 2 -vpre slow
>>>>
>>>> I've changed it to:
>>>>
>>>> -pass 1 -preset slow
>>>>
>>>> -pass 2 -preset slow
>>>>
>>>> I used to get 100 fps on the 1st pass, now about 70. Is this to be
>>>> expected? Or do I need to do something else on the 1st pass?
>>>>
>>>> Here's the full script:
>>>>
>>>> ffmpeg -i $INPUT -an -pass 1  -vcodec libx264 -level 30 -preset
>>>> slow     \
>>>>         -bufsize 10000000 -maxrate 10000000 -b 1200k -threads 0 -f
>>>> mp4 -y
>>>> /dev/null
>>>> ffmpeg -i $INPUT -an -pass 2  -vcodec libx264 -level 30 -preset slow
>>>> -timestamp now \
>>>>         -bufsize 10000000 -maxrate 10000000 -b 1200k -threads 0 $1.m4v
>>>
>>> fastfirstpass should be enabled by default.
>>> Can you please double check that the parameters printed are the same ?
>>>

Fixed fastfirstpass in git, please update.
It seems testing was bumpy here .... sorry about that.


-- 
Baptiste COUDURIER
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
FFmpeg maintainer                                  http://www.ffmpeg.org