Damian Stewart wrote:
what's the order of execution for signal~ objects that output messages (eg
which will get printed first?
It's undefined, unless you define it with subpatches with signal cords
between them (which don't need to carry meaningful data, just the
presence of a signal connection is enough to force order):
if this diagram makes any sense at all:
env~ -- print 1
env~ -- print 2
this is documented somewhere, i think in a flanger example...
Pd-l...@iem.at mailing list
UNSUBSCRIBE and account-management ->http://lists.puredata.info/listinfo/pd-list