[FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

Hendrik Leppkes h.leppkes at gmail.com
Wed May 10 21:52:57 EEST 2017


On Wed, May 10, 2017 at 8:14 PM, Paul B Mahol <onemda at gmail.com> wrote:
> On 5/10/17, Saverio Blasi <Saverio.Blasi at bbc.co.uk> wrote:
>> Dear Michael,
>>
>>  >> Why do you pass a single string of all options and then manually parse
>> all options out of it instead of specifying the options each in teh AVOption
>> array ?
>>
>> We prefer to pass a single string so that we can be more flexible how we
>> then parse it and what to do with it. This gives us more freedom in the
>> future in case we decide to change some of the codec APIs, so that we do not
>> need to change the interface with FFmpeg.
>
> That is unacceptable.

libx264 and 265 pass options the same way, what exactly is the problem
with that?

- Hendrik


More information about the ffmpeg-devel mailing list