Re: [PD] pd message order?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-08-04 00:06, Jonathan Wilkes wrote: Technically it seems to be this: they output in reverse creation order. (The last [receive] you created in the patch will output first.) Conceptually, imagine an evil demon changing the order in real-time to screw up your patch. Thwart the demon by using wired connections, trigger, and subpatches to define order. Only use multiple [receive]s when message order doesn't matter. (Same with multiple wires fanning out to various objects from an outlet.) exactement. that's what i teach my students: don't ever use [receive] if you _might_ depend on execution order. and then there is iemgut's [oreceive] (which stands for Ordered RECEIVE), where you can specify a priority, so you have control over execution order (it's also in Gem known as [gemreceive]) fgamsdrI IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk46S8MACgkQkX2Xpv6ydvT9awCgjDVu45SzeOe4LmCLuxH/0wZ/ tPwAnRqSqA9xg0XtBBgZyFZOeq3lFpN0 =l9+8 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pd message order?
I sometimes just get the receive as the master receive, and then channel it down in sub receives that are numbered, and I use trigger. something like [r a] | [t f f] | | | [s a1] | [s a2] and then a1 goes to where it first needs to be sent to. it doesnt look confusing in the code cheers ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pd message order?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-08-04 16:08, Alexandre Torres Porres wrote: I sometimes just get the receive as the master receive, and then channel it down in sub receives that are numbered, and I use trigger. something like [r a] | [t f f] | | | [s a1] | [s a2] and then a1 goes to where it first needs to be sent to. but why do you use [s a] in the first place then? wouldn't it be way simpler to replace [s a] by | [t a a] | | [s a2] [s a1] ? fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk46r3YACgkQkX2Xpv6ydvThqACgs4aGcQRUYUhxIcaUbkk8F+ub Mo4An3GoklLPbAkIrKGEKzEkU7KQvg7j =uUoD -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pd message order?
so standard objects have right to left ordering of outlet processing, but what about send and receive for messages? if multiple objects receive for the same name, which one gets it first? is there a triggerlike object for messages, or should I send multiple messages each with a differentiated tag like s bla1, s bla2, s s bla3 even when I send the same message? There is a way to sync data from multiple receives and it is to use the [buddy] object. [buddy] waits until it has received data at each inlet and then outputs everything it received through the corresponding outlet in the standard right-to-left order. It might not be a good solution in all cases since the receive objects need to be in the same patch window as the [buddy], but I have used it successfully for synchronizing receives within subpatches. [buddy] is in pd-extended, but I do not believe it is in pd vanilla. Hope this helps, Michael ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] pd message order?
so standard objects have right to left ordering of outlet processing, but what about send and receive for messages? if multiple objects receive for the same name, which one gets it first? is there a triggerlike object for messages, or should I send multiple messages each with a differentiated tag like s bla1, s bla2, s s bla3 even when I send the same message? ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pd message order?
IIRC they'll appear in the order the objects were created. To be clear I would use a trigger to explicitly order and send to destinations with different (and meaningful names) In this case the name is best chosen to reflect the intended action, rather than the source. Hope that makes sense. a. On Wed, 3 Aug 2011 23:16:38 +0200 Ludwig Maes ludwig.m...@gmail.com wrote: so standard objects have right to left ordering of outlet processing, but what about send and receive for messages? if multiple objects receive for the same name, which one gets it first? is there a triggerlike object for messages, or should I send multiple messages each with a differentiated tag like s bla1, s bla2, s s bla3 even when I send the same message? -- Andy Farnell padawa...@obiwannabe.co.uk ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pd message order?
Technically it seems to be this: they output in reverse creation order. (The last [receive] you created in the patch will output first.) Conceptually, imagine an evil demon changing the order in real-time to screw up your patch. Thwart the demon by using wired connections, trigger, and subpatches to define order. Only use multiple [receive]s when message order doesn't matter. (Same with multiple wires fanning out to various objects from an outlet.) -Jonathan From: Ludwig Maes ludwig.m...@gmail.com To: Pd List pd-list@iem.at Sent: Wednesday, August 3, 2011 5:16 PM Subject: [PD] pd message order? so standard objects have right to left ordering of outlet processing, but what about send and receive for messages? if multiple objects receive for the same name, which one gets it first? is there a triggerlike object for messages, or should I send multiple messages each with a differentiated tag like s bla1, s bla2, s s bla3 even when I send the same message? ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
