Native Instruments O Kore 2 - Page 185

KORE 2 – 185
3.8.34 MIDI Player
The Midi Player offers exible facilities for playback and looping of MIDI
les. You can load MIDI les from disk, trigger and stop playback via
note messages, set loop points and create looP traCKS for controlling
downstream MIDI plug-ins and sequencers.
In respect to MIDI data, KORE 2 is strictly hierarchical. MIDI data ows
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 Player to be started.
But the hierarchy doesn’t end there. A Midi Player sitting higher in the
Sound Matrix hierarchy than another imposes the same control over the
ones nested further down. This means, if you have a Midi Player sitting
on the top level of your Performance with some other Midi PlayerS or
KoreSounds containing plug-ins that run sequencers, the top level Midi
Player 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 dening looP traCKS with arbitrary lengths in the player
any sequencer or Midi Player lying downstream of the looP traCK 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.