clone
container.clone
An array of nodes that are processed simultaneously
Parameters
| ID | Range | Default | Description |
| NumClones | 1.00 - 1.01 | 1.00 | The number of active clones. |
| SplitSignal | 0.00 - 2.00 | 2.00 | The process mode for the signal |
There are a lot of DSP concepts that require some sort of duplication of certain elements, for example:
- Additive synthesis
- Unisono synthesiser voices
- Cascading filters
- Feedback delay networks
- Multistage effects (phasers, etc)
which are usually implemented by duplicating a certain part of the signal path. In scriptnode you can implement them naively by copy & pasting the required nodes and connect all parameters manually. However this is super tedious and you don't have the ability to dynamically change the amount of duplicates without getting into complicated hacks.
The container.clone node offers a quick and intuitive way to implement those DSP applications. It's supposed to be populated with nodes that can be duplicated. There are a few requirements for the child nodes:
- They must have the same structure (hence the name clone )
- They immediate child node must be a container (this is required for the C++ code generation)
- They cannot have any modulation / parameter connections to anywhere outside of the clone (as well as with each other).
- Their parameters (and complex data) will be synced.
There are a few convenient functions available in the toolbar of this node:
- delete all clones so that there is only one child
- duplicate the first clone to an arbitrary amount
- hide the clones - you don't want to see 128 oscillators...
The clone node has two parameters: NumClones and SplitSignal . NumClones will define the number of active clones and will always have the parameter range 1 ... number child nodes . The second parameter will determine how the signal will be processed and can have three values:
| Value | Description | Typical application |
| Serial | processes the clones serially (just like a container.chain). | multistage fx, cascaded filters |
| Split | processes the clones in parallel without the signal input and adds their output to the signal | any form of synthesis (that doesn't require audio input) |
| Copy | Copies the input signal and processes each clone, then adds their output to the signal | feedback delay networks |
The default mode is the copy mode, however you can save a few CPU cycles for synthesis applications if you switch to the Split mode.
The synchronisation of all clone parameters results in a severe limitation: For almost every real world use case you will need to change certain parameters of the cloned nodes. An additive synthesiser for example will need to use a different frequencies and amplitudes for representing each harmonic, a unisono saw needs to be detuned and spread across the stereo field etc.
This is where the two nodes control.clone_cable and control.clone_pack come in handy as they allow to send different parameter values to each clone.
For a detailed explanation of these nodes take a look here and here.