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. Rob -- 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