Thanks guys. I guess this serves as an example of how not to fall into this trap . The explanation you gave is worth the misery I went through chasing this, hopefully one for the archives if someone else hits the same issue.
I wonder, about debug. Is there any useful way of using either -d<n> (--debug) or find-last-error to help tracing these little nasties? In other words can Pd show how it is trying to evaluate the tree? Best, ANdy On Fri, 9 Feb 2007 16:21:00 +0000 padawan12 <[EMAIL PROTECTED]> wrote: > I found this behaviour slightly surprising, but on reflection it makes sense. > Pd doesn't seem to check deeply into subpatches when looking for DSP feedback > loops. > > I started making a simple waveguide synth and decided, for a change, to work > on > the feedback mechanism inside another subpatch. I kept getting DSP loop error > even though the signal path contains a [s~] and unique matching [r~]. Making > the feedback loop require a [send~] and [receive~] in the outermost block > seems > to defeat the use of smaller blocksizes in subpatches. > > Anyone care to comment on this (attached example). Or am I understanding this > incorrectly? > > Cheers. > Andy > _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
