[Bug 764148] gtkglsink doesn't fail to create on incompatible hardware

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri Mar 25 06:59:55 UTC 2016


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

--- Comment #6 from Matthew Waters (ystreet00) <ystreet00 at gmail.com> ---
(In reply to Russel Winder from comment #4)
> Given the GStreamer architecture, that makes sense. (Sorry I had to be hit
> over the head with this point twice before it sank in.)
> 
> That leads to the questions:
> 
> Is it possible to query the platform and GStreamer to see if the OpenGL
> version the former provides and the latter requires are harmonious prior to
> making the choice of whether to create a gtkglsink or a gtksink?

Unfortunately, not really without creating your own GtkGLArea and GstGLContext
(like gtkglsink).

> If a gtkglsink element has been created, is there a message on the bus prior
> to instantiating the GL context?

No.

> Is it feasible to replace the gtkglsink with a gtksink and continue if the
> GL context creation fails?

Generally what you do is create gtkglsink (or any element) and set it to READY
for some basic sanity checking that it's supported before adding it to the
pipeline.  If any of that fails you fall back to something else like gtksink or
autovideosink or ...

The mechanism described above is precisely how playsink and autovideosink
select their video sinks so it's standard practice.

-- 
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