New issue
Advanced search Search tips

Issue 889851 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 731170
Owner: ----
Closed: Oct 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Supported audio constraints do not function

Reported by ragy.mor...@vocitec.com, Sep 27

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce the problem:
1. Visit https://mdn.mozillademos.org/en-US/docs/Web/API/Media_Streams_API/Constraints$samples/Example_Constraint_exerciser?revision=1411870 At the top, sampleRate is listed as an available constrainable property.
2. change the "Requested audio constraints:" to {"sampleRate": 8000} then click "Apply Constraints".

What is the expected behavior?
In the "Actual audio settings" box, the sampleRate does not change. In my case, it stays as "sampleRate": 48000, but your computer could show slightly different one like 41000. Nevertheless, setting it to 8000 doesn't work.

What went wrong?
Chrome says it supports the "sampleRate" media constraint (can be obtained via navigator.mediaDevices.getSupportedConstraints() in the console), but it doesn't, as seen in the Mozilla demonstration.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 69.0.3497.81 (Official Build) (64-bit)  Channel: stable
OS Version: 16.04
Flash Version: 31.0.0.108
 
Labels: Needs-Triage-M69
Components: Blink>WebAudio
Components: Blink>MediaStream
I believe this is about MediaStream API.
Components: -Blink>WebAudio
Indeed.  And it's not a WebAudio issue.
This is a bug we're working on. However, note that saying {"sampleRate": 8000} does not mean that the sample rate has to change to 8000. It just means that, among the supported rates, you would prefer the one closest to 8000.
Once we fix the bug, behavior in this particular example will not change.
Mergedinto: 731170
Status: Duplicate (was: Unconfirmed)
Yes, that's correct, but usually there should be at least one supported sampling rate lower than the default 48kHz, and hence I would get a different output so I will know it works. Moreover, in another test, I used {"sampleRate": {"exact": 8000}}, and it behaved in the same way. I believe when I use the "exact" keyword, I should either get the exact requested sample rate or an error of some sort.

Sign in to add a comment