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

RE: Early Holiday Present: Settings API version 6

From: Mandyam, Giridhar <mandyam@quicinc.com>
Date: Fri, 21 Dec 2012 20:17:01 +0000
To: Travis Leithead <travis.leithead@microsoft.com>, Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <CAC8DBE4E9704C41BCB290C2F3CC921A16384913@nasanexd01h.na.qualcomm.com>
>> Minor comment:  I still would like to see the definition of 'gain'
>> consistent with WebAudio (see https://dvcs.w3.org/hg/audio/raw- 
>> file/tip/webaudio/specification.html#attributes-GainNode).

>They are more-or-less already aligned. From your previous feedback I changed the type from unsigned long to float, and set the initial value at 1. Per my reading of the linked document that's basically the parameter constraints on the WebAudio gain value.

Thanks Travis for clarifying.  Look forward to seeing the merged doc.

-Giri
-----Original Message-----
From: Travis Leithead [mailto:travis.leithead@microsoft.com] 
Sent: Friday, December 21, 2012 12:04 PM
To: Mandyam, Giridhar; Stefan Hakansson LK; public-media-capture@w3.org
Subject: RE: Early Holiday Present: Settings API version 6

> From: Mandyam, Giridhar [mailto:mandyam@quicinc.com] What does this 
> mean for the concept of remote source types?  Particularly Issue no. 5 
> in http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-

> capture/proposals/SettingsAPI_proposal_v6.html#constraint-manipulation
> - api-extensions-to-mediastreamtrack seems to open the door to 
> applying constraints to a remote source using mechanisms that as far 
> as I can tell are currently undefined.

I think we should work to define them better once v6 is merged. "remote" seems like an interesting and necessary source type, even if we all jointly decide that those sources simply ignore constraints completely...


> Moreover, in http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-

> capture/proposals/SettingsAPI_proposal_v6.html#constraint-manipulation
> - api-extensions-to-mediastreamtrack under "Remote Media" it is stated 
> that "These requirements for remote media are outside the scope of the 
> Media Capture task force".  If we are going to define remote sources 
> and possibly how to apply constraints to them, then I don't see how we 
> can cay anymore that requirements for remote media are outside the 
> scope of the TF.

"Outside the scope of our task force" may be inappropriate wording then. This is meant to convey that we need to work closely with WebRTC to understand and specify how this will work or not. 


> I think that the merged document can still have 'remote' as part of 
> the SourceTypeEnum, but any discussion about constraints and their 
> applicability to remote sources should be clearly marked as TBD or 
> even out-of-scope.

I agree.


> Minor comment:  I still would like to see the definition of 'gain'
> consistent with WebAudio (see https://dvcs.w3.org/hg/audio/raw- 
> file/tip/webaudio/specification.html#attributes-GainNode).

They are more-or-less already aligned. From your previous feedback I changed the type from unsigned long to float, and set the initial value at 1. Per my reading of the linked document that's basically the parameter constraints on the WebAudio gain value.


Received on Friday, 21 December 2012 20:17:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:13 UTC