Advertisement
the KoreSound will be unable to find the Ensemble. (This is similar to
a sampler that needs its samples at a pre-defined place.) To keep the
Factory Content working, don't move the files. This is also true for custom
KoreSound and custom Ensembles.
Pre-defined Control Pages and User Pages
All pre-defined
pre-defined C
ontrol
Content Ensembles' automation lists. If these lists are changed by the
user the pre-defined C
within the Factory Content folder of Reaktor must not be changed to ensure
proper interaction of KORE 2 and Reaktor.
The pre-defined C
ontrol
KORE. For nearly all applications this is the perfect solution: FM8, for
. For nearly all applications this is the perfect solution: FM8, for
instance, will present the same list of parameters every time it is loaded
into KORE, and thus this forms a stable fundament for the
KORE, and thus this forms a stable fundament for the
, and thus this forms a stable fundament for the C
Reaktor, however, presents parameter lists that can change during opera-
, however, presents parameter lists that can change during opera-
tion, simply by loading a different Ensemble. This complicates the usage
of pre-defined C
ontrol
The preferred way to use Reaktor within
based on a Reaktor Ensemble.
Reaktor Ensemble.
Ensemble.
P
of a KoreSound are based on the Factory
ageS
P
won't work correctly. All Ensembles
ontrol
ageS
P
are loaded when a plug-in is loaded into
ageS
P
.
ageS
Reaktor within
within KORE 2 is loading a KoreSound
All Ensembles
FM8, for
, for
P
.
ontrol
ageS
KORE 2 – 221
Advertisement
