[PD] Send and receive execution order was Re: Zen Garden re-implementing the wheel in C++?

Frank Barknecht fbar at footils.org
Sun Apr 18 10:50:28 CEST 2010

On Sat, Apr 17, 2010 at 08:53:12PM +0200, Matteo Sisti Sette wrote:
> Now the subpatch trick (btw thank you for pointing me to the
> documentation resources about it) doesn't help at all for [send~]
> and [receive~] does it? I mean it's applicable but if you can
> arrange the send and receive into subpatches that you have to
> connect physically, then you don't need the s~ and r~ in the first
> place...

If you only have a s~/r~ in your subpatch, then indeed you should
probably not use them anyway. But very often you have more stuff
happening, so you can sort larger parts of your alorithm. 

As Tim wrote, the problem comes from Pd being a Max-like,
two-dimensional programming language, where order can be ambigous,
unless you employ one of the sorting mechanisms built into Pd. It's the
same for messages, that's why I always keep telling newbies to use more
[trigger] objects. It may come as a surprise that it also affects
signals, but it's a closely related issue. Think of the patchcord as
Pd's DSP way to say [t b a].


More information about the Pd-list mailing list