malletKAT User Manual (ver.07-17-18)
3) Same as (2), but then you also want to play along with the incoming MIDI. (This is a common need when
wanting to perform with accompaniment tracks with minimum equipment)
4) You want to set up your malletKAT as a part of a MIDI chain that passes through some MIDI channels, but not
others.
To best explain how the malletKAT handles all of this MIDI “traffic”, we will
break it up into two groups:
MIDI data generated by the malletKAT
Any MIDI data generated by a User Setup (Controller One, Controller Two, or Reassignments) must routed with
one of the following:
External Only
Internal Only
Both (default setting)
Neither
This is applied to the following Kit Auxiliary settings for a User Kit:
INTERFACE MODE (Kit Shortcut #25) (Note and Channel data for Controller One or Two)
PITCH BEND ROUTING (Kit Shortcut #42)
REASSIGNMENT POLYPHONY AND INTERFACE (Kit Shortcut #30)
This is also applied to the following Global Auxiliary settings:
FINE TUNING ROUTING (Global Shortcut #65)
GROOVE ROUTING (Global Shortcut #62)
This MIDI data is routed to MIDI OUT as follows:
External (or Both) goes to the side MIDI OUT port
Internal (or Both) goes to the rear MIDI OUT port
malletKAT firmware before 7.5B routes all of this data to both ports.
MIDI data coming from the MIDI IN port
There are two settings in the Global Auxiliary area used to handle MIDI IN data. They use the same parameters
(Internal Only, External Only, Both or Neither) as listed above. The default is “Both”
INCOMING CHANNEL ( 1 to 16 ) ROUTE TO (Global Shortcut #24-39) Each MIDI channel can be configured
separately, and can be used to pass through, reroute, or completely block some MIDI channel data.
INCOMING SYSTEM MESSAGE ROUTE TO (Global Shortcut #40) Because there is no MIDI channel data
associated with system messages, they are treated separately.
99 / 109
To Next Page
Loading...
