Scrollable Port Popups

Often I use the port popup (click one port) to get information, for example a path or some text etc.

Problem is the preview often is too short and I end up using a Console Window :(

Could it not just be but scrollable ? Like preview 3 lines instead of one and scroll the rest if more ?

For example here below if the url was way larger I could horizontal scroll it, if it had several lines (tree) I could vertical scroll it :

I know there are also these yellow notepad like popups that sometimes come up (haven't understand when they do and when they not) and that display more info already, which is great, but a longer one could still require scroll.

Plus A - I think the port popup looks better then the yellow pad and B - we have port popups + yellow popups = 2 popups. And C - The port popups can be floated which can be great too sometimes.

Of course I assume popovers are rendered only when opened so I guess that would not affect the editor performance.

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

Ability to collapse other nodes besides type converters

As suggested by @Philip on Only collapse type converters that were added automatically, this could be useful for:

  • Other nodes that have one input only (including lists)? For example, Add, Multiply, Spint Off Event/Value...
  • Nodes where only one input is being sent data? For example, Get Item from List where the List port gets sent data, but Which is entered manually...

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

A UI for storing and loading the state of running compositions

[Original title: PATCHbANK facility for compositions… like an eighties synth memory pretty much.]

This request involves having a facility for saving and recalling composition states at various special nodes in the composition (or if possible already with all Nodes then that would make it less work for users removing the need to put PATCHbANK nodes around the composition to capture and recall data states).

I got a decent way into the process of setting this up in QC as a QC tool that could broadcast to other compositions. I divided it up into a MVC kind of setup and wrote separate compositions for each of this 'trinity' of parts. The PATCHbANK patches that were to go in your comp talked to a separate Controller composition (see image) sending state data while also passing it through, and when receiving Patches recalled messages, changing the data to those messaged data states.

Never brought the whole thing together because the Controller became a monster time sink, it was kind of like a very miniature VDMX sort of thing I realised, with the advantage that generative states could also be recalled (not just published values), like a image you had painted Live using your mouse and composition effects for example.

The main motivation was that even with a single composition without changing patches but just modulating a whole bunch of input port values one could easily generate dozens of different looks for the one composition. Saving a file for each state seemed like a bit much, and if you improved the composition at all, even one new noodle, then you'd have to manually transpose all your saved patches to the new version. I much prefered the old Roland analogue synth (Jupiters and Junos) set up with a digital memory where you just hit a unit number (sometimes preceded by a Bank number to change patch) and to write a patch you just hit write and then the Bank and Unit keys.

I set this up so you could even use a midi music keyboard to change patches or write them, Black keys for BAnk, White keys for Unit. Hence the odd arrangement of buttons on the draft UI.

Anyhow if it's of interest longer term to VUO please raid the memory bank. I have a semi-working QC app of the controller part, but it doesn't actually talk to the the PATCHbANK nodes that do the work in your composition. I got the PATCHbANK inline Patches working also, with simple save to plist and recall but just as proof of concept for each data type including structures and images.

Will tidy and post a demo comp for the feelz.

Screenshots, Mockups, and Videos: 

Component: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Related: A UI for storing and editing published input port values.

The current feature request would store not just published input port values but all input port values and node states. It would be like pausing a composition and resuming it later.

Better cable-highlighting

A node has been selected in a composition. Here's an image that includes two cables connected to the selected node. Can you distinguish the two cables from the rest? How about at a glance?

I have a particularly busy composition and I'm understandably finding it difficult to tell which cables are connected to which nodes. I'm spending a lot of time tinting and un-tinting nodes, as well as moving them around, just to highlight where they send, and from where they receive, events and data. I really think this is an area where the editor can be better.

Right now, selected cables are darker than unselected cables. Cables connected to a selected node are less dark, but still darker than cables that are just hanging about. With regard to how to make a highlight or selection more obvious, I can only suggest something like a prominent shadow, to make it pop out of the otherwise 2D canvas design. (Modifying the thickness would obscure the distinction between data+event and event-only cables, and brightness/colour modification is already implemented and isn't optimal on its own. I'm not sure what else to suggest.)

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

Option to edit subcomposition without affecting other instances

As suggested by @Alastair on Ability to create composition-local subcompositions...

Currently, when you make changes within a subcomposition, the changes apply everywhere the subcomposition is used (every instance of the subcomposition as a node in a composition).

This feature request is to add the option to edit an individual subcomposition instance without affecting others, and without future changes to others affecting it.


There's a bunch of situations I'd use that in. Personal Text Layer nodes where I want to use something I've got already got going but then tweak it inside a bit to do something else, like round off or smooth a number value input that's irrelevant to the original sub-comp/macro I copied it off because it doesnt have a separate numeric value input...

Thinking that through some more, you might want that library or 'node class' kind of subcomp to be universal, either local comp constrained or global for all Vuo comps that user has, and the way they drag it onto the graph determines if it's local or global in scope. Holding "Option" key while dragging from the Node Library or hitting "Enter" key while selected in the Node Library makes it global for instance.

Clicking Period Key while cursor is over a 'node class' subcomp devolves it into a simple macro environment with no implications on other instances when it's changed inside. And vise-versa dumping any internal changes when returning to an existing node class.

Would need some kind of subtle UI indication of scope i.e. itself/local-composition/global.

Square corners ⇒ isolated; round corner ⇒ local sub-comp; chamfered corner ⇒ universal sub-comp.

QC equivalent: 

macros

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Pages

Subscribe to RSS - Vuo Composition Building/Editing