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

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

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 May 2017 22:39:14 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-298781188-1493764753-sysbot+gh@w3.org>
@ShijunS Usually we look at usage when we're deciding between standardizing a legacy API or deprecating it. The [chromium issue](https://groups.google.com/a/chromium.org/d/msg/blink-dev/mba5ziDLFU4/3MGCjHvSDgAJ) I linked to earlier discusses the latter, and boils down to that they haven't added counters yet, and that usage in httparchive looks low.

But we're not trying to standardize `googAutoGainControl`, `googNoiseSuppression`, `mozAutoGainControl` or `mozNoiseSuppression`.

The PR adds `autoGainControl` and `noiseSuppression` which would instantly have two independent mature implementations. I'd hesitate to predict their popularity based off usage of their vendor-prefixed twins, as I expect most sites think twice before relying on undocumented vendor-prefixed APIs.

Anyway, usage seems like a high bar to me. It's quite unusual for new constraints PRs to even come with two independent mature implementations, let alone any actual usage at all.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/444#issuecomment-298781188 using your GitHub account
Received on Tuesday, 2 May 2017 22:39:21 UTC

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