[Public WebGL] OES_EGL_image_external Extension proposal

Florian Bösch [email protected]
Mon Oct 10 23:40:39 PDT 2016


Am I correct in assuming that once you've called ext.
EGLImageTargetTexture2DOES(ext.TEXTURE_EXTERNAL_OES, videoElement); that
the texture is "bound" to the video and no further calls need to be emitted
(as would presently be the case) for it to stay current?

If that's the case, I think it's a good idea, it takes some work off web
application programmers to make sure the video is updated, and it should
also in all cases avoid a texture download/reupload.

There are some other extensions that have attempted to deal with this
problem.

   -
   https://www.khronos.org/registry/webgl/extensions/rejected/WEBGL_texture_from_depth_video/
   : this extension is rejected because it introduced a complex behavioral
   changes/semantics whose benefits where unclear and the champions of this
   extension stopped responding to questions and didn't offer any improvements
   on the extension specification.
   -
   https://www.khronos.org/registry/webgl/extensions/proposals/WEBGL_dynamic_texture/
   : this extension is currently in a proposal state and it covers similar
   functionality as EGL_image_external. Where it fundamentally differs is that
   it also deals with format conversions (YUV 442 to rgb etc.) and accurate
   timing for presentation of a video frame.

 Perhaps you could elaborate a little why OES_EGL_image_external would be
preferrable to WEBGL_dynamic_texture, and how the issues that
EGL_image_external does not tackle (timing, format conversion, other
things) would be handled by the web application programmer?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20161011/d1ce0caa/attachment.html>


More information about the public_webgl mailing list