Re: [web-audio-api] What should happen in case of cycles containing a delay node is under-defined (#75)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=23037#10) by Jussi Kalliokoski on W3C Bugzilla. Sat, 31 Aug 2013 17:21:05 GMT

(In reply to [comment #9](#issuecomment-24244210))
> Clamping to a minimum of one block is only going to happen when the
> DelayNode is part of a cycle. Hopefully your use-cases for low delays don't
> require DelayNodes in cycles.

Unfortunately they do; One common way of achieving wind synthesis is to have a noise and DC source which is then fed to a short feedback loop. There you get feedback resonation, and the length of the delay essentially becomes the base wave length of the note you want to play (similar to how sound moves in a pipe). In practice it's not quite as simple as this of course, there's a lot of filter-work to be done afterwards, but this phase is crucial for the process. If you clamp the delay time down to 128 samples, at the sample rate of 48kHz this gives you the hard limit of 48000Hz/128=375Hz which doesn't really suffice for any wind instrument.

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