[Bug 750310] Ideas around GstGLContextGPUProcess
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Jun 2 18:58:57 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=750310
--- Comment #1 from Matthew Waters <ystreet00 at gmail.com> ---
1) is solved by adding a "create-context" signal on GstGLDisplay that is called
in lieu of the current gst_gl_context_new(); gst_gl_context_create();
There you set your custom window on your custom context. And viola, you have
gstgl using your custom GstGLContext.
Would also need a helper for elements to call the signal without worrying about
GstGLDisplay locking.
2) You should really create your own element and stop abusing glimagesink for
its client-draw signal. The original intent for client-draw was to allow the
application to draw the input texture however in the output window provided by
glimagesink. Passing the output to another process/library is better suited to
an appsink/glappsink like element if needed. See gtkgst for some inspiration.
3) Already handled by GstContext.
--
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