The trigger on a macro attached to a MIDI In port consist of two parts - the data and the mask. The mask defines which parts of an incoming MIDI packet need to match the data for the trigger to fire. The mask is derived automatically from the data given for the trigger - the more data, the more specific the mask.

There are between 1 and 4 fields in the trigger, separated by a space. They are only optional in sequence - so, for example, if you include the 3rd field, you must include the 2nd.

• The first must be present; it must be:
  • cc for control changes
  • pgm for program changes
  • on for note on messages
  • off for note off messages
• The second is optional; if present, it defines the channel of the trigger
• The third is optional; it is the first data byte of the message
• The fourth is optional; it is the second data byte of the message.

Note that program changes only have one data byte

Thus:

• The MIDI trigger pgm 3 will fire on all program changes on channel 3
• The trigger on 1 54 will only fire on Note On, channel 1, note 54 - but the velocity is ignored.
• The trigger cc 8 1 127 will only fire when the modwheel on channel 8 goes to maximum

• midi_macrocreate
• midi_macroadd
• midi_macroclear