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

Re: [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:29:54 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/143/24244495@github.com>
> [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:
Received on Wednesday, 11 September 2013 14:30:29 UTC

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