The HRTF panner uses significant memory for the responses and requires a fair amount of processing to implement. For low-end mobile devices, this can be an issue. Since the default panner model is HRTF, the creation of the panner can cause the responses to be loaded. The default has been changed to equalpower, which doesn't consume significant memory and is much less intensive in processing power.
Specification
Status in Chromium
Enabled by default (tracking bug) in:
- Chrome for desktop release 40
- Chrome for Android release 40
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- No signal
- No signal
- No signal
- No signals
Owner
Search tags
Web Audio API, PannerNode, Panning Model, HRTF, Stereo,Last updated on 2021-01-10
Comments
See also: https://github.com/WebAudio/web-audio-api/issues/368