ChamSys MagicQ User Manual - Manual (Page 279)

MagicQ User Manual 250 / 355
When using the MagicQ MIDI/SMPTE interface for MIDI only the Timecode options can be set to none and then the last received
MIDI command will be shown in the Status Display.
35.1.1 MIDI Autom events
MagicQ supports triggering of automated events via MIDI in the Macro Window, View Autom.
Autom events can be set to trigger Playbacks, Cue Stacks, Cues and other events when MIDI notes are received.
35.1.2 MIDI mapping file
MagicQ supports a custom MIDI mapping file for use instead of the Autom events - this enables greater flexibility and control.
If any Autom events are set to respond to MIDI then the MIDI mapping file is ignored.
MagicQ uses the text mapping file miditable.txt stored in the MagicQ folder to convert from MIDI commands to MagicQ serial
commands.
An example file miditable.txt is included which maps midi notes to the playbacks PB1 to PB34. Each line in the file specifies a
received MIDI command and then the mapping to the serial command in inverted comments “”.
For example, the first to lines in the default file are:
144,36"1t"
128,36"1u"
MagicQ checks the received MIDI note byes to see whether they match the values. So if the MIDI message matches 144 36
then it executes the remote command 1t (Test Playback 1). Similarly if it matches 128 36 then executes the remote command 1u
(UnTest Playback 1).
Note that Test and Untest are like Activate and Release except they force the Playback level to be 100% and 0% respectively.
Note that for security reasons MagicQ limits the number of playbacks that can be controlled using MIDI and the remote protocols.
On MagicQ consoles PB1 to PB34 can be controlled. On MagicQ PC, playbacks PB1 to PB10 can be controlled.
Users may use their own MIDI conversion file “usermidimap.txt” rather than the in-built “miditable.txt”. This avoids user midi
tables being overwritten when new software versions are loaded, since only the “miditable.txt” is updated on software updates.
35.1.3 Advanced MIDI mapping
It is possible to match all 3 MIDI message bytes including the velocity. So for example:
144,36,100”1t”
144,36,101”1u”
This would execute the Test Playback 1 when Note On for note 36 at velocity 100 was received and Untest Playback 1 when
Note On for note 36 at velocity 101 was received.