1. First steps in Reaktor Core - Native Instruments

the other output receives no events (in particular, that means the value of the
other output cannot change).
The Router is controlled by a BoolCtl type of input connection. On the other
side of the connection you would typically have a Compare module (sometimes
a few intermediate modules like BoolCtl macro ports can be placed between
the Compare and the Router).
By using Routers you can dynamically enable or disable evaluations in parts
of your structure.
Typically, after splitting the signal path in two using a Router, you would merge
the two branches using a Merge or other module. Often you would merge a
branch with the original, unsplit signal. But generally you are free to do whatever
you want there (be careful with performance issues though).
B.5. Latching
Latching is probably the most common technique in Reaktor Core. It means
using Latch modules to prevent events from being sent at the wrong time.
For example you wouldn’t want a control signal event to trigger a computation
in an audio loop.
Alternatively you can use macros from the Expert Macros > Modulation group,
which are basically a set of the most typical combinations of Latches with
arithmetic processing modules.
B.6. Clocking
Clocks are sources of events. The clock events typically occur at regular time
intervals corresponding to the clock rate. You normally need clocks to drive
various modules, such as oscillators, filters, and so on. Most of the implementations
of such modules do not require an explicit clock connection from the
outside, but implicitly use a standard clock source available in core structures.
That source is the sample rate clock, which runs at the default audio rate.
Note that in event core cells, although the connection to the sample rate clock
is available, the clock signal itself is not available. Therefore most oscillators,
filters, and similar modules will not run in event core cells.
146 – REAKTOR CORE