diff options
author | Reimar Döffinger <Reimar.Doeffinger@gmx.de> | 2013-08-07 23:22:48 +0400 |
---|---|---|
committer | Reimar Döffinger <Reimar.Doeffinger@gmx.de> | 2013-08-11 22:16:57 +0400 |
commit | d404fe35b2fb918e38e58c2256a77b8113229951 (patch) | |
tree | c3e2acd88f9bf557a6936b1addbd6552de181af2 /doc/APIchanges | |
parent | af05edc658f3af284a1af39c00a36aeff0adaa0d (diff) |
Make new VDPAU easier to use by adding context to callback.
Using VDPAU correctly means checking for preemption
and possibly regenerating the context all the time.
With the current API there is no context or other
user-defined pointer and thus this in not possible
during decoding unless using some hack like global
variables.
The need to reinitialize both surfaces and even function
pointers makes handling preemption even more difficult.
This patch introduces a new render2 function that gets
both the AVCodecContext and AVFrame in addition,
in both the user can store additional opaque data.
This allows even advanced approaches like keeping a
"generation counter" for the surfaces so they can be
regenerated on the fly and efficiently.
In addition, the function has a return value that will
be passed through all the way instead of being silently
ignored as for the current render function.
Unfortunately the HWAccel API has no way of providing
API/ABI compatibility, so a currently disallowed
state (render pointer being NULL) is used to extend it.
Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
Diffstat (limited to 'doc/APIchanges')
-rw-r--r-- | doc/APIchanges | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/APIchanges b/doc/APIchanges index 147b3c722f..049d142760 100644 --- a/doc/APIchanges +++ b/doc/APIchanges @@ -15,6 +15,9 @@ libavutil: 2012-10-22 API changes, most recent first: +2013-08-xx - xxxxxxx - lavc 55.27.100 - vdpau.h + Add a render2 alternative to the render callback function. + 2013-08-xx - xxxxxxx - lavc 55.26.100 - vdpau.h Add allocation function for AVVDPAUContext, allowing to extend it in the future without breaking ABI/API. |