Advertisement
The VST standard for audio plug-ins provides a way for remote-controlling
parameters in plug-ins called automation (this also applies for AU, RTAS
and other plug-in protocols). Nearly every sequencing package that can
host VST-plug-ins supports this. So if you have set up a nice KoreSound
while KORE 2 is running as a plug-in in your favourite sequencer, you can
also use this powerful system to generate very elaborate sounds. Please
refer to the documentation of your sequencing package for information on
how to set up plug-in automation.
KoreSounds can be nested structures using various instruments and effects.
However, the list of parameters subject to automation needs to structured in a
linear fashion, due to the way host and plug-in communicate with each other.
For this reason, the hierarchical structure of KORE 2's performance is
transformed into a linear list.
KORE 2 creates the list by simply adhering the KoreSounds' Pages to each
other. When a new sound is created or loaded, its Pages are inserted at the
first available slot of the list (if any Pages have been removed before there
can be "holes" in the list). This process only ceases when around 1000
parameters – with 16 on each Page, corresponding to more than 60 Pages
– are published. This is due to restrictions on the side of the host. All this
is organized in KORE 2 with the a
on the P
a
ageS and
utoMation
add and remove C
ontrol
Most of the times you won't need to re-arrange your a
However, some sequencing packages are limited in the number of
addressable automation IDs. In such a case you have to manually organize
your automation IDs to put the Pages containing the desired parameters
l
utoMation
iSt
t
of the S
M
aB
ound
anager
P
to the list of automatable parameters.
ageS
. It is opened by clicking
. With this editor you
l
utoMation
iSt
%
Automation of parameters
does work along similar
lines in other plug-in protocols like
AudioUnits or RTAS.
.
KORE 2 – 101
Advertisement
