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~.