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

Re: Behavior of source nodes on connect/disconnect

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 13 Sep 2013 03:34:37 -0700
Message-ID: <CAOp6jLZKKrTzQY3tAuS4r3sVDUfre75gds8Dr6e8dmOiBfTiwQ@mail.gmail.com>
To: Karl Tomlinson <karlt+public-audio@karlt.net>
Cc: Katelyn Gadd <kg@luminance.org>, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, Chris Wilson <cwilso@google.com>, Raymond Toy <rtoy@google.com>, "public-audio@w3.org" <public-audio@w3.org>
On Fri, Sep 13, 2013 at 2:48 AM, Karl Tomlinson <
karlt+public-audio@karlt.net> wrote:

> "audioprocess events are only dispatched if the ScriptProcessorNode has at
> least one input or one output connected."

I stand corrected!

K. Gadd writes:
> > Doesn't that mean that ScriptProcessorNode can be used to observe GCs
> > (measure how long it's been since the last onAudioProcess occurred on a
> > disconnected ScriptProcessorNode)?
> the answer to this is still yes.
> If an AudioNode connected to the ScriptProcessorNode is deleted
> because it has no references, then the ScriptProcessNode will stop
> firing onaudioprocess at the time when the connected node is deleted.

I don't think so. In this case, the observable behavior that must be
preserved is that the AudioNode is connected and the ScriptProcessorNode
keeps dispatching onaudioprocess. Automatic removal of the AudioNode can
only be done insofar as we preserve that observable behavior. In other
words, the onaudioprocess event must keep firing.

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Friday, 13 September 2013 10:35:04 UTC

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