Hello people, hello devvvvs,
Having to do with dynamic modular systems I found something missing in vvvv features that conceptually is really simple and i think it would be usefull in many patching scenarios.
the problem comes if you want to concatenate multiple spreads into one(like the Cons (Spreads)node does) having the possibility to choose dynamically the input spreads (having them also dislocated in different modules).
i’m using network to avoid this vvvv limit:
you just send data via UDP from different modules.
you send them to local host, same port.
UDP receiver must be set to spread.
in this way you concatenate the incoming data from the local network in a unique spread.
the issue of this approach:
- you introduce delays by using network
- you are not sure that data are combined in the same frame (right?).
- you can’t really decide the order in wich the input spreads are concatened.
a couple of new nodes! :)
there would be a ConsS node with these inputs:
- input (where you put data to be concatenated)
- priority (integer that gives the priority for concatenation order, like it works on Group (EX9 Priority)node)
- send string (the target where to send)(like in S (Spreads) node)
then there could be a ConsR node with the input:
- receive string
and the output:
- bin size (eventually)
using these two nodes combined you could concatenate different input spreads choosing also the order of the concatenation using the priority pins.
Priority works exactly like in groups, lower to higher…
What do you think about this? :)
I found it’s really a nice example of a more general concept regarding vvvv itself:
the conncetions between nodes are just one way to see the actual structure of the data flow. It offers the nice possibility to SEE the graphical rappresentation of the node chains, but it also brings to a static structure.
Would be nice to be able to create this kind of “meta structures” (meta operators) wich can’t not be entirely represented in the vvvv patch GUI, but for this reason they can expand possibilities avoiding GUI limits.
In a way you could represent these objects in different vvvv interfaces, like the Finder;
take the S-R nodes: as far as i understand they create “metaconnections”, not visualized in the patch but that can be displayed in a different graphical interpretation of the system like the Finder window.
i really think it’s an interesting topic to explore.
…and staying also on the practical side, these nodes can really make the difference in a scenario where you load dinamically different modules.
let me know what you think and if there’s something missing in my perspective.