On 12/5/12 8:33 PM, Anton Khirnov wrote:
On Tue, 04 Dec 2012 15:37:57 +0100, Luca Barbato <[email protected]> wrote:
On 12/04/2012 03:20 PM, Anton Khirnov wrote:
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.
How would you access the fields?
Well..that is the question ;)
What about having codec capabilities to negotiate what can be exported
or not and a pointer to access it?
It is quite similar to the side data.
Do you have already a list of exported fields and codecs exporting them?
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
