Re: Adding "Media Capture Depth Stream Extensions" as TF deliverable

Hi Anssi,

I'm not sure this terminology is clear or correct.

    A depth stream is an abstraction of a data stream that represents the
    distance between the camera and the subject for each point of the image.

We're not proposing a new type of stream are we? I think we're just 
planning on using the existing MediaStream interface and extending that 
by adding a getDepthTracks() method to the interface.

And perhaps we could be clearer about the use of the term "depth track".

    A depth track is a MediaStreamTrack||object that represents a depth 
stream

Really we're only proposing that we extend MediaStreamTrack to support 
"kind" being set to "depth".

So I'd rewrite that text as:

    This specification extends the getUserMedia based MediaStream interface
    to enable it to also contain MediaStreamTrack's that have their "kind"
    attribute set to "depth". These depth based MediaStreamTrack's can be
    referred to simply as "depth tracks". A depth track is an 
abstraction of a
    stream of image frames that can each be converted to ImageData objects
    which contain an array of pixel data, where each pixel represents the
    distance between the camera and the objects in the scene for that 
point in
    the ImageData array.

It's a bit more wordy but I think it's more explicit.

Also, have we defined more info about the "nature and settings of the 
depth track" that we mention in the constraints section?

BTW: I just got back from the Augmented World Expo in Santa Clara - the 
big annual AR event in the US. The unanimous consensus there was that 
depth sensing was going to be the biggest driving force in the AR 
industry over the next couple of years. So this is perfect timing for 
our spec/extension 8)

roBman



On 5/06/14 5:55 PM, Kostiainen, Anssi wrote:
> Hi All,
>
> On 02 Jun 2014, at 20:24, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
>
>> a group of people have been working on depth track extensions to
>> MediaStreams after a short discussion at last year's TPAC.
>>
>> Use cases and requirements are listed at [1], and there is an initial
>> Editor's draft available [2].
>>
>> Our plan is to make this draft a deliverable of this TF (the formal
>> decision will be when making it a FPWD). Initial editors: Anssi
>> Kostiainen and Ningxin Hu.
> Thanks everyone who've contributed to the draft spec so far. And thanks to the Chairs for the heads-up.
>
> We’re currently looking at closing the open issues [3] and/or noting them in the spec [2], after which we'd be ready for an FPWD publication. We’d like to make the FPWD complete in terms of scope, but as usual, we do not expect FPWD to be perfect (otherwise, it would not be called a FPWD).
>
> All - please feel free to review the spec, discuss on this list, help us close the open issues, or open new issues at [3].
>
> People who are wondering what this is all about, please see the YouTube recording [4] of the Ningxin’s demo. The demo runs in Chromium web browser which is patched with depth camera support. More details (demo source code, patch etc.) at [4].
>
> Thanks,
>
> -Anssi
>
> [1] https://www.w3.org/wiki/Media_Capture_Depth_Stream_Extension
> [2] https://w3c.github.io/mediacapture-depth/
> [3] https://github.com/w3c/mediacapture-depth/issues
> [4] http://youtu.be/7GMkKGPgpx0
>
>
>

Received on Thursday, 5 June 2014 12:11:30 UTC