This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17330 - (AudioNodeReferences): AudioNode context and upstream/downstream references
Summary: (AudioNodeReferences): AudioNode context and upstream/downstream references
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:22 UTC by Philip Jägenstedt
Modified: 2014-10-28 17:17 UTC (History)
3 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2012-06-05 11:22:07 UTC
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.
Comment 1 Olivier Thereaux 2012-06-07 15:58:13 UTC
Comment from Chris Rogers, 18 May 2012

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.
Comment 2 Marcus Geelnard (Opera) 2012-06-12 13:08:26 UTC
Additional comment from Philip Jägenstedt, http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0488.html

"
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.)
"
Comment 3 Olivier Thereaux 2014-10-28 17:14:43 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 4 Olivier Thereaux 2014-10-28 17:17:41 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.