Italian

Patches can not only use native nodes, but also nodes that come with external files. The best example for a node that comes with an external file is a patch that you created and saved to disk. A patch is a node. Check the Root to see it.

But not only patches are nodes. Also effects, modules, plugins and more. See vvvvs application folder to see all the different node types.

The Challenge

A patch using external nodes should still open correctly

• after moving the patch
• on different systems

But you still want the flexibility to organise all

• addons from Contributions,
• your own addons and place them whereever you want on your system.
• your projects in a project folder holding all of the projects patches and addons
• different vvvversions without having to collect and copy all addons from one version and "install them" in the next version.

Usage

Now when when all nodes now are spreaded all over your system it will occur that vvvv can't find it. But there are nice ways to fix that:

When a node could not be found it turns red which says it is a dummy. Now hover over the red node to check in which file vvvv was expecting to find it, search the node on your system and just drag it on any open patch. VVVVV now knows that node and replaces all red dummy nodes that represented that missing node. After saving your patches the problem is solved forever.

However if you have many red nodes you should think about adding a search path:

• open the Root by hitting Alt-r
• enter the directory where you put the contributions that you downloaded
• enter the directory of all the addons that you want to use independant of the project you are working on
• if there is no slot left configure the Cons (String) in a way that you can enter even more strings (open Inspektor, select Cons, increase Input Count...)

You see that you can configure your system in any way you want. The NodeList (VVVV) will collect all the nodes found in these directories on startup and make them available through the node browser.

How it Works

From beta25 on each patch stores the information where to find each node. Typically this is a relative path or a path beginning with %VVVV%, standing for vvvv's application directory.

So independant of the search pathes each patch should open correctly when those external nodes can be found at the same place. That way you can download a contribution to your desktop and just open a help file to a new node. The new node is found since it is referenced relatively.

If something goes wrong either drag the file into vvvv or specify a new search path.
VVVV will then search the node via its name, category and version.

To reduce dummy nodes and encourage you to spread your nodes over your system in a way it feels right for you, here are the tricks we use when the path to a referenced node in a patch is wrong:

Search pathes are either

• specified through NodeList (VVVV)
• anytime a patch is opened its location is added to the list of available search pathes

The meaning of a specific search path FOLDER

• FOLDER is searched for any module, effect or plugin
• when there is a folder named
• FOLDER\effects, it (and its subfolders) will be searched for effects
• FOLDER\modules, it will be searched for modules recursively
• FOLDER\plugins, it will be searched for plugins recursively
• for all these added folders a file watcher additionaly checks for added nodes and turns dummy nodes into real ones as soon the node becomes available via adding the file to the folder.

Your own nodes

For making your own nodes like modules, effects or plugins we recommend to create a folder outside vvvv's application folder and name it "my addons". For project specific addons just put clone them into your project folder.

The Patch file

<NODE systemname="Camera (Transform Softimage)"
filename="%VVVV%\modules\vvvv group\Transform\Camera (Transform Softimage).v4p"
nodename="Camera (Transform Softimage)"
componentmode="Hidden" id="0">
</NODE>

• filename is for referenceing the file either relatively or via %VVVV%
• systemname is the full name of the node with category and version
• nodename is only to be able to open the patch with older vvvversions

Test it

• temporarily move the root.v4p outof vvvv's app dir
• start vvvv
• try to create a module, effect or plugin. It should not be available.
• open your project. It should still work
• open the moved root.v4p and all modules, effects and plugins should be availbable again