marlon brando

Is it good practice to send all parameters in a poly~ through a big pack/unpack?

1-big-packunpack-for-a-big-poly

Just send all messages prepended with a keyword and retrieve them via route inside the poly~ (that way you also don't have to send tons of messages if there is only one that needs to be sent).

I would rather use route.
Just send all messages prepended with a keyword and retrieve them via route inside the poly~ (that way you also don't have to send tons of messages if there is only one that needs to be sent).

Seconded. More flexible method. Easier to add an internal function: just add a keyword in the [route].

Seconded. More flexible method. Easier to add an internal function: just add a keyword in the [route].
J-F.


yes keywords and route. better for overview, too.

also, it is not a shame to use 3 inlets for 3 logical groups of parameters.

Roman Thilenius wrote on Fri, 19 June 2009 08:52

Roman Thilenius wrote on Fri, 19 June 2009 08:52
yes keywords and route. better for overview, too.

gusanomaxlist wrote on Fri, 19 June 2009 06:49

Do I need to use the set message for more than 1 keyword per prepend?

Like, when sending the notein to poly~, can I prepend midinote,pitch and velocity in one message?

gusanomaxlist wrote on Fri, 19 June 2009 06:49I would rather use route.
Just send all messages prepended with a keyword and retrieve them via route inside the poly~ (that way you also don't have to send tons of messages if there is only one that needs to be sent).

Do I need to use the set message for more than 1 keyword per prepend?
Like, when sending the notein to poly~, can I prepend midinote,pitch and velocity in one message?

you could collect pitch, velocity, duration, etc. into a list, then [prepend] an index for the whole list. Then you route within the poly~ (since route works with lists), unpack it, and send the values where they're needed. I find this better than doing things separately, it makes more sense to me to keep similar sets of parameters together. So as another example, you could have the cutoff, gain, and resonance for a filtergraph~ collected into a similar list... or brightness, contrast, and saturation going into jit.brcosa. [route] is incredibly useful once you start using #1 etc. in abstractions or polys~.

"then [prepend] an index for the whole list"

1 big pack/unpack for a big poly~