hello,
i read this afternoon :
however: pd is a graphical programming language with one simple paradigma: if you have the plot/image of a pd-patch and you make a patch, that looks exactly the same, the patch *has* to work exactly the same way. this of course is not true if you rely on the order of cord-creation.
in fact I don't really understand cos there's somethings not clear in my mind. I was told by a friend, experimented user of Max/msp that when you create a patch, there are some 'hidden' rules : example: if a bang is connected to 2 objects, the most at right receive the bang first (it can be very important for an init) or : if this objects are centered, the most on the bottom receive the bang first (same problem) and : the date of creation of a link (inlet->outlet) can also say which object receive the info first between 2. (::everything is from my memory %}
I'd like to know if there are some rules like this I missed in the Pd-doc, and in general I'd like to know if there is a doc giving simple optimization advices (like 1 loadbang to multiple bang is better than multiple loadbang (which is the first ??)) .. and tricks like that to make my video/hypernav project going faster.
i realize my questions are not really clear, but I'm sure there is somewhere anybody who experimented PD in optimization problems.
Sebal>
the correct answer to all of these questions is:
if order is important, use a trigger. otherwise, order is undefined.
so, in the loadbang example, if you need to know the order of the bangs coming out of a loadbang, then you would use one loadbang and a trigger.
the only rule regarding order is that unless otherwise documented, in an object with multiple outlets, the outlets will be triggered right-to-left (as in a trigger).
similarly, objects with multiple inlets are normally designed such that the pin on the left is the "hot" pin, and should be triggered last.
pix.
On Fri, 11 Jul 2003 17:38:15 +0200 nicolas.sevaux@tremplin-utc.net wrote:
hello,
i read this afternoon :
however: pd is a graphical programming language with one simple paradigma: if you have the plot/image of a pd-patch and you make a patch, that looks exactly the same, the patch *has* to work exactly the same way. this of course is not true if you rely on the order of cord-creation.
in fact I don't really understand cos there's somethings not clear in my mind. I was told by a friend, experimented user of Max/msp that when you create a patch, there are some 'hidden' rules : example: if a bang is connected to 2 objects, the most at right receive the bang first (it can be very important for an init) or : if this objects are centered, the most on the bottom receive the bang first (same problem) and : the date of creation of a link (inlet->outlet) can also say which object receive the info first between 2. (::everything is from my memory %}
I'd like to know if there are some rules like this I missed in the Pd-doc, and in general I'd like to know if there is a doc giving simple optimization advices (like 1 loadbang to multiple bang is better than multiple loadbang (which is the first ??)) .. and tricks like that to make my video/hypernav project going faster.
i realize my questions are not really clear, but I'm sure there is somewhere anybody who experimented PD in optimization problems.
Sebal>
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
nicolas.sevaux@tremplin-utc.net wrote:
hello,
in fact I don't really understand cos there's somethings not clear in my mind. I was told by a friend, experimented user of Max/msp that when you create a patch, there are some 'hidden' rules :
as you have pointed out, your friend is an "experimented user of Max/msp". in pd things are similar to max, but nevertheless different. the placement of objects does not mean anything with respect to execution order. the only rule, and it is not "hidden", is, that behaviour (time of execution) is undefined when multiple cords are connected to one outlet. the only time, the placement of object has a meaning, is when creating [inlet]s and [outlet]s.
the rest has been answered by pix.
mfg.as.dr IOhannes