AD2 *.INS file creation

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 www.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 Roland.ins contains definitions for many Roland modules. The file Misc.ins contains miscellaneous definitions that might include your instrument if you don’t see a specific file for it. You can find these files in your SONAR folder. The file Master.ins contains all the instrument definitions currently loaded into SONAR, and determines the list of instruments that appears in the Assign Instruments dialog box.