controlAid 1.97

controlAid was designed to help maximize the use of MIDI controllers with Live or any program that allows you to assign onscreen controls to MIDI messages.
Main features:
- outputs MIDI data it receives to a user selected channel. You can choose which channel controlAid outputs to with any knob/pedal/fader that sends CC messages.
- many programs let you MIDI map controls on different channels. One common use for controlAid is with MIDI maps in which all controls (such as pan, volume, aux sends etc) use the same note on or cc messages from track to track, but on different MIDI channels. By using controlAid to select which channel you are outputting to, you can in effect select which track or device your MIDI controller is sending data to.
- when a channel is selected, the track the channel number corresponds to is automatically selected and highlighted in Live so that you can view the effects for it.
- converts mouse movements for the entire screen to three different sets of user defined CC messages. Each set can be turned on/off individually, or they can be used simultaneously. When used with the 1->many option this allows you to control unlimited knobs/faders/buttons/notes using only your mouse.
- The velocities/values of noteon/cc messages can be assigned min/max values or inverted. This is useful when used with the one-to-many feature described next.
- allows you to have unlimited "one-to-many" noteOn or cc triggers. When these notes or cc messages are received, controlAid will create unlimited additional cc / note on messages as defined by the user. Examples of use include triggering multiple one-shot clips with a single note, or controlling the cutoff frequency for the filters of all your tracks / instruments with a single knob, slider or pedal. You can use the invert, max and min capabilities of controlAid to setup all kinds of special crossfades between different effects using the one-to-many function. All MIDI messages generated using mouseMode are sent through these transformations.
- allows you to map the noteOn and CC messages that your controllers create to three different virtual outputs via a small matrix. This is very useful for controlling multiple programs simultaneously. One example would be to send noteOn messages from a controller to a Reason synth but not to Live so that you dont have to worry about accidentally triggering audio clips. The CC messages from the same controller could then be mapped to both Live and Reason if desired, or have the CC messages going to Live while only the notes go to Reason.
- converts program change messages to note on messages for people with foot controllers that only send program change.
- allows you to delete a selected clip in Live using a user-defined note on message. This is useful for deleting clips from a pedalboard in the event you create an undesirable loop.
- clipFill mode is an optimized way to quickly loop through a user defined range of slots using a single note on message. This allows a user to quickly record into a predefined number of slots and then immediately start triggering them for playback, all using a single switch pedal or note.
- the channel selected for output can be incremented or decremented using the cmd+5 and the cmd+6 key combinations. This allows you to select which channel controlAid is transmitting on using a device like the Griffin Powermate, or any other external device than can trigger keystrokes.
- cmd+7, cmd+8, cmd+9, cmd+0 allow you to trigger four midi notes of your choice using the keyboard. The keystrokes can also be triggered via an external device such as the Griffin Powermate. cmd+4 allows you do delete clips in Live from one of these devices.
- controlAid can merge two MIDI inputs.
Enhancements:
- Added channel split feature to i/o section.
- Added greater ability to split notes from their cc values and route to different outputs.
- Added "help" button for quicker online help access.
- Really fixed the bug that was supposedly fixed in 1.81. No, really. 1.81 Fixed bug that would cause controlAid to crash when two MIDI devices with the same port names were being used. Midi Devices are now identified by their model and port name in the i/o menu, and are also each assigned a unique ID number to prevent the bug.