Closed
Bug 1275961
Opened 9 years ago
Closed 6 years ago
Allow developer to specify the Audio Context sampling rate
Categories
(Core :: Web Audio, defect, P3)
Core
Web Audio
Tracking
()
RESOLVED
DUPLICATE
of bug 1387454
| Tracking | Status | |
|---|---|---|
| platform-rel | --- | - |
People
(Reporter: sole, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: DevAdvocacy)
This is something developers ask me really often - specially also since we can record stuff with MediaRecorder and it seems it will just accept whichever sampling rate the stream carries, but will not let the developer configure it.
So developers have no way of controlling the end sampling rate result.
I know this is not even defined in the spec level yet, but this can help spec writers see what people want to do.
There's an existing bug filed in the spec for this: https://github.com/WebAudio/web-audio-api/issues/300
|
Reporter | |
Updated•9 years ago
|
|
|
Reporter | |
Updated•9 years ago
|
Keywords: DevAdvocacy
|
||
Comment 1•9 years ago
|
||
I agree this would be useful.
Perhaps an OfflineAudioContext may be an option in the meantime for MediaRecorder?
|
||
Comment 2•9 years ago
|
||
This is planned on a spec level but we need to write some code to be able to have multiple MediaStreamGraph that can communicate with different sample rates.
Depends on: 1265402
|
||
Comment 3•9 years ago
|
||
Initially setting the priority of this bug to match that of its blocking bug.
Priority: -- → P2
|
|
||
Updated•9 years ago
|
Flags: platform-rel?
|
|
||
Updated•9 years ago
|
platform-rel: --- → ?
|
|
||
Updated•9 years ago
|
platform-rel: ? → -
|
||
Comment 4•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
|
||
Comment 5•6 years ago
|
||
We've have this implemented for some time now, implemented in bug 1387454.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•