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

[web-audio-api] Behavior of multiple connections to same node needs to be explicitly defined (#143)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:37 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/143@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17795](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795) Tue, 17 Jul 2012 18:40:12 GMT
> Reported by Chris Wilson
> Assigned to 

I noticed that the spec doesn't say what should happen when you multiply connect() a node to another node, e.g.

nodeA.connect( nodeB );
nodeA.connect( nodeB );

Given the fan-out/sum-in model, it *could* be expected you could have multiple independent connections.  The current Chrome behavior is that the second line above is a no-op; I prefer this behavior, but it needs to be explicitly stated in the AudioNode.connect() description.

Suggested text:

There can only be one connection between a given output of one specific node and a given input of another specific node; multiple connections with the same termini are ignored.  For example, 

nodeA.connect( nodeB );
nodeA.connect( nodeB );

will have the same effect as

nodeA.connect( nodeB );

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:29:04 UTC

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