- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Thu, 18 Sep 2014 11:18:54 +0200
- To: public-media-capture@w3.org
On 09/17/2014 04:03 PM, Kostiainen, Anssi wrote: > Hi All, > > On 17 Sep 2014, at 16:23, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote: > >> Media Capture question! >> >> -------- Forwarded Message -------- >> Subject: RE: publish FPWD of Media Capture Depth Stream Extensions; >> respond by 26 Sept 2014. >> Date: 16/09/14 19:52 >> From: Bernard Aboba <Bernard.Aboba@microsoft.com> >> To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, >> public-webrtc@w3.org <public-webrtc@w3.org> >> >> Out of curiosity - what happens in addTrack(mst) if mst.kind == 'depth'? > Bernard - thanks for the feedback. > > The short answer is, this needs to be specified in the spirit of “[t]his document is not complete and is subject to change”. > > I’ve logged this as an open issue [1] and the editors will look at this shortly and come back with a proposal. All the Task Force participants are encouraged to provide suggestion on the preferred behaviour too. This seems to be a multifaceted thing, since I don't know how a depth channel should be represented across the network either; there are H.26x extensions for carrying depth channels inside a video stream, but I'm not sure those extensions are supported by the relevant RTP formats. And how is a depth channel best represented if there's no associated video? > > [This should not block the FPWD publication, however.] > > Thanks, > > -Anssi > > [1] https://github.com/w3c/mediacapture-depth/issues/18
Received on Thursday, 18 September 2014 09:19:31 UTC