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

[Bug 17795] Behavior of multiple connections to same node needs to be explicitly defined

From: <bugzilla@jessica.w3.org>
Date: Mon, 30 Jul 2012 21:42:03 +0000
Message-Id: <E1Svxj1-0001Tf-VQ@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795

--- Comment #8 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-30 21:42:03 UTC ---
(In reply to comment #7)
> Think about this in the real world - what does it mean if I plug my guitar into
> my guitar amp with a cable - then plug it in *again* to the exact same amp
> input with another different cable!

Presumably it's just like plugging in another guitar which happens to be
producing the same output as the first one.

> I'm quite certain developers won't be
> confused by this, because I think it's an anomaly and doing nothing will be
> exactly what they expect.

The real world doesn't have code modularity and first-class node objects that
can be passed around and shared through arbitrary control and data flow. I
suspect in the real world you don't shout "here's the output of my guitar, do
what you want with it" and throw a lead over to someone on the other side of a
crowded room you haven't ever met (who then shares it with several of her
friends).

We're not building guitars and amps, we're building software APIs. These APIs
will be used by thousands of people who have never plugged a guitar into an
amp. They will not limit themselves to using Web Audio to simulate "real world"
artifacts.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 30 July 2012 21:42:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 July 2012 21:42:05 GMT