On 14/10/15 11:33, Vittorio Giovara 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(-)
Ok, I'll add few helpers to avframe later. lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
