On Sun, 02 Dec 2012 12:28:10 +0100, Luca Barbato <[email protected]> wrote: > On 12/1/12 11:31 PM, Anton Khirnov wrote: > > > - cleaning up AVFrame: > > AVFrame currently contains a lot of crap I'd rather not have in lavu, > > mainly mpeg-specific tables. One other thing is owner, which is also > > lavc-specific. > > * one possible solution is to just remove the crap (which most > > probably has vanishingly small usefulness) and require frame > > threaded decoders to use a lavc specific frame struct which would > > contain AVFrame+owner. > > This is probably the simplest solution, but quite ugly IMO. > > Seems good to me. > > > * another one is to add some kind of side data/metadata to AVFrame. > > The question is how specifically should it look. I'm currently > > thinking about making it basically identical to the AVPacket side > > data. Better suggestions welcome. > > I'm not so sure it would be better than the former. >
Even though it's unprobable, there just might be some people who find those tables and motion vectors and whatever useful. And Kieran recently expressed an interest in exporting some h264-specific per-frame thing. Also I still need some place to store the per-frame threading data. Using a wrapper struct in all the frame threaded decoders is possible, but not exactly elegant. Side data would solve both of this, which is why i think it might be better. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
