Re: Missing information in the Web Audio spec

On Thu, May 17, 2012 at 8:32 AM, Chris Rogers <crogers@google.com> wrote:

> On Wed, May 16, 2012 at 1:25 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>
>> On Thu, May 17, 2012 at 3:19 AM, Philip Jägenstedt <philipj@opera.com>wrote:
>>
>>> If circular routing is not to be allowed, I quite like the solution in
>>> MSP, to consider that graph blocked. To require throwing an error
>>> synchronously would require checking for loops on every operation :(
>>
>>
>> This example:
>> var node = (new webkitAudioContext()).createGainNode();
>> node.connect(node);
>> doesn't throw in Chrome dev. Chris, how does Webkit handle cycles?
>>
>
> They are allowed.  It's common in audio processing graphs to have delays
> with feedback and they are commonly used in musical audio production.  As a
> simple example, consider a delay with a low-pass filter in the feedback
> loop which would be something like the beloved "Echoplex" tape delay:
> http://en.wikipedia.org/wiki/Echoplex
>

Ah, thanks, I should have remembered that. Then resolving ISSUE-24 will
require specification of a processing model that handles cycles. I would
like resolving that to be quite high priority as it will have significant
impact on the architecture of any implementation.

Rob
-- 
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]