Advertisement
exposed to the host software. As the setup of a REAKTOR Ensemble
or a KONTAKT Multi can be arbitrarily complex, the creators of the
respective patches have to decide and manually program the parameter set.
Please be aware of this when you create your own REAKTOR Ensembles
or KONTAKT Instruments and refer to the documentation of the respective
plug-in if you are unsure how to manage this. For the Native Instruments
KOMPLETE series of virtual instruments, the complete library of patches
has been prepared for the use in KORE 2. Please refer to Appendix A
for more information about the special behavior of some KOMPLETE
plug-ins. Appendix A is also a good read if you want to integrate your own
REAKTOR Ensembles in KORE 2. It contains a dedicated section about
REAKTOR in KORE 2.
KORE 2 and sample libraries
KORE 2 acts as a host for VST-/AU-plug-ins. This means it directly handles
the parameters that are exposed by the various plug-ins. But plug-ins do
not only consist of parameter settings, they also bring along other content,
like samples. KORE 2 only loads the plug-in and the sample content is
handled on the plug-in level without control by KORE 2. This leads to some
pitfalls when handling sample libraries. The basic rule is that the respective
plug-in has to know where to find its content so that it loads correctly in
KORE 2. If the plug-in alone doesn't even know where to find its content,
it won't know it in KORE 2, either. If you ever experience problems with
samples not loading in KORE 2, be sure to first check the settings inside
of the respective plug-in and do not look for the problem in KORE 2.
Some rules of thumb:
KORE 2 – 29
Advertisement
