- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Mar 2016 08:57:39 +0000
- To: public-media-capture@w3.org
anssiko has just created a new issue for https://github.com/w3c/mediacapture-depth: == Range constraint == Creating a standalone issue for this discussion started in #100: >@jan-ivar: > I naively imagine I'd probably want a different setting for pointing my kinect out my window vs. pointing it at my couch? > @martinthomson: >@jan-ivar, that would be a separate constraint, probably two. minimumRange: 1, maximumRange: 100. If that's a real concern, then a separate issue. For this one, I think that @anssiko has the right approach: find out how do the devices actually measure and work from there. >@huningxin: >@jan-ivar, Kinect SDK allows to configure depth camera range (`Default` or `Near`) [\[1\]](https://msdn.microsoft.com/en-us/library/microsoft.kinect.depthimagestream.range.aspx). libealsense [\[2\]](https://github.com/IntelRealSense/librealsense/blob/master/include/librealsense/rsutil.h#L107) allows to configure several ranges to RealSense front facing depth camera as well (`Common`, `ShortRange`, `LongRange` etc.,). I am not aware Tango SDK allows to configure working range of its depth camera. Please view or discuss this issue at https://github.com/w3c/mediacapture-depth/issues/114 using your GitHub account
Received on Wednesday, 23 March 2016 08:57:41 UTC