[Bug 776927] vaapi: plugins: accept GLMemory buffers from upstream

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=776927

--- Comment #10 from Matthew Waters (ystreet00) <ystreet00 at gmail.com> ---
(In reply to Víctor Manuel Jáquez Leal from comment #8)
> In deed. In the case of GLX, (again) IIUC, it would need to dump the
> texture's pixels into a pixmap and then copy it into a system's memory
> GstMemory. It won't be zero-copy.
> 
> Which brings me to another approach to this functionality: the element
> gldownload.
> 
> That element downloads a GstGLMemory into a system's memory based GstMemory.
> Which is normally the case without zero-copy.

Which is actually just a simple wrapper for the caps negotiation to be correct
currently, all the transfers happen in the memory when mapped/unmapped.

> We could extend this functionality to the case where the GstGLImage is EGL,
> and EGL_MESA_image_dma_buf_export is available, to generate a
> GstDmaBufMemory, which could be imported by gstreamer-vaapi as is.
> 
> What do you think Matthew??

That's certainly a possibility.  There's still the option of the dma-buf import
failing so I think gldownload will have to push a combined memory type so that
on dma-buf import failure, one can fallback to a texture download and reupload
into vaapi.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.