jstrecker's picture

Joe, thanks for reporting. Added to the list of known graphics bugs.

cwilms-loyalist's picture
Chris commented on savienojums's Feature Request, “Face detection

Could this node also have a “faces detected” output? That way it can be used to trigger another event to happen when faces are detected.

Bodysoulspirit's picture
Bodysoulspirit commented on howie's Discussion, “Pubblish ports in exported apps

With Vuo 2.0 around the corner, it will include checkboxes & sliders, so it will be possible to use those as "Input Parameters" for exported apps too.
Right now you can already create your own checkboxes & sliders, but it takes more nodes VS the upcoming stock nodes for them (see joined composition Slider + Checkbox).

For text boxes, they're still marked as "chosen to be implemented", but not for the first Vuo 2.x. version.
You can also somehow make your own ones, but they really take quite a big amount of nodes, and need the custom Paradox nodes to be installed (link) (put the custom downloaded node from Github in your User Module Folder you can access from the Vuo editor Menubar > Tools > Open User Modules Folder & Relaunch Vuo) because the current Vuo version needs layer names for layers to be clickable (Vuo 2.0 will fix that if I'm right so it will already lower the amount of nodes needed).
(See joined composition Text Boxes)

And as said, since we cannot yet hide/close windows, right now you can show/hide the UI or parameters using a keyboard key (command key used in bot joined compositions).

jersmi's picture
jersmi commented on jersmi's Discussion, “Math question

Nice to see that work. Much appreciated, Jean Marie. If you have a public source for the formula, I'd love to have a look. Might have some clues for manipulating transformations like this.

jstrecker's picture
Jaymie commented on lhepner's Bug Report, “OSX Crashing Vuo Composition Loader

Confirmed — same bug.

Bodysoulspirit's picture

Will this be supported in exported screensavers too (by clicking options in the screensaver preference panel), or should I create a separate Feature Request ?

Bodysoulspirit's picture
Bodysoulspirit commented on howie's Discussion, “Pubblish ports in exported apps

Yes, looking forward to it too, and in exported screensavers too.

Yes, OSC is a way to go, one can also create a separate Vuo window for the controls by duplicating "Render __ to Window", but to be able to hide windows or closing them, we'll need : Nodes for showing/hiding windows, and to enable the window's close button

With Kineme the team built upon QC, here, they built it from the ground, still pretty young software, so features are added over time, still missing some features, but already totally loving Vuo fro what it offers ;)

howie's picture
howie commented on howie's Discussion, “Pubblish ports in exported apps

Thanks for those links, the 2nd one is what i was hoping for but without the need to store values. Basically a separate UI window that is automatically generated from the published inputs when you export to an app. This was a feature or QuartzBuilder, the kineme app that built apps from QC comps and i was expecting vuo apps to have the same functionality. It really does add a lot to the usefulness of being able to create separate apps, i guess for now i'll look using OSC to intract with app. Cheers Howie



Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion

Browse Feature Requests

Suggest a Feature

Browse the Composition Gallery

Share a Composition

How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.