On Mon, Oct 19, 2015 at 2:10 PM, Vittorio Giovara
<[email protected]> wrote:
> On Wed, Oct 14, 2015 at 11:33 AM, Vittorio Giovara
> <[email protected]> wrote:
>> This structure served as a bridge between data pointers and frames, but
>> it suffers from several limitations:
>> - it is not refcounted and data must be copied to every time
>> - it cannot be expanded without ABI break due to being used on the stack
>> - its functions are just wrappers to imgutils which add a layer of
>>   unneeded indirection, and maintenance burden
>> - it allows hacks like embedding uncompressed data in packets
>> - its use is often confusing to our users
>>
>> AVFrame provides a much better API, and, if a full blown frame is not
>> needed, it is just as simple and more straightfoward to use data and
>> linesize arrays directly.
>>
>> Signed-off-by: Vittorio Giovara <[email protected]>
>> ---
>>  libavcodec/avcodec.h    | 50 
>> +++++++++++++++++++++----------------------------
>>  libavcodec/avpicture.c  |  3 ++-
>>  libavcodec/imgconvert.c |  2 ++
>>  3 files changed, 25 insertions(+), 30 deletions(-)
>
> If no more comments I'd push the set this week.
> Cheers
> --
> Vittorio

Set is pushed, I'd like to thanks Luca and wm4 for their help and
reviews about it.
-- 
Vittorio
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to