Native Instruments O Kore 2 - Page 221

KORE 2 – 221
the KoreSound will be unable to nd the Ensemble. (This is similar to
a sampler that needs its samples at a pre-dened place.) To keep the
Factory Content working, don’t move the les. This is also true for custom
KoreSound and custom Ensembles.
Pre-denedControlPagesand User Pages
All pre-denedpre-dened C ontrol P ageS of a KoreSound are based on the Factory
Content Ensembles’ automation lists. If these lists are changed by the
user the pre-dened C ontrol P ageS won’t work correctly. All Ensembles All Ensembles
within the Factory Content folder of Reaktor must not be changed to ensure
proper interaction of KORE 2 and Reaktor.
The pre-dened C ontrol P ageS are loaded when a plug-in is loaded into
KORE. For nearly all applications this is the perfect solution: FM8, for. For nearly all applications this is the perfect solution: FM8, forFM8, for, for
instance, will present the same list of parameters every time it is loaded
into KORE, and thus this forms a stable fundament for theKORE, and thus this forms a stable fundament for the, and thus this forms a stable fundament for the Control PageS.
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-dened Control PageS.
The preferred way to use Reaktor withinReaktor within within KORE 2 is loading a KoreSound
based on a Reaktor Ensemble.Reaktor Ensemble. Ensemble.