Custom nodes and collections
Build reusable blocks, open their internal graphs and share .vltnode files.
Package a graph
Select processing nodes and create a custom node. Wires crossing the boundary become named ports. The group needs an outgoing connection; Input, Output and Interface are not packed inside.
Double-click to open a custom node. Editing the definition updates its instances; Make independent creates a separate type. Exporting .vltnode includes nested definitions and node positions.
Oversampling
Choose 1×, 2× or 4× for the internal graph. 2×/4× is useful for nonlinear processing and creates an explicit sample-rate boundary. Return to 1× before expanding the node.
Oversampled graphs and Map/Reduce bodies support elementary nodes. Built-in Effects, Reverb and C++ Function are not allowed in these bodies; Function and Buffer cannot cross a rate boundary.
Array, List, Map and Reduce
Array has a fixed length; List changes length within Capacity. Get/Set use zero-based indices. Editing nodes return a new collection; History retains the result between samples.
A Map subgraph requires inputs with IDs item:Number and index:Integer, and one Number output. Reduce additionally requires accumulator:Number. These IDs matter. The body is created with the node; double-click or choose Open node to edit it. This is not a Function wire.
Graph limits
The current format supports up to 512 nodes and 2048 connections after expansion, eight nesting levels, 16 ports per custom-node side, collections up to 4096 elements and 16 MiB of prepared DSP storage.