[Bug 743345] glupload: Add support for dmabuf
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Oct 13 07:23:22 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=743345
--- Comment #35 from Julien Isorce <julien.isorce at gmail.com> ---
>From last discussion there is still a problem which is:
In case of memory:EGLimage, the GstEGLImageMemory own a gl texture from which
it has been created. So gst_is_egl_image_memory(mem) will return true and you
can access the eglimage through gst_egl_image_memory_get_image(mem). But there
is currently no way to access the owned gl texture.
In case of memory:GLMemory (created from dmabuf), the GstGLMemory owns an
eglimage. (actually should own because the current solution just create and
destroy it right after). So gst_is_gl_memory(mem) return true and you can
access the gl texture through gst_gl_memory_get_texture_id (mem) (at least this
function should exist instead of using mem->tex_id).
So as you can see there are reverse way. First eglimage own texture, second gl
texture owns eglimage.
Currently GstGLMemory and GstEGLImageMemory do not have any kind of relation.
Should it possible to use the GstMemory::parent for this or is it only about
memory sharing ?
I was thinking in the first case, GstEGLImageMemory is parent of GstGLMemory
and in the second case GstGLMemory is parent of GstEGLImageMemory.
In any case we need to find a nice way to handle the 2 cases. Any suggestion ?
--
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