1. First steps in Reaktor Core - Native Instruments
1. First steps in Reaktor Core - Native Instruments
1. First steps in Reaktor Core - Native Instruments
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Some types of process<strong>in</strong>g, mix<strong>in</strong>g for example, make sense for both<br />
audio and control types of signals. In those cases, you will f<strong>in</strong>d versions<br />
of such macros dedicated to process<strong>in</strong>g audio and versions dedicated to<br />
process<strong>in</strong>g control signals. For example, there are audio mixers and control<br />
mixers, audio amplifiers and control amplifiers, and so on. Generally<br />
it’s not a very good idea to misuse a module to process signals of types<br />
it was not <strong>in</strong>tended for, unless you really know what you’re do<strong>in</strong>g.<br />
Hav<strong>in</strong>g said that, quite often it’s possible to use audio signals for control<br />
purposes. The most common example would be to modulate an oscillator’s<br />
frequency or a filter’s cutoff by an audio signal. That is absolutely<br />
OK because you are <strong>in</strong>tend<strong>in</strong>g to use an audio signal as a control signal.<br />
We assume that the opposite case, <strong>in</strong> which you really mean to use a<br />
control signal as an audio signal, would be pretty rare.<br />
The separation between audio, control, event, and logic signals is not to<br />
be confused with event/audio separation on the <strong>Reaktor</strong> primary level. The<br />
primary-level event/audio classification refers to speed of process<strong>in</strong>g, audio<br />
signals be<strong>in</strong>g processed faster and requir<strong>in</strong>g more CPU. Also as you probably<br />
know, primary-level event signals have different propagation rules than audio<br />
signals. The difference between audio, control, and event signals <strong>in</strong> <strong>Reaktor</strong><br />
<strong>Core</strong> term<strong>in</strong>ology is purely semantic, def<strong>in</strong><strong>in</strong>g the mean<strong>in</strong>g of the signal rather<br />
than the type of process<strong>in</strong>g. There is not a one-to-one relationship between<br />
primary-level event/audio and <strong>Reaktor</strong> <strong>Core</strong> audio/control/event/logic terms,<br />
but we can still try to expla<strong>in</strong> their relationship:<br />
- a primary-level audio signal normally corresponds to either a <strong>Reaktor</strong><br />
<strong>Core</strong> audio signal (for example, an output of an oscillator or an audio<br />
filter) or a <strong>Reaktor</strong> <strong>Core</strong> control signal (for example, an output of an<br />
envelope).<br />
- a primary-level event signal is typically a control signal <strong>in</strong> terms of<br />
<strong>Reaktor</strong> <strong>Core</strong>. An example of such signal would be an output of an<br />
LFO, a knob, or a MIDI pitch or velocity source.<br />
- sometimes a primary-level event signal corresponds to a <strong>Reaktor</strong> <strong>Core</strong><br />
event signal. The most typical example of that is a MIDI gate (<strong>Reaktor</strong><br />
<strong>Core</strong> event signals will be described later, as we promised).<br />
- sometimes a primary event signal resembles a <strong>Reaktor</strong> <strong>Core</strong> logic<br />
signal; however, they are not fully compatible, and there must be<br />
explicit conversion between them (a topic that also will be covered<br />
later). Examples <strong>in</strong>clude signals processed by Logic AND or similar<br />
primary-level modules.<br />
REAKTOR CORE – 37