Bruce's MIDI Solution Gallery

In addition to changing the AN1x's functions, we want the CX-3's expression (volume) pedal to work with the S4, for use with combo organ and accordion sounds. This way, we don't need to carry an extra pedal for the songs that use these sounds. It would also be nice if the AN1x's knobs and switches provided control over the S4 and vocoder when in use.

We send the AN1x and CX-3 to a MIDI Solutions Quadra Merge -- a MIDI Solutions Merger would also work here -- and then into the S4, and use different MIDI channels on the AN1x to select its function: CH2 for organ, CH3 or CH4 for synthesizer and other sounds, and CH5 for vocoder.

Sounds straightforward, right? Sure ... except that, like most MIDI setups, there are some snags:

• The vocoder obeys MIDI controls CC102-CC116, while the AN1x's knobs can only send CC1-CC95.
• I didn't want CX-3 program changes to reach the S4, but there's no way to turn them off on the organ, or to ignore them on the S4.
• I wanted AN1x Knob 7&8 and the CX-3's pedal to go to the S4, but the signals come in on different MIDI channels, while the module needs them on one channel (CH1).
• The merged MIDI stream had data that the S4 never used; removing it reduced MIDI traffic and prevented MIDI Overflow messages.
• The AN1x program changes should always go to the S4, regardless of the channel used, to keep it in sync with the rest of the gear; however, the AN1x's transmit channel was being used to select the sound being played, and changed often.

Luckily, a MIDI Solutions Router and a MIDI Solutions Mapper can fix all the shortcomings of the gear. (The Mapper isn't made anymore, but a MIDI Solutions Event Processor can do the same thing.) I used the Mapper to change the CC number of the An1x's Knob 1-4 and Scene controller to match the needs of the vocoder -- but only when the keyboard was sending on the vocoder channel (CH5), so that they were still available for synthesizer needs. I then used the Router to change Knob 7&8 and expression pedal messages to CH4, regardless of the real transmit channel, and to send program changes there, too. The Router also filtered out all CH1 program changes and CH2 note messages from the CX-3.

Here is how the whole thing was wired up:

Programming this whole setup takes five of the ten "rules" in the Mapper, and six of ten in the Router, leaving plenty of room for future needs. The Router, Mapper, and QuadraMerge can all be mounted with Velcro® and pre-wired in a rack with the S4 and vocoder, leaving only the four green connections to be re-attached at the gig.

• The KS88 controls both the Virus and a pair of Alesis QSR rack modules, along with a MAM Vocoder through one of the QSRs. The QSRs have an annoying wrinkle in that they re-initialize all channel volume and expression to full-on after a program change. Why? Maybe it works better with MIDI files in GM mode, or maybe it's just easier to implement. Either way, it's annoying to switch programs in a soft part and have the volume jump up when playing live.

  Correcting this problem is complicated by the fact that the QSRs don't obey CC messages until the program change has "settled in," meaning that one cannot just send a PG message immediately followed by a series of CC messages.

• The Virus can be used in Single or Multi mode, but the user must switch from one mode to the other before calling up a new program of a different type. This can be done manually, but since the Virus is sitting off to the side of the KS88, it's not very performance-friendly to remember to reach over and change modes before calling up a new program. It would be better if the KS88's many switchs could call up a mix of Single and Multi programs without having to remember the current mode.

  Like the QSRs, the Virus seems to like a brief pause between the SysEx message that changes modes and the next program change message.

• Believe it or not, I need more than four zones! I don't use them for splits, but there are certain things that I want to do with the Virus and QSR that can't be globally linked to one MIDI channel. (The explanation is complicated. If you really want to know the details, contact Ashby Solutions.) I already have the four zones linked to CH1, CH2, CH6, and CH16 -- I'm out of transmit channels.

We send the KS88 to a MIDI Solutions Event Processor Plus (EPP) and then into the QSR and Virus. We use the EPP to keep track of several volume and expression sliders from the KS88, and to re-send this information to the QSRs, after the necessary pause, with each program change.

Rather than sending program changes directly to the Virus, we use two CC values to signify Single and Multi programs, and use the mapping ability of the EPP to convert these CC events (messages) to program changes. When a "program change" is sent, the EPP adds in the necessary SysEx to switch modes, along with a pause, and allows different "program change buttons" to call up the correct mode for the sound without any hassles.

The EPP also filters out all QSR program changes above 99, because they wrap around. Here is how the whole thing is wired up:

We also map incoming note messages to other channels, sometimes in place of the original note message, or in addition to the original message.