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

Re: Behavior of source nodes on connect/disconnect

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Sat, 14 Sep 2013 07:38:41 +0300
Message-ID: <CAJhzemXReMON4a+JsjAVrkYe5JRP3_-x312drTyr7=SpB-TvsA@mail.gmail.com>
To: Chris Wilson <cwilso@google.com>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, Jer Noble <jer.noble@apple.com>, Raymond Toy <rtoy@google.com>, "public-audio@w3.org" <public-audio@w3.org>
On Sat, Sep 14, 2013 at 12:08 AM, Chris Wilson <cwilso@google.com> wrote:

> On Fri, Sep 13, 2013 at 1:52 PM, Jussi Kalliokoski <
> jussi.kalliokoski@gmail.com> wrote:
>
>> While I do acknowledge that it is tedious to have to connect analyzer
>> nodes to the DestinationNode (IIRC I was one of the people pushing for
>> AnalyzerNode to not have this requirement), I don't think alleviating that
>> pain point (that can be solved by, well, connecting to the DestinationNode)
>> is worth the cost.
>>
>
> Um.  AnalyserNodes DON'T have to be connected to the destination - cf "*Note
> that this output may be left unconnected."* in
> https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#AnalyserNode-section.
>
>

That's what I'm saying I pushed for and we got:
http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0010.html

Cheers,
Jussi


>
>
Received on Saturday, 14 September 2013 04:39:08 UTC

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