1. First steps in Reaktor Core - Native Instruments

In this version, the 0 output of the Router is disconnected; therefore, the Router
works as a gate, letting the events through only if it’s in the ‘true’ state. The
inverted value then arrives at the second input of the Merge, thus overriding
the non-inverted value, which is always arriving at the first input. If the router
is in ‘false’ state the inverter doesn’t receive an event and doesn’t send an
event to the second input of the Merge; therefore, the original unmodified
signal goes to the output of the Merge.
The branches are most often merged with a Merge module. But theoretically
speaking you could use many other modules (for example, arithmetic
modules like adder, multiplier, and so on) instead.
Routers treat the initialization event just like any other event. Therefore,
one could filter out the initialization event by using routers, thereby
ensuring that the initialization event won’t appear in particular areas
of the structure.
6.2. Building a signal clipper
Let’s build a Reaktor Core macro structure that would clip the incoming audio
signal from the top at a specified level:
If the input signal is not greater than the threshold it will be routed to output
0 of the Router and, through the Merge, to the output of the structure.
Otherwise, the signal will be routed to output 1, where it triggers the latch,
sending the threshold value to the Merge instead. The same thing happens
during initialization.
Note that this structure will not change its output in response to changes
to the threshold. Rather the new threshold value will be used for the
next and all subsequent events at the signal input. This is in a way
similar to a modulation macro’s behavior, where modulator changes do
not result in output events.
REAKTOR CORE – 107