W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Audio-ISSUE-32 (AudioNodeReferences): AudioNode context and upstream/downstream references [Web Audio API]

From: Philip Jägenstedt <philipj@opera.com>
Date: Fri, 01 Jun 2012 15:19:17 +0200
To: public-audio@w3.org, "Audio Working Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.we77afg9sr6mfa@kirk>
On Tue, 15 May 2012 15:46:20 +0200, Audio Working Group Issue Tracker  
<sysbot+tracker@w3.org> wrote:

> Audio-ISSUE-32 (AudioNodeReferences): AudioNode context and  
> upstream/downstream references [Web Audio API]
> http://www.w3.org/2011/audio/track/issues/32
> Raised by: Philip Jägenstedt
> On product: Web Audio API
> The AudioNode interface includes a reference to the creating context,  
> but not to the connected inputs and outputs. This seems like an odd  
> choice, since the context will typically be easy to find (there's  
> usually only one) but walking the filter graph is very hard and  
> currently requires building a wrapping implementation.
> Suggestion:
> Drop context, numberOfInputs and numberOfOutputs. Knowing the number of  
> inputs/outputs is by itself not very useful.
> Possibly, we could expose an Array-like object for access to the inputs  
> and outputs, but only if the use cases are strong.

Chris replied in a note:

"My belief is that it's not *that hard* to keep track of these  
relationships with quite simple wrapper code. After all, most people don't  
really care about "walking the graph", and those who know what this means  
can certainly track this state easily themselves. We can change it if most  
people think this is the way to go, but I don't recommend it since I think  
it adds more complexity than is necessary."

We would be fine with not introducing arrays of connected nodes, at least  
until Web authors complain about having to wrap AudioNodes all the time.  
However, our suggestion to drop context, numberOfInputs and numberOfOutput  
stands, but overlaps with ISSUE-103. (Of course, if there are use cases,  
we'd be interested to learn about them.)

Philip Jägenstedt
Core Developer
Opera Software
Received on Friday, 1 June 2012 13:22:14 UTC

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