Re: [web-audio-api] What should happen in case of cycles containing a delay node is under-defined (#75) from Olivier Thereaux on 2013-09-11 (public-audio@w3.org from July to September 2013)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:30 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/75/24244166@github.com>

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=23037#0) by Robert O'Callahan (Mozilla) on W3C Bugzilla. Wed, 21 Aug 2013 22:17:00 GMT

Having to recheck for cycles every time we sample the delay AudioParams would be pretty bad I think.

So I think we should clamp the DelayNode's delay to a minimum of 128 cycles at all times. Then cycle-checking just needs to ensure there's at least one DelayNode in every cycle and we're fine.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/75#issuecomment-24244166

Received on Wednesday, 11 September 2013 14:32:44 UTC