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

[Bug 23037] What should happen in case of cycles containing a delay node is under-defined

From: <bugzilla@jessica.w3.org>
Date: Sun, 01 Sep 2013 12:08:03 +0000
To: public-audio@w3.org
Message-ID: <bug-23037-5429-qbNSjlVWBf@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23037

--- Comment #13 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> ---
(In reply to comment #12)
> 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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 1 September 2013 12:08:05 UTC

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