Re: [Mlt-devel] libavcodec version 54.1

[Dan D. <da...@de...>]

On Sun, Feb 12, 2012 at 8:34 PM, Brian Matherly <pez...@ya...> wrote:
>>>  2) MLT does not detect libx264 because it uses the new "encode2"
>> field in
>>>  AVCodec
>>
>> but this is a problem
> <snip>
>>
>>>  Let me know if you want any help getting the avformat module updated.
>> I'll
>>>  probably start hacking on it anyway since I would like to see libx264
>>>  working again.
>>
>> go for it
>
> Here is a quick (and proper) fix to get libx264 working again:
> https://github.com/pez4brian/mlt/commit/405d42d200ad93ea2be347ce3615b968522635cd

well, that was easy :) Did you test this with libav.org as well?

> I looked at the other API changes. We might want to discuss this. It appears they are switching from the application managing its own buffers, to the application using AVFrame and having libav manage the buffers therein. The code might get ugly. You should probably have a look at the API changes before we commit. Again, I'm happy to help. But I don't want to invest a lot of time into a bunch of precompiler conditionals - only to find out I went the wrong direction.
>

Nah, they can't impose that. Memory is always a copy away. We already
do that in some places and use AVFrame.

-- 
+-DRD-+