W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] (ConvolverNodeLimits): ConvolverNode buffer size limits (#117)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:26 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/117@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17360](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17360) Tue, 05 Jun 2012 11:48:54 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/117
Received on Wednesday, 11 September 2013 14:28:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC