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

[web-audio-api] (AudioNodeReferences): AudioNode context and upstream/downstream references (#73)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:07 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/73@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17330](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17330) Tue, 05 Jun 2012 11:22:07 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/73
Received on Wednesday, 11 September 2013 14:29:54 UTC

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