render to egl texture
ystreet00 at gmail.com
Mon Mar 15 09:40:38 UTC 2021
This combination is fine if libgstgl is built for those platforms and
your log would indicate that this is the case.
Almost all gl elements in gst-plugins-base support that combination.
glupload, gleffects, glimagesink, gltestsrc are non-exhaustive examples
that support that just fine. There are very few gl elements nowadays
that struggle with the (gles2) requirement. wayland+egl is fine and is
supported by all OpenGL elements.
Further comments inline.
On 15/3/21 8:13 am, Joel Winarske wrote:
> Using the below combo of variables seems to be invalid, for both
> Ubuntu 18.04 LTS (Wayland on Ubuntu) and Fedora 33 (Wayland is active
> by default). Canonical (Ubuntu) is stating they will default with
> Wayland (again) in an upcoming release.
These variables will only have any effect when GStreamer is creating the
necessary resources. If you are passing in some shared resources
(display or OpenGL context), GStreamer will use the values from there
> What gl test cases are expected to work via wayland/egl/gles2? Or any
> test case for that matter.
The gtk examples support wayland, otherwise the gtkglsink or qmlglsink
elements contain the necessary code for retrieving the wl_display from
those respective toolkits and then passing the required GstGLDisplay to
> On Thu, Mar 11, 2021 at 4:02 PM Joel Winarske <joel.winarske at gmail.com
> <mailto:joel.winarske at gmail.com>> wrote:
> I'm taking a look at the sdlshare example, and porting to Fedora
> 33 - wayland/egl.
> After pausing the pipeline I get an eglCreateContext EGL Error of
> EGL_BAD_CONTEXT. The context being passed in is shared, without a
> How do I avoid the dummy window altogether?
> My end goal is to simply update a texture on each frame. Something
> else renders the texture.
For wayland, you need to share the wl_display between SDL and
GStreamer. Once you retrieve the wl_display from SDL, create the
necessary GstGLDisplay with gst_gl_display_wayland_new_with_display().
> On Tue, Mar 9, 2021 at 4:42 PM Matthew Waters <ystreet00 at gmail.com
> <mailto:ystreet00 at gmail.com>> wrote:
> There is no way to know the texture ID without uploading the
> The texture ID is almost never a constant value. At least,
> there will probably be two textures that will be flipped
> between. At most, each texture id will be unique.
> On 10/3/21 5:34 am, Joel Winarske wrote:
>> In my use case (video player) I just need to initialize the
>> pipeline and return a texture id.
>> Is there a way to determine the texture id without loading a
>> Is the texture id constant over the lifecycle of the pipeline?
>> On Mon, Mar 8, 2021 at 9:57 PM Matthew Waters
>> <ystreet00 at gmail.com <mailto:ystreet00 at gmail.com>> wrote:
>> That is one option if you're looking to use glimagesink's
>> rendering. If you're rendering the texture yourself,
>> something like
>> is more appropriate.
>> On 9/3/21 1:37 pm, Joel Winarske wrote:
>>> I'm figuring a pipeline like this:
>>> uri=file:///usr/local/share/assets/video.mp4 !
>>> ! glimagesink
>>> To get the texture id I see a pattern in the cube
>>> example of attaching callback to "client-draw" of
>>> glimagesink, then mapping the video buffer which
>>> provides access to the texture id. Is this the only way
>>> to access the texture id?
>>> On Mon, Mar 8, 2021 at 4:59 PM Joel Winarske
>>> <joel.winarske at gmail.com
>>> <mailto:joel.winarske at gmail.com>> wrote:
>>> Thank you for that.
>>> What is the current recommended pattern for
>>> rendering to a GL texture which gets consumed by a
>>> shared context? The shared context handles the
>>> On Mon, Mar 8, 2021 at 4:32 PM Matthew Waters
>>> <ystreet00 at gmail.com <mailto:ystreet00 at gmail.com>>
>>> clutter has not been recommended for many
>>> years. gst-plugins-gl neither for many more.
>>> gst-plugins-gl has been migrated into
>>> gst-plugins-bad as can be seen from the latest
>>> commit on that repo:
>>> and then promoted to gst-plugins-base and is
>>> available as the libgstgl-1.0 library.
>>> On 9/3/21 8:59 am, Joel Winarske wrote:
>>>> still the recommended pattern for rendering to
>>>> an EGL texture?
>>>> gstreamer-devel mailing list
>>>> gstreamer-devel at lists.freedesktop.org <mailto:gstreamer-devel at lists.freedesktop.org>
>>>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel <https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 495 bytes
Desc: OpenPGP digital signature
More information about the gstreamer-devel