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

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:38 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/75/24244236@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=23037#12) by Jussi Kalliokoski on W3C Bugzilla. Sun, 01 Sep 2013 12:08:03 GMT

(In reply to [comment #12](#issuecomment-24244231))
> OK. Unfortunately that's just too bad. You'll need to write your simulator
> in JS.

Hahah, yeah, I expected as much. I'll just have to wait until for worker processing (and that I make a new audio processing library) before finishing my work on it. Kinda sad how even the simplest parts of Web Audio API, such as delay, fail to be usable in some cases. There probably won't be a backwards compatible way of supporting this use case in the future either, aside from adding another delay node type with different semantics.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:34:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC