[PD] Dynamically created signal object bug
Enrique Erne
enrique at netpd.org
Tue Feb 24 08:49:40 CET 2009
hi luke
yep i know this problem, i think it's called "updating the dsp-tree".
one workaround, i used to do, is to create a +~ and delete it again.
faster is to turn off the dsp while doing dynamic patching stuff and
then turn it back on again, but then you should keep track of [r
pd]->[route dsp]
btw i have written an abstractions to dynamically chain abstractions
together (sound weird doesn't it?). i got it finally working and i'm
just about to write some example and little documentation before posting
a preview release on the list.
cheers eni
Luke Iannini wrote:
> Hi all,
> Here's another bug I've just managed to boil down and reproduce. I'm
> kind of surprised at this one - I thought it was a pretty common thing
> to dynamically spawn signal objects.
>
> The bug is: a dynamically spawned abstraction containing signal
> objects won't start processing/generating audio until you either
> delete an object in the parent patch or connect two signal objects
> together.
>
> As usual this is tested on Pd-e 0.40.3 and Pd 0.42-4...
>
> Can anyone confirm?
> Thanks!
> Luke
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
More information about the Pd-list
mailing list