2019/10/22 16:44 65/76 MIDIbox SEQ V4 Beginner's Guide
MIDIbox - http://wiki.midibox.org/
On the output side, GPK12 selects the output port where the node's input port's MIDI messages are
routed to. GPK13 selects the MIDI channel which the outgoing message is sent on. The outgoing
channel doesn't have to be the same as the original incoming channel, so you can e.g. transform
incoming channel 1 to outgoing channel 13. Channel options are:
a) 1 to 16 for a single MIDI channel. All incoming MIDI messages, regardless of their original channel,
are sent out on this channel;
b) 'All' for sending the message on its original channel; or
c) two special options: Track and Selected Track (Sel.Trk).
If the output port/channel option is 'Track', the router will direct the incoming messages to the track
whose ordinal number matches the incoming MIDI channel (provided that the input port/channel
options allow the message through). For example, if you have a MIDI controller that's sending MIDI
data on channel 7, 'Track' option will send the message out on the port and MIDI channel set on track
7's (G2T3) EVENT page. MIDI channel 10 will get sent out on track 10 (G3T2), etc.
If the output channel option is 'Sel.Trk' (Selected Track), the router will direct the incoming messages
to the sequencer track that is currently active (provided that the input port/channel options allow the
message through). If you have several tracks selected, the MIDI message will go out on the channel
with the lowest ordinal number (track 1 before track 2, track 5 before track 6 etc.)
The final option on the MIDI Router page is DefaultPort. The tracks' EVENT page and a few other
pages allow you to select 'Def.' as one of the Port options. If you select 'Def.' as the Port, it will refer to
the Default Port setting on the MIDI Router page.
Note that the router settings might overlap with the Jam page note live forwarding option ('Fwd'). If
you have Fwd 'on', it will forward incoming MIDI messages on the 'Jam' bus (see section 4.1.1.) to the
active track's output port, set on the track's EVENT page. This is done regardless of any MIDI Router
settings. However, if Fwd is 'on', and at the same time you have a MIDI Router node routing MIDI
messages to the same port and channel as Fwd is forwarding them, MIDI messages like notes will get
triggered twice, almost simultaneously. This most likely alters how the note will sound, and perhaps
causes hanging notes. If you are using the MIDI Router to forward MIDI messages from one or several
MIDI controllers to output ports, you might want to make sure that Fwd on the Jam page is 'off'. On
the other hand, note that the Live Patterns function depends on Fwd being on. (See section 4.1.5.)
If you have two MIDI keyboards, one in IN1 (a plain MIDI controller) and the other in IN2 (a
keyboard synthesizer that's sending on, and listening to, channel 1), you could set them up so
that one of them always plays the channel it is set to send on, and the other always plays the
currently selected (active) sequencer track. Let's say you want to set your keyboard synth to
play the active track (selectable on the group and track selection buttons on the sequencer),
and the plain MIDI controller to play the channel you've selected on the controller. For this to
work optimally, you need to turn the Jam page Fwd option 'off' to avoid forwarding messages
twice. Also, you want to set your keyboard synthesizer's 'local' function off, so that the synth
is triggered only via MIDI.
On the MIDI Router page, set Node 1 like this for the plain MIDI controller:
IN Chn./P OUT Chn./P
Node 1 IN1 All OUT1 All
To Next Page
Loading...