Advertisement
The concept of KoreSounds within a KoreSound is called nesting within
this manual.
Nesting allows two things: On a basic level it provides the possibility to
easily combine not only SingleSounds, but also MultiSounds into a new
MultiSound. This bridges the gap between both types as you don't need
to care which type you are working with (unless you want to change the
inner workings of a KoreSound). On an advanced level, you can create any
signal flow you can think of: Even feedback loops are possible.
With the nesting concept in mind it is also obvious that the top level of
KORE 2 – the Performance, filled with KoreSounds via the B
not very different from a MultiSound. You can, for example, save the
whole Performance as MultiSound (using the F
part of another Performance. The only difference between Performances
and MultiSounds lies in non-structural information: A Performance saves
the global clock's BPM value, for instance, while a MultiSound adapts its
speed to the global value.
Again, the building blocks of KORE 2's sound engine are (from the bottom
to the top of the hierarchy):
►
The Single Sound
►
The Multi Sound
►
The Performance
Except for the Performance, everything on this array of Sounds is
interchangeable and you can recombine it via drag and drop or convert
and save parts of the structure as self-contained KoreSounds.
– is
rowSer
M
) and load it as
ile
enu
KORE 2 – 26
Advertisement
