GNOME Bugzilla – Bug 736721
Add abstraction for exported VA buffers (GstVaapiBufferProxy)
Last modified: 2015-01-28 16:37:56 UTC
The VA buffer export APIs work for a particular lifetime starting from vaAcquireBufferHandle() and ending with vaReleaseBufferHandle(). As such, it could be much more convenient to support implicit releases by simply having a refcount reaching zero. Proposed APIs: - Name: GstVaapiBufferProxy - gst_vaapi_buffer_proxy_new(GstVaapiBufferProxyClass *klass, GstVaapiObject *parent): internal function - gst_vaapi_buffer_proxy_get_parent(GstVaapiBufferProxy *proxy): Retrieves the parent GstVaapiObject (GstVaapiSurface, GstVaapiImage, etc.) - gst_vaapi_buffer_proxy_get_type(GstVaapiBufferProxy *proxy): Retrieves the type of the underlying buffer handle - gst_vaapi_buffer_proxy_get_handle(GstVaapiBufferProxy *proxy): Retrieves the underlying buffer handle - gst_vaapi_buffer_proxy_get_size(GstVaapiBufferProxy *proxy): Retrieves the size of the buffer
commit 250260cc36189911c5ebf62eade4c1a1647c85d8 Author: Gwenole Beauchesne <gwenole.beauchesne@intel.com> Date: Mon Sep 15 10:58:51 2014 +0200 Add abstraction for exported VA buffers. The VA buffer export APIs work for a particular lifetime starting from vaAcquireBufferHandle() and ending with vaReleaseBufferHandle(). As such, it could be much more convenient to support implicit releases by simply having a refcount reaching zero. https://bugzilla.gnome.org/show_bug.cgi?id=736721