W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > April 2017

Re: [mediacapture-main] Add autoGainControl and noiseSuppression constraints.

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Sun, 30 Apr 2017 21:18:48 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-298257868-1493587127-sysbot+gh@w3.org>
@ShijunS Constraints don't have defaults, by design. Unconstrained == UA chooses. Constraints are externalized (app) requirements letting UAs change device properties as they sees fit within the net envelope of all constraints put on it.

So basically, as a user of the API, if I care about a property, I should constrain it. If I don't care, I shouldn't have expectations of what value it'll have.

> Would they be different based consuming target objects?

They could be. The [spec](https://w3c.github.io/mediacapture-main/getusermedia.html#the-model-sources-sinks-constraints-and-settings) says:

 *"Implementations may choose to make such source-to-sink optimizations as long as they only do so within the constraints established by the application, as the next example demonstrates.*

*It is fairly obvious that changes to a given source will impact sink consumers. However, in some situations changes to a given sink may also cause implementations to adjust a source's settings."*

I don't think anyone has implemented anything like that yet though, but maybe someday.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/444#issuecomment-298257868 using your GitHub account
Received on Sunday, 30 April 2017 21:18:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:32 UTC