The information in this document is subject to change without notice and does
not represent a commitment on the part of Native Instruments Software Synthesis
GmbH. The software described by this document is subject to a License Agreement
and may not be copied to other media. No part of this publication may be copied,
reproduced or otherwise transmitted or recorded, for any purpose, without prior
written permission by Native Instruments Software Synthesis GmbH. All product
and company names are trademarks of their respective owners.
And also, if you’re reading this, it means you bought the software rather than stole
it. It’s because of people like you that we can continue to create great tools and
update them. So, thank you very much.
REAKTOR, REAKTOR 5 and REAKTOR CORE are a trademarks of
Native Instruments Software Synthesis.
Germany USA
Native Instruments GmbH Native Instruments USA, Inc.
Schlesische Str. 28 5631 A Hollywood Boulevard
D-10997 Berlin Los Angeles, CA 90028
Germany USA
info@native-instruments.de info@native-instruments.com
www.native-instruments.de www.native-instruments.com
Table of Contents
1. First steps in Reaktor Core ..................................................................... 11
1.1. What is Reaktor Core ...............................................................11
1.2. Using core cells .......................................................................12
1.3. Using core cells in a real example ..............................................15
1.4. Basic editing of core cells .........................................................17
2. Getting into Reaktor Core ......................................................................22
2.1. Event and audio core cells ....................................................... 22
2.2. Creating your first core cell .......................................................24
2.3. Audio and control signals ........................................................ 36
2.4. Building your first Reaktor Core macros ..................................... 42
2.5. Using audio as control signal ....................................................49
Index ......................................................................................................209
X – REAKTOR CORE
1. First steps in Reaktor Core
1.1. What is Reaktor Core
Reaktor Core is a new level of functionality within Reaktor with a new and
different set of features. Because there is also an older level of functionality,
we will hereinafter refer to these two levels as the core level and the primary level, respectively. Also when we say “primary-level structure” we will mean the
structure of an instrument or macro, but not the structure of an ensemble.
The features of Reaktor Core are not directly compatible with those of the
primary level, so some interfacing is required between them, and that comes
in the form of core cells. Core cells exist inside primary-level structures, and
they look similar and behave similarly to primary-level built-in modules. Here
is an example structure, using a HighShelf EQ core cell, which differs from
the primary-level built-in module version in that it has frequency and boost
controls:
Inside of core cells are Reaktor Core structures. Those provide an efficient way
to implement custom low-level DSP functionality as well as to build larger-scale
signal-processing structures using such functionality. We will take a detailed
look at these structures later.
Although one of the main purposes of Reaktor Core is to build low level DSP
structures, it is not limited to that. For users with little DSP programming
experience, we have provided a library of pre-built modules, which you can
connect inside core structures, just as you do with ordinary modules and
macros in primary-level structures. We have also provided you with a library
of pre-built core cells, which are immediately available for you to use in primary-level structures.
In the future, Native Instruments will put less emphasis on creating
new primary-level modules. Instead, we will use our new Reaktor Core
technology and provide them in the form of core cells. For example,
you will already find a set of new filters, envelopes, effects, and so on
in the core cell library.
REAKTOR CORE – 11
1.2. Using core cells
The core cell library can be accessed from primary-level structures by rightclicking on the background and using the Core Cell submenu:
As you can see, there are all different kinds of core cells; they can be used
in the same way as primary-level built-in modules.
An important limitation of core cells is that you are not allowed to use
them inside event loops. Any event loop occurring through a core cell
will be blocked by Reaktor.
You can also insert core cells that are not in the library. To do that, use the
Load… command from the Core Cell menu:
12 – REAKTOR CORE
You may also want to save core cells you’ve created or modified, so that you
can load them into other structures. To save a core cell, right-click on it and
select Save Core Cell As:
Rather than using the Load… command, you can have your core cells ap-
pear in the menu by putting them into the Core Cells subdirectory of your
user library folder. Better still, you can further organize them into subgroups.
Here’s an example:
REAKTOR CORE – 13
“My Documents\Reaktor 5” is the user library folder in this example. On your
computer there may be a different path, depending on the choice you’ve made
during installation and any changes you’ve made in Reaktor’s preferences.
Inside the user library folder there’s a folder named “Core Cells”. (Create it
manually if it doesn’t exist.)
Inside the Core Cells folder, notice the folder structure consisting of the Ef-fects, Filters, and Oscillators folders. Inside those folders are core cell files
that will be displayed in the user part of the Core Cell menu:
The menu contents are scanned once during Reaktor startup, so after
putting new files into these folders, you should restart Reaktor.
Empty folders are not displayed in the menu; a folder must contain
some files to be displayed.
Under no circumstances should you put your own files into the system
library. The system library may be changed or even completely replaced
when installing updates, in which case your files will be lost. The user
library is the right place for any content that is not included in the
software itself.
14 – REAKTOR CORE
1.3. Using core cells in a real example
Here we are going to take a Reaktor instrument built using only primary-level
modules and modify it by putting in a few core cells. In the Core Tutorial Examples folder in your Reaktor installation, find the One Osc.ens ensemble
and open it. This ensemble consists of only one instrument, which has the
internal structure shown:
As you can see this is a very simple subtractive synthesizer consisting of one
oscillator, one filter and one envelope. We are going to replace the oscillator
with a different, more powerful one. Right-click on the background and select
Core Cell > Oscillator > MultiWave Osc:
The most important feature of this oscillator is that it simultaneously provides
different analog waveforms that are locked in phase. We are going to replace
the Sawtooth oscillator with the MultiWave Osc and use a mix of its waveforms
instead of a single sawtooth waveform. Fortunately, there’s already a mixer
macro available from Insert Macro > Classic Modular > 02 - Mixer Amp > Mixer – Simple – Mono:
REAKTOR CORE – 15
Connect the mixer and the oscillator together and use their combination to
replace the sawtooth oscillator:
Switch to the panel view. Now you can use the four faders of the mixer to
vary the waveform mix.
Let’s do one more modification to the instrument and add a Reaktor Core-based
chorus effect. We say Reaktor Core based, because although the chorus itself
is built as a core cell, the part containing panel controls for this chorus is still
built using the primary-level features. That’s because at this time Reaktor
Core structures cannot have their own control panels – the panels have to be
built on the primary level.
Select Insert Macro > Building Blocks > Effects > SE-IV Chorus and insert it
after the Voice Combiner module:
If you look inside the chorus you can see the chorus core cell and the panel
controls:
16 – REAKTOR CORE
1.4. Basic editing of core cells
Now we are about to learn a few things about editing core cells. We are going to start with something simple: modifying an existing core cell to your
particular needs.
First, double-click the MultiWave Osc to go inside:
Inputs Normal Outputs
What you see now is a Reaktor Core structure. The three areas separated by
vertical lines are for three different kinds of modules: inputs (on the left),
outputs (on the right), and normal modules (center).
Whereas normal modules can move in all directions, the inputs and outputs
can only be moved vertically, and their relative order matches the order in
which they appear outside. So, you can easily rearrange their outside order by
moving them around. Try moving the FM input below the PW input:
REAKTOR CORE – 17
You can double-click the background now to ascend to the outside, primarylevel structure and see the changed port order:
Now go back to the core level and restore the original port order:
As you have probably already noticed, if you move modules around, the three
areas of the core structure automatically grow to accommodate all modules
inside them. However, they do not automatically shrink, which can lead to
these areas sometimes becoming unnecessarily large:
18 – REAKTOR CORE
You can shrink them back by right-clicking on the background and selecting
Compact Board command:
Now that we have learned to move the things around and rearrange the port
order of a core cell, let’s try a few more options.
For a core cell that has audio outputs it’s possible to switch the type of its
inputs between audio and event (a more detailed explanation can be found
later in this manual). In the above example, we used a MultiWave Osc module,
all of whose inputs and outputs are audio. However, in this example we don’t
really need them as audio, because the only thing connected to the oscillator
is a pitch knob. Wouldn’t it be more CPU efficient to have at least some of
the ports set to event type? The obvious answer is, “yes, it would.” Here’s
how to do that.
Changing both P and PM inputs to event mode should produce the largest
CPU improvement. To do that double-click on the P port module to open its
properties window:
Double-click here
Switch the properties window to the function page, if necessary, by clicking
on the tab. You should now see the Signal Mode property:
REAKTOR CORE – 19
Change it to event. Note how the large dot at the left of the input module
changes from black to red indicating that the input is now in event mode (it’s
more easily visible after you deselect the port – just click elsewhere):
The dot turns red
Now click on the PM input to select it, and change it to event mode, too. If
you want, you can change the two remaining inputs to event mode as well.
Finally, double-click the structure background to return to the primary level
and observe that the port colors have changed to red and the CPU usage has
gone down.
Sometimes it doesn’t make sense to switch a port from one type to another.
For example, it doesn’t make sense to switch an input that receives a real
audio signal (meaning real audio, not just an audio-rate control signal like an
envelope) to an event rate. In some cases such switching could even ruin the
functionality of the module. Going in the other direction, it doesn’t make sense
to change an event input that is really event sensitive, such as an envelope’s
event trigger input (for example, gate inputs of Reaktor primary-level envelopes).
If you change such an input to audio, it will no longer work correctly.
In addition to cases in which port-type switching obviously does not make sense
there may be cases in which it does make sense, but in which the modules
will not work correctly if you switch their port types. Such cases are quite
special, although they can also result from mistakes in the implementation
20 – REAKTOR CORE
or design of the module. Generally, port-type switching should work; hence
the following switching rule:
In a well designed core cell, an audio-rate control input can typically
be switched to event mode without any problem. An event input can
be switched to audio only if it doesn’t have a trigger (or other eventsensitive) function.
Another way to save CPU is to disconnect the outputs that you don’t need,
thereby deactivating unused parts of the Reaktor Core structure. You have to
do that from inside the structure – outside connections do not have any effect
on deactivating the core structure elements.
Suppose in our example we decide that we only need the sawtooth and pulse
outputs. We can lower the CPU usage by going inside the MultiWave Osc and
disconnecting the unused outputs. Disconnecting is simple in Reaktor Core,
you click on the input port of the connection, drag the mouse to the any empty
part of the background and release it. For example, click on the input port of
the Tri output and drag the mouse into empty space on the background.
There’s another way to delete a connection. Click on the wire between the
sine output of the MultiWave Osc and Sin output of the core cell, so that it
gets selected (you can tell that it’s selected by its blue color):
Now you can press the Delete key to delete the wire:
After you deleted both wires, the CPU meter should go down a little more.
REAKTOR CORE – 21
If you change your mind, you can reactivate the outputs by clicking on either
the input or the output that you want to reconnect and dragging the mouse to
the other port. For example, click on the Tri output of the MultiWave Osc and
drag to the input of the Tri output module. The connection is back:
Of course, numerous fine-tuning adjustments can be made to core cells. You
will learn about many more options as you proceed through this manual.
2. Getting into Reaktor Core
2.1. Event and audio core cells
Core cells exist in two flavors: Event and Audio. Event core cells can receive
only primary-level event signals at their inputs and produce only primary-level
event signals at their outputs in response to such input events. Audio core
cells can receive both event and audio signals at their inputs but provide only
audio outputs:
FlavorInputsOutputsClock Src
EventEventEventDisabled
AudioEvent/AudioAudioEnabled
Therefore audio cells can implement oscillators, filters, envelopes, effects and
other stuff, while event cells are suitable only for event processing tasks.
The HighShelf EQ and MultiWave Osc modules that you are already familiar
with are examples of audio core cells (you can tell that by the fact that they
have audio outputs):
22 – REAKTOR CORE
And here is an example of an event core cell:
This module is a parabolic shaper for control signals, which can be used to
implement velocity curves or LFO signal shaping, for example.
As previously mentioned, event core cells are restricted to event processing
tasks. Because clock sources are disabled inside them (see the table above),
they cannot generate their own events and, therefore, cannot implement modules such as event-rate LFOs and envelopes. When you need such modules,
we suggest that you take an audio cell and convert its output to event rate
using one of the primary-level audio to event converters:
The above structure uses an audio core cell implementing an ADSR envelope
and converts it to event rate to modulate an oscillator.
REAKTOR CORE – 23
2.2. Creating your first core cell
You create new core cells by right-clicking on the background in a primary-level
structure and selecting Core Cell > New Audio or, for event cells, Core Cell > New Event:
We are going to build a new core cell from scratch inside the same One Osc.ens
you already played with. We will be using the modified version of that ensemble
with the new oscillator and chorus that we built in the last chapter, but if
you didn’t save it don’t worry, you can do the same steps using the original
One Osc.ens.
As you can see, in this ensemble we are modulating the filter at the P input,
which accepts only event signals. We are not using the FM version of the same
filter because it does not perform as well at higher cutoff frequencies, and
because the modulation scale is linear at an FM input, which generally gives
less musical results when modulated by an envelope. (That phenomenon is
typically but incorrectly referred to as “slow envelopes”.):
Because we need to apply the modulation at an event input, we also need
to convert the envelope’s output to an event signal, which we do with an A/E
24 – REAKTOR CORE
converter. As a result, our control rate is pretty low. Of course we could have
used a converter running at a significantly higher rate (and eating up significantly more CPU), but what we are going to do instead is replace this filter
with one which we build as a core cell. Alternatively, we could have taken an
existing filter from the core-cell library, but then we would miss all the fun of
making our first Reaktor Core structure.
We’ll start by creating a new audio core cell. Select Core Cell > New Audio
and an empty audio core cell will appear:
Double-click it to see its structure, which is obviously empty. As you surely remember, the three areas are meant for input, output, and normal modules:
REAKTOR CORE – 25
Attention: we are going to insert our first module into a core structure right
now! Right-click in the normal area to bring up the module creation menu:
The first submenu is called Built-In Module and provides access to the built-
in modules of Reaktor Core, which are generally meant to do really low-level
stuff and will be discussed later.
The second submenu is called Expert Macro and contains macros meant to
be used alongside built-in modules for low-level stuff.
The third submenu, called Standard Macro, is the one we want to use:
26 – REAKTOR CORE
The VCF section could be promising, let’s look inside:
Let’s try Diode Ladder:
Well, maybe that was not the best idea, because a diode ladder might sound
significantly different from the primary-level filter module we are trying to
replace. At minimum, Diode Ladder is a 4-pole (24dB/octave) filter, and the
one we are replacing is a 2-pole filter (12dB/octave). To delete it there are two
options. One is to right-click on the module and select Delete Module:
REAKTOR CORE – 27
The other option is to select the module by clicking on it and pressing the
Delete key.
After deleting the Diode Ladder, insert a 2 Pole SV C filter from the same VCF
section of the Standard Macro submenu:
This is a 2-pole, state-variable filter and is similar to the one we are replacing
(there are some differences, but they are quite subtle). What’s important is
that we can modulate this filter at audio rates.
Obviously, we need some inputs and some outputs for our core cell. To be
exact we need only one output – for the LP signal. To create it right-click in
the outputs area:
28 – REAKTOR CORE
There’s only one kind of module you can create there, so select it. This is
what the structure is going to look like:
Double-click the output module to open the Properties window (if it’s not
already open). Type “LP” in the label field:
Now connect the LP output of the filter to the output module:
Now let’s start with the inputs. The first input will be an audio-signal input.
Right-click in the background of the inputs area and select New > In:
REAKTOR CORE – 29
The input is automatically created with the right type – it’s an audio input,
as you can tell by the large black dot. Rename this input to “In” in the same
way you renamed the output to “LP”, then connect it to the first input of the
filter module:
The second input is a little bit more complicated. As you can see, the second input of the filter Reaktor Core module is labeled “F”. That means frequency,
and if you hold your mouse over that input for a while (make sure the button is active), you’ll see the info text, which says “Cutoff frequency (Hz)”:
As we know, the cutoff of our primary-level filter module is controlled by an
input labeled “P”, and as you can see from the info text, the signal uses a
semitone scale.
We obviously need to convert from semitones to Hz. We can do that either
on the primary level (using the Expon. (F) module) or inside our Reaktor Core
structure. Because we are learning to build Reaktor Core structures, let’s go
for the latter option. Right-click in the background of the normal area and
select Standard Macro > Convert > P2F:
30 – REAKTOR CORE
Loading...
+ 180 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.