This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Audio-ISSUE-73 (ConvolverNodeLimits): ConvolverNode buffer size limits [Web Audio API] http://www.w3.org/2011/audio/track/issues/73 Raised by: Philip Jägenstedt On product: Web Audio API https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#ConvolverNode Should there be an upper limit for the length of the impulse response buffer? If a huge buffer is used this could easily completely destroy performance. If there are no practical uses for convolution over a certain size, we could just limit it and avoid different implementations having different internal limits and having to reverse engineer the competition to figure out what the Web-compatible limits are.
Do we have any limits on the dimensions of <img>, or size of objects in WebGL? I'm just trying to get an idea if we have any examples to follow here. If we do make a limit, then I'd like to make it rather high, like > 1 minute
Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.