Advertisement
Custom u
P
, however, are always part of the KoreSound, they are
Ser
ageS
not saved with the Ensemble or its snapshots. They can only be re-loaded
if the KoreSound is loaded – re-assembling the sound by subsequently
loading Reaktor, the Ensemble and the snapshot won't recall any u
Ser
P
.
age
As mentioned above, the REAKTOR Factory Library has been prepared for
use in KORE 2. This also means that all IDs are already accessible with the
KORE 2 update of the factory content. If a controller cannot be automated,
this is due to technical limitations, and should not be changed.
There are some REAKTOR control elements that cannot be reached via a
VST host. The mouse area is an example.
Preparing an Ensemble for Use with KORE
The Ensembles that can be downloaded from the Reaktor User Library
Reaktor User Library
User Library
have not been optimized for KORE. New Ensembles built from scratch are
KORE. New Ensembles built from scratch are
. New Ensembles built from scratch are
also not optimized for KORE automation, of course. With the techniques
described above, preparing an Ensemble for use in KORE is straightfor-
KORE is straightfor-
is straightfor-
ward. Imagine an Ensemble that has been downloaded from the User
Library. If its builder designed it for use with Reaktor stand-alone (where
Reaktor stand-alone (where
stand-alone (where
automation is of no importance) all automation parameters will be at
random values. The incorporated controls like faders and buttons will fill
the local parameter lists in the order of their creation, and the MAX ID
value will have no relation to the number of available parameters. If there
are several instruments within the Ensemble, the order of the local lists
within the global list might also be not optimal. The automation has to be
KORE 2 – 223
Advertisement
