>I recommend doing this only in subpatches, with<br>
>individual block~ objects, rather than for huge sections of your patch.<br>
<br>
Unfortunately, as I said, the signal feedback loop occurs on the top
layer of the program- I tried writing a delay line with the minimum
length as an abstraction and completing the system loop with that, but
Pd won't allow it, so therefore the top layer (and I'm guessing all the
ones below it) needs to be blocksize 1. Effectively my whole program!<br>Anyway, I'll give it a try it before slating it further.<br>K<br><br><div><span class="gmail_quote">On 1/30/07, <b class="gmail_sendername">Derek Holzer
</b> <<a href="mailto:derek@umatic.nl">derek@umatic.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi again,,<br>
<br>Kim Taylor wrote:<br> > It means the layer with the system topology needs to have its sampling<br> > block forced to 1. Mightn't this affect performance? especially for a<br> > large program?<br><br>Of course it will affect the performance, because a blocksize 1 is very
<br>heavy on the CPU. I recommend doing this only in subpatches, with<br>individual block~ objects, rather than for huge sections of your patch.<br>Either your methods with delays, or a send/receive pair in that same<br>subpatch (that's how I would do it personally), will give the same
<br>result. Perhaps the send/receive pair has slightly less overhead, but I<br>couldn't tell you for sure.<br><br> > That is the best way? Hm, I'm surprised!<br><br>The best way yes, but that doesn't mean it's nice. Welcome to the
<br>wonderful[ly warped] world of PD ;-)<br>d.<br><br>--<br>derek holzer ::: <a href="http://www.umatic.nl">http://www.umatic.nl</a><br>---Oblique Strategy # 125:<br>"Only a part, not the whole"<br></blockquote>
</div><br>