
23
All programming steps come to an end when the first EMPTY slot is encountered. Programming commands placed after the
first EMPTY slot will be ignored. Keep this in mind if testing parts of the programming commands are needed- you can
temporarily add an EMPTY command to stop processing the commands below it in the sequence.
The Structure of Programming Commands
Think of programming commands as a sequence of events. The events get triggered one after another until there is a reason to
stop. The reasons to stop in this case will be either (1) an EMPTY slot is found, (2) we are processing STEPS and we
encountered the next STEP, and finally (3) if we processed the last programming command.
Normally programming commands are processed one after another. This only differs when you are programming STEPS.
STEPS offer enormous levels of functionality control, but are simple to implement. Every Preset and IA Slot can process up to
four STEPS each, with each STEP having the ability to be given a unique name to identify it. On a first press of the preset or IA
switch- Step #1 commands will be processed. A 2
nd
press will trigger those commands found in STEP #2, etc…
Preset MSG #
Data to enter Prompt (entering a midi command)
An example of a Continuous Change Message:
Command Type MIDI CHAN MESSAGE TYPE DATA1 (CC#) VALUE
The above command says: Message #1 is a Command Type:MIDI Command (01), which will transmit on MIDI CHAN (01),
and will send a CC# message to controller (002), and will send a value of (127 = ON).
Preset MSG #
Data to enter Prompt (entering a set color command)
An example of a NON-MIDI Command:
Command Type
VALUE
MSG01|CC#
01 | 01|4| 002 | 127
MSG02|SET COLOR
13 | Green (Dim)
Содержание Mini
Страница 1: ...Table of Contents...
Страница 31: ...31 MSG01 CHANGE PAGE 08 011 LOOPERpg MSG02 CHANGE PAGE 08 010 MainPage...
Страница 67: ...67...
Страница 98: ...98 www FAMCmusic com...