- From: Mandyam, Giridhar <mandyam@quicinc.com>
- Date: Mon, 23 Mar 2015 23:09:28 +0000
- To: "Hu, Ningxin" <ningxin.hu@intel.com>, 'Harald Alvestrand' <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
> I think PhotoCapabilities and PhotoSettings are only for color image capture. We may add DepthCapabilities and DepthSettings for depth image capture. > This is similar to native camera SDKs. They usually group capture properties to color and depth, and provide property query and set API. I think this is fine, but we should arrive at agreement as to what the depth capabilities/settings are. It does not appear that Qualcomm and Intel are providing support for depth settings at the driver level in the same way (at least for Android devices). I assume that the settings listed in the current Depth Camera extensions (http://w3c.github.io/mediacapture-depth/#settings-dictionary) are compatible with RealSense SDK. So I have a homework assignment to see if these settings work with the Qualcomm-recommended driver. -Giri -----Original Message----- From: Hu, Ningxin [mailto:ningxin.hu@intel.com] Sent: Wednesday, March 18, 2015 6:32 PM To: 'Harald Alvestrand'; public-media-capture@w3.org Subject: RE: Depth image capture workflow proposal for Web Hi Harald and Anssi, > From: Harald Alvestrand [mailto:harald@alvestrand.no] > Sent: Wednesday, March 18, 2015 11:36 PM > > On 03/18/2015 03:27 PM, Kostiainen, Anssi wrote: > > Hi Giri, Ningxin, All, > > > >> On 18 Mar 2015, at 05:13, Hu, Ningxin <ningxin.hu@intel.com> wrote: > > Ningxin - thanks for informing the TF mailing list of the recent > developments. > > > > [...] > > [[ > > > > [Constructor(MediaStreamTrack track), > > Constructor(MediaStream stream)] > > interface ImageCapture { > > // .. > > }; > > > > ]] > > > > That'd allow other specs to reuse and extend ImageCapture APIs, > > I'd want to ask, though: Does the API that gets reused have to carry > everything currently defined on ImageCapture? > > In particular, the PhotoCapabilities and PhotoSettings may not be > applicable to something that captures something very different from > images. (what's the whiteBalanceMode of a depthmap?) > I think PhotoCapabilities and PhotoSettings are only for color image capture. We may add DepthCapabilities and DepthSettings for depth image capture. This is similar to native camera SDKs. They usually group capture properties to color and depth, and provide property query and set API. > > enable extensions such as: > > > > [[ > > > > partial interface FrameGrabEvent { > > readonly attribute DepthMap depthMap; }; > > > > partial dictionary FrameGrabEventInit { > > DepthMap depthMap; > > }; > > > > ]] > > > > I observe the interface name "ImageCapture" may not be a perfect > > match for a more generalized API, but the ship may have sailed on > > the name (has the feature shipped btw?). If we could still rename > > things, "MediaCapture" would perhaps be a better name for a > > generalised API that's able to extract also other data than > > ImageData our of MediaStreamTracks or MediaStreams. But I don't want > > to bikeshed about naming at this time :-) > > ImageCapture has not been shipped. I understand "ImageCapture" name is fine. Supporting depth image capturing or 3D image (color + depth) capturing are all under "Image Capturing". Thanks, -ningxin > > > > > Thanks, > > > > -Anssi > > > > [1] http://w3c.github.io/mediacapture-image/ >
Received on Monday, 23 March 2015 23:10:03 UTC