Le 2014-09-16 20:43, Anton Khirnov a écrit :
On Thu, 11 Sep 2014 18:08:18 +0300,
=?UTF-8?q?R=C3=A9mi=20Denis-Courmont?= <[email protected]> wrote:
This function provides an explicit VDPAU device and VDPAU driver to
libavcodec, so that the application is relieved from codec specifics
and VdpDevice life cycle management.
A stub flags parameter is added for future extension. For instance,
it
could be used to ignore codec level capabilities (if someone feels
dangerous).
---
doc/APIchanges | 4 ++++
libavcodec/vdpau.c | 21 ++++++++++++++++++++-
libavcodec/vdpau.h | 21 +++++++++++++++++++++
libavcodec/version.h | 2 +-
4 files changed, 46 insertions(+), 2 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index f17f1cf..3df116e 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -13,6 +13,10 @@ libavutil: 2014-08-09
API changes, most recent first:
+2014-09-xx - xxxxxxx - lavc 56.2.0 - vdpau.h
+ Add av_vdpau_bind_context(). This function should now be used for
creating
+ (or resetting) a AVVDPAUContext instead of
av_vdpau_alloc_context().
+
Do we really need a new function here?
The reset member is not visible to the application, and I would much
rather it stays that way.
Adding a new function also ensures proper symbol-based dynamic library
versioning. Changing the size of a structure does not.
Cannot you accomplish the same thing (but more extensible) simply by
having the caller set the corresponding AVVDPAUContext fields?
Not really.
--
Rémi Denis-Courmont
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
