[Bug 739681] GstGL: let applications use the glimagesink's output texture
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Mar 10 04:12:51 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=739681
--- Comment #5 from Julien Isorce <julien.isorce at gmail.com> ---
I am going to work on that during the GStreamer hackfest 2015 this weekend.
I realized that we can make it work with the existing "client-draw" callback.
So if the user provide a wrapped GL context with "gst_gl_context_new_wrapped
through glimagesink property or through GstContext", and if the user also use
the "client-draw" callback then we need to make glimagesink not create any
visible window.
Also existing signal is good because it's blocking so we can benefit qos for
example, and we make sure to be synchronized with audio and subtitles.
I have some initial work around. I will also make a minimal example with SDL.
I also wonder if we should add GstSample* as one of the input. Currently this
is:
gboolean client_draw_callback (GstElement* object, GstGLContext*, guint
texture_id, guint width, guint height, gpointer user_data);
(having explicitly id, w, and h still avoids the user to do gst_video_frame_map
to get the size and texture id). Having also GstBuffer* would allow some custom
work.
I also do not like the name of the signal "client-draw", I would like to rename
it to "new-sample" (like appsink signal) or to "push-sample".
--
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