1. First steps in Reaktor Core - Native Instruments

�
��
���� �
�� ��
72 – REAKTOR CORE
������
�� ��
��
�����
�� ��
Even when it appears that the relative order of read and write operations is
irrelevant, it doesn’t hurt to impose a particular order, and it’s a little bit
safer.
The relative order of write operations is important. The relative order of
read operations does not matter, as long as their order relative to the
write operations remains defined.
OBC connections are not compatible with normal signal connections.
Furthermore, OBC connections corresponding to different types of objects
(for example, different floating point precision of memory storage)
are not compatible with each other. Pins of incompatible types cannot
be connected; for example, you cannot connect a normal signal output
to an OBC input.
4.3. Initialization
As we are starting to work with objects that have an internal state (in case of
Read and Write, the shared memory of the objects is their internal state), it
becomes important to understand what the initial state of the structure you’ve
built is. For example if we are going to read a value from memory (using a
Read module) before anything is written to it, what value will be read? And,
if we don’t like the default value, how can we change it?
Those questions are addressed by the initialization mechanism of Reaktor Core.
The initialization of core structures is performed in the following way:
- first, all state elements are initialized to some default values, usually
zeroes. Particularly all shared memory and all output values of the
modules will be set to zeroes, unless explicitly specified otherwise in
the documentation
- second, an initialization event is sent simultaneously from all initialization
sources. The initialization sources include most of the modules
that do not have an input: Const modules (including QuickConsts), core
cell inputs (typically), and some others. The sources would normally
send their initial values during an initialization event; for example,