513
Engl
ish
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).
Instrument Definition Tutorial
The following tutorial takes you through the process of setting up an instrument definition for a Roland
keyboard so that the bank and patch names, including any self-created sounds, read the same in
SONAR as they do on the display screen of your keyboard instrument.
Why Use Instrument Definitions?
The main reason to import or create an instrument definition is so you can use patch names that are
specific to the MIDI module you’re using, instead of using generic General MIDI patch names. It’s much
easier to find a particular sound on a MIDI module when the actual names of the patches in the current
bank of sounds pop up on a list, instead of just the numbers 0 to 127, or General MIDI names like
Trumpet. Of course, if you’re only using General MIDI modules, General MIDI patch names might be
all you need. You can also rename each MIDI output with the name of the MIDI module it’s connected
to. For example, it might be more meaningful to name a MIDI output Roland Sound Canvas instead of
MOTU MIDI Express 5. That way, you won’t have to remember that you connected the Sound Canvas to
the MOTU MIDI Express output number 5—the name Sound Canvas shows up as an option in the
Output field of each MIDI track in SONAR’s track view. Also if you have an effects processor or module
that’s hard to get to in your studio, you may find it convenient to control it from SONAR.
What Can They Do and Not Do?
Instrument definitions don’t increase the number of sounds or the capabilities of your modules, they
just make it easier to find and remember the sounds and/or MIDI controllers you want to use, if they’re
not all generic General MIDI items. After you define an instrument, SONAR displays the names that
you choose for the sounds in each of that instrument’s banks, rather than displaying the same 128
General MIDI names over and over for each bank of sounds.
Where Do Instrument Definitions Come From?
The patch names and other characteristics of each particular MIDI module are supplied by the
manufacturer, and are contained in an instrument definition file, which is a text file written in a format
SONAR can read. Many of these files come with SONAR, and many more are available at Cakewalk’s
website, and also at lilchips.com. Instrument definition files have the extension .
INS
and can contain a
definition for only one instrument, or definitions for several instruments. For example, the file
Summary of Contents for Cakewalk SONAR
Page 1: ...Cakewalk SONAR User s Guide ...
Page 2: ......
Page 4: ......
Page 22: ...xxii ...
Page 50: ...50 ...
Page 102: ...102 ...
Page 182: ...182 ...
Page 302: ...302 ...
Page 420: ...420 English ...
Page 466: ...466 ...
Page 502: ...502 ...
Page 574: ...574 ...
Page 580: ...580 ...
Page 608: ...608 ...