Reference Guide

1133
Creating instrument definitions
Instrument definitions
See also:
“Creating and editing patch name and other lists” on page 1125
“Copying name lists” on page 1127
“Assigning the Bank Select method” on page 1127
“Assigning patch names” on page 1129
“Assigning note names” on page 1130
SONAR flags in instrument definitions
SONAR has several flags that you can use in instrument definition files for use with specific
instrument definitions.
UsesNotesAsControllers=n
Some MIDI devices, certain mixers for example, use MIDI Note events instead of Continuous
Controller events for automation. It is often desirable to treat the Note events as Controller events in
order for them to obey the “Zero Controllers When Play Stops” and “Patch/Controller Searchback
Before Play Starts” settings.
You can enter this variable in any instrument definition by using a text editor, such as Windows
Notepad. The variable should be entered directly below an instrument definition. For example:
[Mackie OTTO-1604]
UsesNotesAsControllers=1
Control=Mackie OTTO-1604
Patch[*]=Mackie OTTO-1604
Key[*,*]=Mackie OTTO-1604
NoControllerReset=n
Any port/channel using an instrument definition that has a NoControllerReset flag set to 1 does not
receive a "zero controller" message upon stop. You can enter this variable in any instrument
definition by using a text editor, such as Windows Notepad. The variable should be entered directly
below an instrument definition. For example:
[Yamaha Promix 01 Control Chan]
NoControllerReset=1
Control=Yamaha Promix 01 Control Chan
Patch[*]=Yamaha Pro Mix 01
This parameter should be used when it is undesirable to zero/reset controllers when playback stop,
such as when using an external effects processor that uses MIDI controllers for real-time parameter
control, or when using a digital mixer as a MIDI control surface (and not using the generic control
surface plug-in).