<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Thanks Matthew! I’ll follow that up.<div><br></div><div>Best,</div><div>Michael</div><div><br></div><div><div><div>On 14 May 2014, at 12:39 am, Matthew Waters <<a href="mailto:waters.matthew00@gmail.com">waters.matthew00@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;">Sure, glimagesink is the way forward for a GL-based video sink however it does not seem to have support for the GstVideoOverlay API on the RPI [1]. glshader is a little finicky in that it expects a couple of things in order to integrate with the video pipeline. Most notably would be the texture parameter in order to access the frame data, which is a NPOT 2D texture represented by "sampler2D tex" in GLSL.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><br></div></body></html>