Routing data

vvvv beta question
1

i need to ‘wrap up’ several bits of data to be able to route them through one node to other modules.

as an example i refer to the Svvvvitcher by tonfilm where he ‘wraps up’ control data in the GUI, routes it to other patches, then ‘unwraps it’.

i (just about) understand how the data is ‘unwrapped’ through the use of slices etc. but i cannot work out how to ‘wrap up’ data.

i attach a patch which shows what i would like to do.
i have a bpm value, a pause button and a reset button.
i would like all 3 values to be routed through one node.

thanks in advance.

routing1.v4p (9.7 kB)

2

I think you should have a look at the Vector nodes, both join and split versions.

also Stallone and Cons could help you out

3

thankyou very much. i just needed a prod in the right direction.
i now understand Stallone and Cons.

i have used Cons (spread) to solve my problem.

i attach a patch for anyone who follows in my footsteps.

4

thankyou very much. i just needed a prod in the right direction.
i now understand Stallone and Cons.

i have used Cons (spread) to solve my problem.

i attach a patch for anyone who follows in my footsteps.

routing_fixed.v4p (11.3 kB)

5

Hi, I would recommend vector 3d instead, because its easier to patch, faster and its better spreadable. Be aware that vector is intertweening values. See patch for example. Other good nodes to check about spreading is SwapDim, getslice (with binsize, little different than getspread), vector2d and vector4d, setslice, CAR and CDR.

6

Hi, I would recommend vector 3d instead, because its easier to patch, faster and its better spreadable. Be aware that vector is intertweening values. See patch for example. Other good nodes to check about spreading is SwapDim, getslice (with binsize, little different than getspread), vector2d and vector4d, setslice, CAR and CDR.

routing_fixed2.v4p (22.9 kB)
routing_fixed3.v4p (34.7 kB)

7

thanks frank.

…erm… makes sense, but gonna stick with simple for the time being.

8

on second thoughts…

i will go the vector route. it’s still simple but leaves room for expansion.

thanks