<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Looking closer at available plug-ins, there's also something called GstGLUpload - which says that it uploads to GL Textures... Is this supposed to be used as a sink? Can it? I've also just learned that if I wanted to use the GstGLShader object, I am forced to make use of the GstGLImageSink? Would GstGLUpload also be acceptable here? Regards, Lasse <div class="moz-cite-prefix">On 08-08-2014 19:09, Lasse Laursen wrote: </div> <blockquote cite="mid:53E4A1BF.2050108@lasselaursen.com" type="cite"> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> Hey y'all, I know this is kind of a beaten horse, but given the recent release of the 1.4 version of gStreamer I thought I'd pull out a stick and give it a few more whacks. Today I finally got around to working out how to properly use an appsink to copy gstreamers video output directly into an OpenGL texture. This works pretty well for now - but I'm constantly trying to work out, if there's a way of bypassing having to copy the data manually and just have gstreamer throw it into an OpenGL texture for me. The glimagesink looked promising, despite it's current 'bad' status and... 0.10 reference manual? I take it, this is the most up-to-date doc currently: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-gl-plugins/html/">http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-gl-plugins/html/</a> (although it probably should eventually be merged into the 'bad' folder given it's status?) Anyway - I had a closer look at the following example: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/tests/examples/gl/generic/cube/main.cpp">http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/tests/examples/gl/generic/cube/main.cpp</a> It seems as though the client callback receives a texture reference... Is there anyway of specifying a texture to which one would like the glimagesink to write, instead of receiving a reference to one in every callback? If not - is it possible to somehow intercept the texture ID earlier - and are there any guarantees that it doesn't change at some point down the line? Regards, Lasse <div class="moz-signature">-- Lasse Farnung Laursen Post.doc at the University of Tokyo <a moz-do-not-send="true" href="http://www.lasselaursen.com">www.lasselaursen.com</a> FB: <a moz-do-not-send="true" href="https://www.facebook.com/lasse.laursen">lasse.laursen </a> Twitter: <a moz-do-not-send="true" href="https://twitter.com/PMP_J">@PMP_J</a></div> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ gstreamer-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> </pre> </blockquote> <div class="moz-signature">-- Lasse Farnung Laursen Post.doc at the University of Tokyo <a href="http://www.lasselaursen.com">www.lasselaursen.com</a> FB: <a href="https://www.facebook.com/lasse.laursen">lasse.laursen </a> Twitter: <a href="https://twitter.com/PMP_J">@PMP_J</a></div> </body> </html>