Gordius TinyBox, Руководство пользователя

Страница: 44 / 90

43
4.5. Defining the preset contents
In many cases a preset can be very simple: a single MIDI ProgChange command can be used to select
a certain patch or sound in an effects module for instance. In this case the preset content can be
described on a single line in the setup :
PRESET Vox Ac-30 = SendMidi Profiler ProgChange 2
In other cases a preset can be more complex, sending multiple MIDI commands to multiple devices. In
that case those commands are specified on multiple lines, surrounded with curly braces:
PRESET 65_Bassman =
{
SendMidi Profiler ProgChange 5
SendMidi Helicon ProgChange 17
SendMidi Octaver CtrlChange 13 127
}
Do the same for each preset in the preset list. If you don’t specify any content for a preset, the setup
compiler will not complain, but obviously nothing will happen when selecting that preset using the
FCB1010 preset switches.
Optionally a preset can also send MIDI messages on switch release, although this behavior is more
appropriate for “triggers”, which are designed for exactly that (see below). If you want a preset to send
messages on switch release, use following syntax :
PRESET_RELEASE Vox Ac-30 = SendMidi Profiler CtrlChange 23 100
4.6. Defining the effect contents
As explained in an earlier chapter, the main difference between effects and presets is that effects can
toggle between 2 states: ON and OFF. For each of those 2 states you will need to specify the MIDI
command(s) to be sent. Again, in many cases sending one single MIDI command will be sufficient to
(de)activate an effect, but you can go as complex as you desire, using following syntax :
EFFECT_ON Chorus = SendMidi Strymon CtrlChange 3 127
EFFECT_OFF Chorus = SendMidi Strymon CtrlChange 3 0
EFFECT_ON Delay =
{
// any combination of multiple commands
}
EFFECT_OFF Delay =
{
// any combination of multiple commands
}