Intent to Prototype: WebAudio: Configurable render quantum
Chromestatus
Contact emails
hong...@chromium.org, mjwi...@chromium.orgExplainer
NoneSpecification
https://webaudio.github.io/web-audio-api/#dom-baseaudiocontext-renderquantumsizeSummary
AudioContext and OfflineAudioContext now take an optional renderSizeHint, which allows users to ask for a particular render quantum size when an integer is passed, to use the default of 128 frames if nothing or "default" is passed, or to ask the User-Agent to pick a good render quantum size if "hardware" is specified.
Blink component
Blink>WebAudioMotivation
It is difficult and complex to write a web app when the audio processing block size does not match with the WebAudio render quantum size (128 sample-frames). Removing this restriction and making it customizable on AudioContext would enable easier development and more efficient audio processing.
Initial public proposal
NoneTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
None
Gecko: No signal (https://github.com/WebAudio/web-audio-api/pull/2469) A Firefox developer wrote the specification change.
WebKit: No signal
Web developers: Positive (https://github.com/WebAudio/web-audio-api/issues/1503) Developers have requested a way to increase the render quantum size, and are looking forward to the feature being implemented.
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Debuggability
None
Is this feature fully tested by web-platform-tests?
NoFlag name on about://flags
NoneFinch feature name
NoneNon-finch justification
NoneRequires code in //chrome?
FalseTracking bug
https://crbug.com/40637820Estimated milestones
No milestones specified