2 nodes: a send super cable and a receive super cable.

The role of the super cable is to allow the user to use a unique variable name: "foobar" so that all downstream "foobar" variables automatically connect together. Similar to spooky send and receive but an exact replication as opposed to connecting cables and then hiding. Very useful for use in subcompositions when you want to allow copies of nodes to access same data.

Obviously the super cable has to know not to connect 2 cables to 1 input- so only outputs can stream to multiple inputs. User would be warned not to proceed- (like feedback warning)

QC equivalent: 

Kineme Spooky Send/Receive

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●●○○ — A few weeks of work

Comments

there are definitely

useful design's picture
Submitted by

there are definitely situations where you want to have multiple sender nodes sharing a channel using momentary pulses to send for example hit interrupts to other instances or iterations of a sub composition. speaking from experience in QC using Spooky patches.

I suppose @Alastair that that

alexmitchellmus's picture
Submitted by

I suppose Alastair (@usefuldesign) that that implementation would work with a "Fire Event" however I don't think it would work with values. I think that it would work programmatically with values- however I suppose there would be no way to work out from our end when the variable was being updated.

I think Steve (@smokris) is the best to comment - If it can be done he will let us know! But great addition Alastair (@usefuldesign)! I hope that gets put into this request if possible.

If the node is "generic" enabled then I suppose that if it was in "Fire Event" type then it could be allowed to spawn multiple instances.

Can't you use lists and make

MartinusMagneson's picture
Submitted by

Can't you use lists and make a "multiplex" node? It will be with cables, but it should be a "cleaner" option for now. Make a new node with an "add to list" node, publish as many inputs you need/want, and publish the list output. Then make a deplex node to pick out the values and insert it in the nodes you need the data.

(I get the idea by the way, Reaktor Core uses something like that and it is convenient).

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

Votes

1 vote so far!

Who voted?

alexmitchellmus's picture