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

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795#4) by Robert O'Callahan (Mozilla) on W3C Bugzilla. Thu, 19 Jul 2012 16:37:30 GMT

> > Imagine if some module builds an AudioNode A, and then two other modules
> > independently get hold of A and try to play it by connecting it to the
> > DestinationNode. It would be confusing to have one of those operations
> > unexpectedly fail.
> 
> I'm not suggesting at all that it WOULD fail.  It doesn't today - it just
> doesn't create an ADDITIONAL, duplicate connection (thereby doubling the gain,
> which would be just as unpredictable, and IMO less usable.)

Depends on your point of view I guess. In this case I think the author would expect connect() to cause a change in the output, and it won't.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/143#issuecomment-24244495