[Bug 704809] Use one GstGLContext per streaming thread

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=704809
  GStreamer | gst-plugins-gl | git

--- Comment #4 from Sebastian Dröge (slomo) <slomo at circular-chaos.org> 2013-08-27 10:42:12 UTC ---
(In reply to comment #3)

> > 
> > Sharing between contexts should work in theory, 
> 
> Could you clarify ? I mean what should work compared to gst-gl-0.10 ?

What do you mean? If you have a pipeline where upstream uses a different
context than downstream, sharing of buffers between them is supposed to work.

> > > ** With solution 1) and 2) we would need to know in which streaming thread we
> > > are in GST_QUERY_CONTEXT. If we are in the same then we use it directly but if
> > > we are in an other streaming thread then we share. How to do that ? Improve
> > > GstContext ? Is there a GST_QUERY_STREAMING_STATUS ? I only saw examples with
> > > messages.
> > 
> > There's nothing yet for that, we need to add API for that. I think it should be
> > part of the ALLOCATION query (as said in the other bug, GstContext should here
> > probably only be used to share GstGLDisplay, not GstGLContext and thus not the
> > threads).
> 
> I'm not convinced :)
> I think GstGLDisplay should be removed, and merged into GstGLContext. I mean in
> the gstgl history gstgldisplay should had been called gstglcontext from the
> beginning.
> 
> Currently in HEAD what is the goal of GstGLDisplay ? Almost just be able to
> call gst_gl_display_thread_add. Why not just move it to GstGLContext ?
> 
> Also I do not see a use case where we would need to use a GstGLDisplay without
> a GstGLContext.

It's work-in-progress, see the related bug reports. GstGLDisplay will become
smaller and will just share whatever is required to create a context (and thus
a surface). You want to share that between elements because otherwise they most
likely can't interoperate in a fast way.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.