[FFmpeg-user] libx264 options through FFmpeg

[Tim Nicholson]

On 30/06/11 11:08, Tim Nicholson wrote:
> On 28/06/11 17:51, Thomas Worth wrote:
>> On Tue, Jun 28, 2011 at 8:31 AM, Tim
>> Nicholson<tim.nicholson at bbc.co.uk> wrote:
>>> On 22/06/11 06:43, Thomas Worth wrote:
>>>>
>>>> While I've historically used a standalone x264 binary to do encoding
>>>> by piping yuv420p from FFmpeg, I thought I'd try libx264 through
>>>> FFmpeg since it's certainly more convenient.
>>>>
>>>> [....]
>>>>
>>>> If I can safely pass all my options via -x264opts then I'll just use
>>>> that from now on and disregard FFmpeg's x264 interface.
>>>
>>> But what about options that require colon delimited parameters
>>> themselves
>>> such as "--sar 1:1"?
>>
>> If I use a forward slash (sar=16/9), libx264 doesn't complain but it
>> also doesn't use the supplied ratio. It seems to default to "1/1"
>> every time.
>
> I have tried sar="1:1" and it hasn't complained about that.
>
> Howver it doesn't want to accept a profile specification. Using:-
>
> ffmpeg -i $in_file -vcodec libx264 -pix_fmt yuv420p -s 1920x1080 -an \
> -x264opts bitrate=35000:preset=veryslow:tune=$tune:\
> [...]
>
> I get a:-
> "[libx264 @ 0x12e0960] bad value for 'preset': 'veryslow'"
>
> error. replace "veryslow" with whatever you like from the legal list.
>

Actually its worse than that, it also doesn't accept any of the --tune 
parameters, or seem to handle options that don't have values, e.g --tff
-- 
Tim

http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.