It would be nice to be able to render directly to the editor background. That way the logistics of working with multiple windows will be a little less hassle when working with only one screen (less wasted screen estate). Preferrably with a node transparency option. It would also make (video) tutorials a bit easier as the result is displayed directly if screencasting or recording.
An observation ... when creating compositions I find clear layout is crucial. I find myself clumping functional units together, eg: IO section, display section and so on. Then occasionally one want to connect one part with a distant other part which often involves connections passing under nodes and immediately seems to make things messy, especially when the source or destination cannot be seen on the screen at once. This confusion also arises from links connections from the right to the left in a composition, eg: those pesky window request frame connections.
What I think would be "nice" would be a node that acts as a "sink" for data+events and another node that acts as a "source". These would be associated together by an id, or better a name. They could of course be colour coded ... seems to me this could be used to add clarity to larger compositions.
How to load Vuo Image Generator compositions and how to manipulate Vuo's inputs (published ports) from within VDMX
Hi! I’m Jean Marie from Team Vuo. Vuo compositions can be used in other applications. In this tutorial we’ll cover how to use a specific type of Vuo composition, one that conforms to Image Generator protocol, as input to VDMX.
OK, let’s get started. Here I’m using VDMX’s simple mixer template, and I’ve already moved the crossfader all the way to the left, so we are looking at the left screen. I’m going to drag my Vuo composition into a media bin.
It takes moment to compile the first time, but after that it will be available right away.
Origami has a nice feature that when the cursor is hovered over a port or a noodle it inserts some patches like math function mini-patches into the comp and automatically wires them to the port. So if the cursor is over an input port, the output of the inserted patch is wired to it. If the cursor is over an output port, the most relevant input of the inserted patch is wired to the output port of choice. This works for all the patches which Origami has made keyboard single-key [a-z] equivalents (where data types allow for noodle(s) to be created). Both the Origami stand alone app and the QC plugin have this feature.
Would be nice for Vuo to be able to auto-prewire, say math nodes or shared value nodes, into any selected or highlighted wires on the canvas by wiring the input and the output. And for other nodes, where it makes sense and the cursor is hovering over a port, prewire the inserted node to that port. This has the advantage of placing the node in a more relevant location too. If no port is hovered over the node should go wherever the cursor is located on canvas, as it currently does.