On Mon, Jan 27, 2014 at 4:19 PM, Vittorio Giovara <[email protected]> wrote: > Hi all, > this set of patches tries to improve interlaced frames handling in libav. > > First of all it updates AVFrame to use one AVFieldState variable instead of > two different integers. Then it introduces two new "states", that is when > the interlacing mode is unknown and when you know that the frame interlaced > but not if it's top field first or bottom field first. This also addresses > peculiar decoders, like png and utvideo, whose concept of interlacing is > slightly different than the other. > > Finally it sliglty modifies the context information so that when > encoding/decoding, users can immediately see if a video contains interlaced > frames or not, and (optionally) override interlacing coding from the command > line. > > This is my first large deprecation patchset, so please be gentle ^^. > Vittorio >
Hi, I've gathered most of the comments received in this blueprint: https://wiki.libav.org/Blueprint/Interlacing I'm not sure if the convenience functions that preserve compatibility should be public or not, what do you think? Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
