Re: Missing information in the Web Audio spec

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?

I agree that checking for cycles on every connect() could be a performance
killer. Depending on how the author constructs the graph, it could make
graph construction an O(N^2) operation.

[Of course I agree with you that MSP's solution is a good one :-).]


>
>  Do AudioBuffers created on one AudioContext work with other AudioContexts?
>> This needs to be specified.
>>
>
> I agree, can you enter this into <https://www.w3.org/2011/**
> audio/track/issues/new <https://www.w3.org/2011/audio/track/issues/new>>?


Filed ISSUE-77.

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]