W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2012

RE: Distinguishing video and audio streams to enable fine-grained feature control

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Tue, 14 Aug 2012 17:50:46 +0000
To: Rich Tibbett <richt@opera.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B38384034F6@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
> From: Rich Tibbett [mailto:richt@opera.com]
> Hi,
> During the last few months we've received a number of requests from
> developers to provide more granular control over camera streams provided
> via getUserMedia. Such requests have centered around providing auto-focus
> feature detection/setting/monitoring, zoom detection/setting/monitoring,
> enabling camera flash in a sensible way, and changing the
> rotation/orientation of a webcam stream. Because the current specification
> does not incorporate these features at present we did some brainstorming
> and came up with the following idea.

Overall, I like the extra detail this brings and look forward to iterating on the design. Thanks for the proposal!

> [NoInterfaceObject]
> interface CameraInfo {
>             attribute unsigned short facing;
>    // facing above will be either 'user' or 'environment'

As we looked at extracting these details for a variety of camera types before (when these tokens were part of the options string for getUserMedia), it proved to be very hard to know what direction a camera is facing. In practice the only time we could positively identify this detail was when the camera was part of an embedded hardware and the manufacture's driver supplied this information. In relation to the proposal, I would suggest adding an "unknown" value for cases where the facing value can't be identified.
Received on Tuesday, 14 August 2012 17:51:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:24:36 UTC