MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
92
➏
If you need more than three split points, you can bring up the next row of three split points
using
, where is an arrow.
The suggested MIDI channel for the next split zone in the sequence will be shown.
➐
Activate the new row of split points by pressing
, and program any further split
points.
➑
The “
CLR
“ (Clear) key deletes split points, starting always with the highest.
➒
The “
Read
“ key allows you to check the split settings of your currently selected input
without any danger of changing anything. Repeated presses will cycle through all the splits.
%
Quit this function by pressing
.
&
No more than 16 split zones can be set up per input and MIDI base channel, because
zones are split into MIDI channels. Designating channel 16 as the base channel would
mean the next zone would become channel 1, which makes no chance.
With the Split function you have to work with the sequence of following channels and
cannot leave one channel between out! Otherwise try your split with the Filter function
(Notes </>/).
6.3.1 Special handling of controllers
6.3.1 Special handling of controllers
6.3.1 Special handling of controllers
6.3.1 Special handling of controllers
“Controllers
Controllers
Controllers
Controllers“ are MIDI control change events such as Modulation, Sustain, Volume etc. plus
MIDI Pitch Bend events. All controllers and Pitch Bends are given special treatment within the split
function. The idea of this is to allow this data to be separated from the rest. For this reason controller
data is not split like notes are.
➔
Controller events are kept on the MIDI channel on which your keyboard sent them, and not
Controller events are kept on the MIDI channel on which your keyboard sent them, and not
Controller events are kept on the MIDI channel on which your keyboard sent them, and not
Controller events are kept on the MIDI channel on which your keyboard sent them, and not
converted to other channels by the split function.
converted to other channels by the split function.
converted to other channels by the split function.
converted to other channels by the split function.
The crucial factor in the output of keyboard split zones and controllers is routing. The most
straightforward way of making use of this arrangement is to set the MIDI base channel to 2
(“
keyboard=Ch 2
“ therefore “
left zone=Ch 2
“), but to leave the keyboard set to transmit on
channel 1:
*
Receive channel
➪
channel 1
*
“left zone“
➪
channel 2
*
Zone 2
➪
channel 3
*
Zone 3
➪
channel 4
*
Zone 4
➪
channel 5
You can then route the control channel (in this case 1) from this split input to the required
outputs and convert it to the receive channel of the expander, synthesizer etc. which needs those
controllers. The four split zones should be routed as follows:
*
Channel 2 to
➪
channel 10, output 2
*
Channel 3 to
➪
channel 11, output 2
*
Channel 4 to
➪
channel 12, output 2
*
Channel 5 to
➪
channel 13, output 2
Channel 1, the control channel, should also be routed to channels 10, 11, 12 and 13 in
output 2 if all zones need to have controllers acting on them. If you do not program the routing for
one of the split channels, you can filter controllers out for one or more of your keyboard zones.
