
KORE 2 – 185
3.8.34 MIDI Player
The Midi P
layer
offers flexible facilities for playback and looping of MIDI
files. You can load MIDI files from disk, trigger and stop playback via
note messages, set loop points and create l
ooP
t
raCKS
for controlling
downstream MIDI plug-ins and sequencers.
In respect to MIDI data, KORE 2
is strictly hierarchical. MIDI data flows
from top level down through the S
ound
M
atrix
. The highest instance is the
global clock of the stand-alone or the host clock, when KORE 2 is running
as a plug-in, respectively. It has to run for any Midi P
layer
to be started.
But the hierarchy doesn’t end there. A Midi P
layer
sitting higher in the
S
ound
M
atrix
hierarchy than another imposes the same control over the
ones nested further down. This means, if you have a Midi P
layer
sitting
on the top level of your Performance with some other Midi P
layerS
or
KoreSounds containing plug-ins that run sequencers, the top level Midi
P
layer
has to run for the downstream sequencers to run.
The Midi P
layer
can also be controlled by an upstream S
teP
S
eQuenCer
component and of course this works the other way around, too.
Another intended use of this plug-in is a reset facility for downstream
Midi P
layerS
and Sounds that use sequencers or arpeggiators within of
their plug-ins. By defining
l
ooP
t
raCKS
with arbitrary lengths in the player
any sequencer or Midi P
layer
lying downstream of the l
ooP
t
raCK
is reset
%
Internal MIDI plug-ins are
handled in the same way
as any other device in KORE. This
means you can save them as a
KoreSound to recall their settings at
a later stage.
!
If the MIDI Player’s Track
List is empty, it will not
prevent any downstream players or
sequeners from running, even if it
is stopped.