jstrecker's picture

Yep! If you share your composition in the gallery, we'll post the export there (time permitting, as I mentioned above). We've already exported Star Glow by @Scratchpole and Shadertoy compositions by @Bodysoulspirit.

kingluma's picture

That sounds great. And once you have exported them, will we receive a copy of our own exported comps (as FxPlug, etc.) ?

Scratchpole's picture
@Scratchpole posted a new Discussion, “vid2vid (style transfer)
useful design's picture

Hi Jaymie (@jstrecker) when I simply replicate a vuo file the same as yours (Make Color Layer patch only) I don't get the bug.

But when I'm working on sub compositions used in my own Vuo files I consistently have this problem. See screenshot. Attached a sub-composition for you to examine. Try creating an output called acceleration. Not possible for me, Vuo will always append the lowest number not used by another output port already. Even if I delete all the output ports first.

microlomaniac's picture

Thanks, I'll try that.

How about using wildcards like ? and *? So a String without wildcards would be handled as "exact match", but one could then easily filter out controls that begin with a certain String (Button*) or end with it (*n 13) or, for a partial match: *partialmatch*


keep the partial match behaviour but make it an exact match when entered in quotes, i.e. Button 1 vs. "Button 1"

jstrecker's picture

Workaround: Instead of Filter Control or Filter and Scale Control, you can use Get Control Values -> Are Equal, as in the attached composition.

I agree that it should be more obvious how to do an exact match instead of a partial match on the control name. Would people still want to do a partial match sometimes? That would affect our implementation.

jstrecker's picture

I haven't been able to reproduce this. Alastair (@usefuldesign), did I miss any steps?

Start with subcomposition with published ports:

Delete a published input port

Add a published input port of the same name back in:

jstrecker's picture

@DRDN, I'm glad you were able to find and delete the problematic node. If you still have the node, could you attach it to this bug report so we can figure out why Vuo crashed? In fact, it would help even more if you could provide all of the nodes you had installed, in case the problem involves multiple nodes.

(We tried turning this Flashes composition into a subcomposition but couldn't reproduce the problem.)

@Kewl, thanks for the suggestion about AppCleaner. It seems like a useful tool in general, although in this case AppCleaner missed the folders where the problematic node would have been installed (either User Modules or System Modules). We looked into how the Vuo app could inform AppCleaner about those locations and, not finding any documentation, have asked the developers.

Bodysoulspirit's picture

Okay Jaymie this is AMAZING ;)
Thrilled to see you managed to add an icon image as well as live preview in the gallery preferences ! Very well done !

I noticed they get exported with this plugin generic icon instead of the default OS X screensaver icon but cmd-i on the file and just deleted the icon there and it automatically uses the default screensaver icon so really really cool.

Using KIK's plasma as my screensaver now and already shared ;)



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.