1. First steps in Reaktor Core - Native Instruments

6. Conditional processing
6.1. Event routing
Events in Reaktor Core do not always have to travel along the same predefined
paths. It is possible to dynamically change these paths. You can achieve this
by using the Router module (Built-In Module > Flow > Router):
The Router module accepts events at its signal input (bottom) and routes them
to either its output 1 (top) or its output 0 (bottom). The routing, i.e. whether
the event goes to output 1 or output 2, depends on the current state of the
Router, which is controlled from the Ctl input (top)
The Ctl input accepts a connection of a new type, which is not compatible with
either normal signals or OBC connections. It is a BoolCtl (Boolean control)
signal type. The BoolCtl signal can be in one of two states: true or false (on
or off, 1 or 0). If the control signal is in the true state the events are routed
to output 1. If the control signal is in the false state the events are routed to
output 0.
The control signals have a significant difference from normal signals in
Reaktor Core: they do not transmit events and therefore cannot trigger
any processing by their own.
To control a Router you obviously need a control signal source, the most
common of which is the Comparison module found under Built-In Module >
Flow > Compare:
This module performs a comparison of the two incoming signals and outputs
the result as a BoolCtl signal. The upper input is assumed to be on the left of
the comparison sign and the lower input, on the right. So a module reading
‘>’ produces a true control signal if the value at the upper input is greater
than the value at the lower input.
You can change the comparison criterion in the properties of the module:
REAKTOR CORE – 105