I think it would be valuable to have depth data accessible in absolute units, such as linear 16-bit millimeters, or floating-point meters. The logical way to implement this would be as the depth component of a GL texture, which can be UNSIGNED_SHORT or FLOAT in GLES 3.0. Unfortunately, WebGL is currently limited to GLES 2.0, which does not appear to support setting arbitrary depth component values. Therefore, to support this use case, it might be appropriate for your Extension to include modifications both to getUserMedia and to WebGL. On Wed, Jan 29, 2014 at 4:55 AM, Kostiainen, Anssi < anssi.kostiainen@intel.com> wrote: > Hi All, > > On 16 Dec 2013, at 00:07, Rob Manson <roBman@mob-labs.com> wrote: > > > I'll contact you and Anssi off list and we can start working on the > extension proposal in the early new year. > > Together with Ningxin and Rob we've now collected use cases and > requirements for the proposed Media Capture Depth Stream Extension the > group discussed at TPAC, see: > > http://www.w3.org/wiki/Media_Capture_Depth_Stream_Extension > > We believe we now have a good set of use cases and requirements to be used > as a starting point for the work, and would like to ask the group to review > the above UCs and reqs, let us know if you have any suggestions, concerns.. > > If we hear no concerns, we’ll start drafting a concrete proposal for the > depth stream extension, layer it on top of the getUserMedia API as an > extension specification [1]. This allows us to proceed independently with > the extension, not block the core dependency getUserMedia. > > Thanks, > > -Anssi > > [1] http://www.w3.org/html/wg/wiki/ExtensionSpecifications >
Received on Friday, 31 January 2014 08:59:23 UTC