WebAudio: Biquad filters run at a-rate

Automations for the BiquadFilter node will run at a-rate (updated every frame) instead of the current k-rate (updated every rendering quantum of 128 frames)

Comments

There are no API changes, but moving from k-rate to a-rate automation will produce audible differences, generally for the better. There will very likely be a performance hit with this change, but only if the application is doing parameter automations for BiquadFilter nodes.

Documentation

• http://webaudio.github.io/web-audio-api/#the-biquadfilternode-interface

Specification

Editor's draft

Status in Chromium

Blink components: Blink

Enabled by default (launch bug) in:

• Chrome for desktop release 50
• Chrome for Android release 50
• Chrome for iOS release 50
• Android WebView release 50
• Opera release 37
• Opera for Android release 37

Consensus & Standardization

• Firefox: No public signals
• Edge: No public signals
• Safari: No public signals
• Web Developers: Positive

Owners

• rtoy@chromium.org
• hongchan@chromium.org

Last updated on 2017-06-14