1. First steps in Reaktor Core - Native Instruments

4.7. Fixing the event shaper
We can now discuss in more detail exactly what’s wrong with the event shaper
module structure we built earlier:
The problem is the initialization event. If you consider how the initialization
of the above structure will happen you’ll notice the following:
- the x input is firing or not firing an initialization event depending on
whether it receives an initialization event from the outside, primarylevel
structure (that is the initialization event rule for core-cell event
inputs)
- the constants 4 and 0.25 are always firing an initialization event
Thus, in case for whatever reason the initialization event does not occur at
the input of the shaper, the output of the shaper will still receive the event
from the last multiplier and will forward that event to the outside primary
level structure.
Although for control signal processing purposes, that might be OK (in case of a
missing input initialization event, the input is considered zero, and the output
initialization event is still fired), it is not exactly what one would intuitively expect
from an event processing module. A more intuitive behavior would be for
the module to send an output event only in response to an incoming event.
So, the problem is that our two constant modules may be sending events at
a wrong time (that is when there’s no input event). As a solution, we suggest
replacing the subtraction and multiplication modules, which have constants
at their inputs, with their Modulation counterparts.
The Modulation macros is a group of modules in the Reaktor Core library found
under Expert Macro > Modulation:
84 – REAKTOR CORE