Mute Automation
MIDI Map
The MIDI Map determines what MIDI messages will be used for each Mute and Mute Group when using an external MIDI sequencer to automate the X2. There are several maps to choose from, each designed for use with specific sequencers. In general, you will probably pick one Map to use on all occasions, based on what type of sequencer you are using.
JYou must be offline for the MIDI maps to be active. If you are online, the X2’s internal sequencer is active.
MIDI Map 1.1 assigns each Mute and Mute Group to a different MIDI note number. Whenever a channel is muted, its respective note number message is sent as a short note (a note-on followed by a note-off) with a high velocity value. When that channel is unmuted, the same note number is sent, this time with a velocity value of 0. This map can be used by almost any sequencer. However, if your sequencer has the ability to “chase events,” you will probably want to use a different map that works better. The X2 is designed to ignore the common ALL NOTES OFF message that most sequencers transmit when playback is stopped. This is important as it could potentially change the mute status in an undesirable fashion.
Map 1.2 is a variation of 1.1. The note number assignments are the same for all channels. However, when a channel is muted, a note-on message is sent; when the channel is unmuted, a note-off of the same note number is sent. Thus, sequencers that can chase note events will allow you to locate anywhere in the sequence and update the console’s mute status.
Map 1.3 is the opposite of Map 1.2. When a channel is muted, a note-off is sent; when unmuted, a note-on is sent. This is useful when using a sequencer that doesn’t like to record very long notes (if you have some channels muted most of the time while using Map 1.2, some sequencers may “bail out” of record and create a note-off for that channel, assuming that the note is stuck).
Map 1.4 uses MIDI controllers to control the Mutes. When a channel is muted, a value of 127 is sent for the corresponding controller number; when unmuted, a value of 0 is sent. MIDI provides 128 possible controllers. However, certain controllers are not used, due to the fact that some sequencers reset them whenever playback is stopped. This is useful on keyboards (turning off a sustain pedal, etc.), but is not desirable on a mixing console.
Maps 2.0 through 2.9 send out bursts of System Exclusive messages, sort of like a camera with automatic film-advance. The difference in the Maps is how often a snapshot is sent. Map 2.0 sends a snapshot every 250 ms, whereas Map 2.9 sends a snapshot out every 8 seconds. This means if the mixer just sent out a snapshot before you pressed a MUTE, you’ll have to wait anywhere from 250 ms to 8 seconds before the change in mute status is transmitted. These maps are useful when using a sequencer that does not provide event chasing. Use the higher-numbered maps to minimize MIDI information when accurate timing is not essential.
