[PD] problem with send~ instead of patchcord

IOhannes m zmölnig zmoelnig at iem.at
Tue Sep 13 22:00:07 CEST 2016


On 09/13/2016 08:24 PM, oliver wrote:
> i'm not really sure i implemented everything the right way, but in my
> tests i came to the conclusion, that the send~ object has to be created
> AFTER the corresponding receives~ (regardless of subpatches) to work
> correctly in this setup.
> 
> can you confirm this ?

oh no, please don't do this.
never.
ever.
it's a sure way to call the wrath of the gods upon you.

depending on the creation order is the signal domain equivalent of the
dreaded fan-out in the message domain.
in the message domain use [trigger].
in the signal domain, use connections.

it's quite simple:
if you have two subpatches/abstractions that are connected via a
signal-connection, then the "upper" subpatch will always be evaluated
before the "lower" subpatch; simply because the lower one is waiting for
the upper one to produce data - even if the connection is really just a
dummy one.


gfmrdsa
IOhannes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160913/dec71ee9/attachment.sig>


More information about the Pd-list mailing list