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)
Documentation
Specification
Specification being incubated in a Community Group
Status in Chromium
Enabled by default
(tracking bug)
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- No signal
- No signal
- Positive
Owners
Last updated on 2021-05-05
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.