[Bug 755072] vaapi: expose memory:DMABuf capsfeature
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Mon Oct 3 09:59:59 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=755072
--- Comment #48 from Julien Isorce <julien.isorce at gmail.com> ---
I implemented options 2, i.e. re-use GstVaapiSurface->extbuf_proxy to cache
GstVaapiBufferProxy which now owns the GstMemory(FD). And seems to work fine, I
can see that in GstGL it creates only 16 EGLImages (2 per frames and because 8
dmabuf because 8 vaapisurface on a 720p video) but then that is all, it is
cached and properly re-used in GstGL.
https://github.com/CapOM/gstreamer-vaapi/commit/7364ea196030ac56b5aaf75a0b8a485e611390a5
(branch "ceyusa_755072_plus_caching")
I had to add the 3 new following API:
GstMemory*
gst_vaapi_buffer_proxy_get_memory (GstVaapiBufferProxy * proxy, gsize size);
void
gst_vaapi_surface_set_buffer_proxy (GstVaapiSurface * surface,
GstVaapiBufferProxy * proxy);
GstVaapiBufferProxy *
gst_vaapi_surface_peek_buffer_proxy (GstVaapiSurface * surface);
Let's discuss about it and then I can re-work it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list