Load nodes from composition path and other custom folders

So I just downloaded an example composition from the Composition Gallery which included a .vuonode file alongside the .vuo file. However in order to run this, I have to move the .vuonode file inside my user library folder.

It would be great if vuo would automatically load up any .vuonode files contained within the current composition’s directory to avoid having to do this, especially considering after viewing this example, I’d probably want to delete the node that I’d just installed into my Library anyway.

As a secondary thought, it would be amazing if there was a user settable location where Vuo would also load up nodes from. This way a user could sync their node custom library across multiple machines via Dropbox.

I’ve opened this feature request for community voting.

I’d vote if I had any.

i have votes now but there’s so many great feature requests now!

if when opening the composition with in-built nodes would be good to get a dialogue asking if user desires that the nodes be copied to her User Nodes folder automatically for future use. With checkboxes for ‘set my response as default’ and ‘don’t show this dialogue again’.

As a secondary thought, it would be amazing if there was a user settable location where Vuo would also load up nodes from. This way a user could sync their node custom library across multiple machines via Dropbox.

@DiGiTaLFX (or anyone else who’d like to customize the location where modules are installed) — would this solve your problem?

  • Place your Vuo Modules in your Dropbox folder.
  • Delete ~/Library/Application Support/Vuo/Modules
  • Open Terminal and create a symbolic link so that ~/Library/Application Support/Vuo/Modules redirects to your Dropbox subfolder.
  • Launch Vuo.

This procedure was quick to get working, and will work in the next release. Since it requires using Terminal it’s not the most user-friendly solution. But before spending more time on it (making a Preferences dialog or whatnot), I wanted to check with y’all to see if that was important to you or if there are other things you’d prefer we spend our time on.

1 Like

More of a question than an answer @jstrecker, but in the past when I’ve tried to organise sub comps inside the …/Modules folders by putting sub comps in a second layer of folders (organised say by author or project) I’ve found they don’t load. If you have a symbolic link working I’m wondering if you’ve changed something to allow Vuo to land comps from sub-folders in the …/Modules folders?

No, the change involving symlinks didn’t affect the (in)ability to load modules from subfolders.

Added support for loading subcompositions and custom nodes from a local folder. Implemented in Vuo 2.0 beta.

Oh, now that’s nice. :)