The above command says: Message #2 is a Command Type:Set Color (13), which will change the current preset to show a
green color (dimmed). This will override the default color scheme for this preset only.
Navigating the creation of a programming command is accomplished by pressing and to select
a value, and pressing and to move the cursor (data entry position). In the above
example, an underline (cursor) is located under the 4, which is a CC# midi command. As you move through the parameters,
the PROMPT area will tell you what it is looking for you to enter as far as data. The screen will change based on how many
parameters need to be entered for a given command.
Press after you complete your edits to the command. The system will save your modifications and move the
cursor back to the Message # field so that you can select another Message to edit.
Command Types
The first parameter you must enter is the Command Type. Most often you will be using command type 1 (MIDI COMMAND).
Special Commands will be added as firmware revisions are made available. Check updated firmware user guides for details on
specific functions and their related parameters.
Commands are processed in the sequence they are programmed. This matters for instance when using steps (command #3).
Think of the commands as a set of instructions for the preset, song, or IA Slot to process in a particular order. This will also
sequence the order of MIDI commands going to your effects and other MIDI equipment. This will matter if you are using the
Delay command (#5). Perhaps you need a 5ms delay between sending one SYSEX message, and a second message. The
sequence of events would be a COMMAND TYPE #4 (SYSEX SEND), a COMMAND TYPE #5 (delay), COMMAND TYPE #4
(another SYSEX SEND). Sometimes equipment can’t change presets and process messages instantly. Thus an inserted delay
after a preset change message would be the solution. Hence the order matters.
Below is a list of the Command Types available:
To Next Page
Loading...