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

Re: Behavior of source nodes on connect/disconnect

From: Raymond Toy <rtoy@google.com>
Date: Fri, 13 Sep 2013 16:29:11 -0700
Message-ID: <CAE3TgXHCCXDZGzyK1uPpsYhfv96U8stFK3O8nD0MBuSySZkg8A@mail.gmail.com>
To: Jer Noble <jer.noble@apple.com>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, Chris Wilson <cwilso@google.com>, "public-audio@w3.org" <public-audio@w3.org>
On Fri, Sep 13, 2013 at 4:23 PM, Jer Noble <jer.noble@apple.com> wrote:

> On Sep 13, 2013, at 4:16 PM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> On Fri, Sep 13, 2013 at 1:50 PM, Jer Noble <jer.noble@apple.com> wrote:
>> Of course, HTMLMediaElements must pause when they are removed from the
>> DOM.  So in the general case, disconnecting a playing media element and
>> throwing away all references to it will allow it to be GCd.
> But you can call play() on a media element after removing it from the DOM.
> If we were to follow the media element model in Web Audio, we would
> introduce per-node pause() and resume() APIs and specify that when you
> disconnect the last output of a node, there is an implicit pause() call.
> I’d actually be fine with that.
> One further hypothetical: should “pause” and “play” traverse down the
> graph?  I.e., if you “pause” a ConvolutionNode, would the
> AudioBufferSourceNode feeding it pause as well.

In a pull operation model, wouldn't pausing the ConvolverNode stop pulling
on the AudioBufferSourceNode, impllicitly pausing it as well?  But I guess
if there is a ScriptProcessorNode in between, you'd have to do something.

And what exactly are we saying a paused node would output? Nothing?

> -Jer
Received on Friday, 13 September 2013 23:29:38 UTC

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