1. First steps in Reaktor Core - Native Instruments

In the picture above we can see changes of the output of our adder occurring
during the time from 0 to 7 ms. At the moment in time that the output changes
its value, it generates an event. An event means that the output reports a
change of its state, meaning that it has got a new value.
In the following example, the upper left module has changed its output value
from 2 to 4, generating an event. In response, the adder module will change
its output value and generate an event at its output, too.
�
����
��
58 – REAKTOR CORE
��
����
Alternatively, the upper left module could have generated a new event with the
same value as the old one. The adder would have still responded by generating
a new event, but this time, without changing its output value.
�
����
��
��
����
The new value appearing at the output is not required to be different
from the old one. However, the only way an output can change its value
is by generating an event.
As you have seen from the previous examples, an event occurring at an output
of some module will be sensed by downstream modules, which would in
turn produce further events (remember the adder producing an output event
in response to an incoming event). Those new events would be sensed by
the modules connected to the corresponding outputs and propagated further
downstream, until the propagation stops for one of the reasons discussed
later in this text.
Events in Reaktor Core are not the same as events on the Reaktor
primary level. They behave according to different rules, which will be
explained below.