useful design's picture

Alastair (@usefuldesign)


  • Vuo Founder


2 years ago
useful design's picture

I gave up on this because positioning each of the eight elements was taking about 5 minutes each and it did my head in. And if I find the last one doesn't have room I have to move them all over again one by one. It's just so frustrating, @teamVuo.

QC has dials for adjusting number inputs (which can be replaced with an Input Splitter with a set range if desired but not compelled to use). Vuo has decided to put range bars with a very small pixel range for adjusting these standard input values. As if nobody would ever care about any kind of precision.

Using the slider is impossible to get the accuracy I need. Using the up and down arrows are too big in the jumps. If there were some modifier keys for making the up and down arrows move in smaller and larger increments or if it was possible to adjust the standard increment in preferences there would be other ways to do this. As it is it's insanely problematic and not the first time I've thought so and given up using Vuo for a project. I'm forced to manually keep trying numbers (trial and error) and unlike the standard macOS interface default that "enter" updates the number with the typed input but keeps the highlight on that input it "Tabs" to the next one. So I have to enter a number and then tab forward then "shift" + "tab" back to enter another number, over and over and over again. It's a bit dispiriting for a designer trying to line up a few objects visually.

Most of my PNG file sizes are the same so I should be able to give them all the same position and they sit in place but that isn't working for me either, and in any case sometimes you need quick and precise manual adjustments in visual design without the frustration of typing in 30 values until you get the right one.

In QC you can grab the adjustment dial for an input and drag the cursor away from the dial half a screen length and then get very tiny increments per 10 pixels of movement of the cursor, like a wretch with a very long arm. THere's no way to do this in Vuo and this is not the first time I've given up using it for some UI frustration.

useful design's picture

I was trying something similar to the first but I hadn't noticed the Replace Opacity input until I saw iron your screenshot set to False. Now it's working, thanks Joe. I like the second method better, didn't think to use a mask, obvious now you show me!

useful design's picture

Fetch 8 white/clear images and apply a colour to each of them…easiest way?

I have a really simple composition in QC that loads 8 images (.ai files which I have to export as .png files to use in Vuo) and have colour wells for all the images and I rotate one of the images according to a simple random generation algorithm. Vuo's Make Image Layer node doesn't have a colour input like the QC Billboard patch. Looking for something equivalent to sprite/billboard with colour tinting of image function.

useful design's picture
Alastair commented on Bodysoulspirit's Discussion, “Vuo redesign - Nodes

I realise the look of Vuo 2.0 is probably locked down now. But I'm going to make one more plea for consideration to the idea that Vuo shift input ports to inside the node and put the value print outs after the port label, the exact same way Origami Studio does. Drawers and extremely long values like font names could still be hung of the node (or make it optional).

My reasons are twofold: aesthetics/ease of visually parsing the general composition and optimal use of screen "realestate" or a more functional use of space.

When double clicking node inputs (or tabbing through them) to edit the value the input could pop out on the left or on the right of the label. I also prefer the node corner radius used in Origami Studio, and more generally, it is more functional and more sophisticated and professional looking than Vuo 2.0. Just copy it as much as possible, it copied QC after all… it works.

useful design's picture
Alastair commented on Philip's Feature Request, “Nodes to convert from Text to most other types

I think Vuo needs a scripting node, JS, Lua, Python or something like that. Makes data and state machine stuff so much less hassle.