> Good point. Liveness shouldn't depend on GC. We'd better say that only explicit disconnect() calls make the node non-live. .. but won't that mean AudioBuffers associated with ConvolverNodes that are in "fire and forget" signal paths will be immutable forever? -Kumar On 1 Aug, 2013, at 7:25 AM, "Robert O'Callahan" <robert@ocallahan.org> wrote: > On Thu, Aug 1, 2013 at 1:51 PM, Srikumar Karaikudi Subramanian <srikumarks@gmail.com> wrote: > 2. It may be clearer to make it explicit that an AudioBuffer can be "associated with" multiple AudioNodes, some of which may be live and some not and that the AudioBuffer is to be immutable as long as at least one of these AudioNodes is live. The current "associated with" language reads close to one-to-one association. > > 3. There is some residual nondeterminism with the ConvolverNode's liveness being tied to its connect()/disconnect() calls. If a convolver node is part of a voice's effect chain, it can be released without an explicit disconnect() call and at a time that is not predictable due to reverb tails and "dynamic lifetime". Not sure if this needs fixing or can be fixed, but just pointing it out. > > Good point. Liveness shouldn't depend on GC. We'd better say that only explicit disconnect() calls make the node non-live. > > 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 Thursday, 1 August 2013 03:39:49 UTC