Advanced audio params don't respect {exact: true} syntax
Reported by
thehunmo...@gmail.com,
Jul 29 2017
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.13 Safari/537.36
Steps to reproduce the problem:
1. Use this form for passing, say, googEchoCancellation as an advanced audio param to getUserMedia():
advanced: [
{
googEchoCancellation: {exact: true},
},
]
2. Examine the resulting value in the "GetUserMedia Requests" tab at chrome://webrtc-internals
What is the expected behavior?
The resulting "Audio Constaints" value in the "GetUserMedia Requests" tab at chrome://webrtc-internals is:
advanced: [
{
googEchoCancellation: {exact: true},
},
]
What went wrong?
The resulting "Audio Constaints" value in the "GetUserMedia Requests" tab at chrome://webrtc-internals is:
advanced: [
{
googEchoCancellation: {exact: false},
},
]
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 61.0.3163.13 Channel: dev
OS Version: OS X 10.12.5
Flash Version:
If I use this form:
advanced: [
{
googEchoCancellation: true,
},
]
Then examining the resulting "Audio Constaints" value in the getUserMedia request output at chrome://webrtc-internals, it is passed correctly:
advanced: [
{
googEchoCancellation: {exact: true},
},
]
Is the first form not officially supported? I would think it should be, given that's how it is expressed in the final object.
,
Jul 31 2017
,
Aug 24
We decided that we won't support nonstandard constraints with the old syntax, so this will not be fixed. A small number of the old prefixed constraints have made it to the standard and are supported (echoCancellation, noiseSuppression and autoGainControl). |
|||
►
Sign in to add a comment |
|||
Comment 1 by guidou@chromium.org
, Jul 31 2017