opcode using oms name manager 1996

7/30/2019 Opcode Using OMS Name Manager 1996

1/35


2/35

Ch 1: Overview and Terminology Using the OMS Name Manager pg. 2

CH 1: OVERVIEW AND

TERMINOLOGY

OMS prov ides a patch nam e management tool, called theName Man-

ager

. With th is tool, you can organ ize the nam es of all the patches in

your MIDI devices and p rovide those nam es to Vision or an y other

OMS 2.0-compatible ap plications.

You configure the Nam e Manager using theNames Window

, which is

available within any OMS 2.0-comp atible app lication. Once the

Nam e Manager is configured, comp atible applications will display

your MIDI devices pa tches by name

rather than byprogram number

.

Generally, the d ocumentation th at accomp anies your OMS-comp ati-

ble applications will discuss the Nam es Window in d etail. This

docum ent is meant to be a general, stand-alone d iscussion of the

Name Man ager. It is somew hat Vision-specific, but the techniques

discussed w ithin it ap ply to any OMS 2.0-comp atible ap plication.

NOTE: This document discusses Name Manager operations for bothMacintosh and Windows. Screen-shots from both operating systemsare used interchangeably. Whenever any platform-dependent differ-ences occur, they are noted specifically.

TERMINOLOGY

Every MIDI device manu facturer seems to u se different terminology

to describe similar features in th eir devices. For example, d ifferent

synthesizer manu facturers u se the terms p atch, voice, part,

program, or sound to mean th e same thinga collection of pro-

gramm able parameters that work together to create a un ique sound .

Because Op code has no way of knowing w hich MIDI devices you

own, we m ust d escribe certain Nam e Manager fun ctions generically.The following m ini-glossary lists the terms well use in describing

the Name Manager.

P

ATCH

A collection of param eters in a d evice that d efine the soun d played

wh en recalled. For example, one patch might create a trumpet soun d

and another might create a guitar sound.


3/35


B

ANK

A collection of patches stored in a MIDI device. Most modern MIDI

devices have storage for hun dreds (or even thou sand s) of different

patches. However, the MIDI specification only provides patch

change m essages for 128 patches. In ord er to access more than 128

patches, a device mu st store them in banks

, which are accessed via

bank select

messages. The actual bank select messages vary from

device to device.

M

ODE

The state of a device that d etermines how MIDI program changes are

interpreted.

Imagine a synthesizer with three different mod es:

Patch Mode

: Individual sounds, such as Electric Piano, Acoustic

Guitar , or Flute.

Effect Mode

: Effects programs such as H all Reverb, Slap Delay,

or Flange.

Performance Mode

: A combination of several individu al sound swith an effects patch, such as an Electric Piano p atch layered w ith

a Flute patch and assigned to a Hall Reverb effect.

Usually devices access the d ifferent mod es by interp reting p atch

change m essages different ly for different chan nels. For instan ce,

General MIDI devices have patch channels and drum channels.

Send ing program change #1 to a channel in patch m ode calls up a

piano, whereas sending p rogram change #1 to a channel in d rum

mode calls up a standard d rum kit.

By using d ifferent device mod es, Vision can display and select any

patch typ e contained in your MIDI device.

Do not confuse modes w ith banks; a bank of patches for one m ode

might contain an entirely different nu mber of patches than a bank

for a different m ode.

P

ATCH

N

AME

DOCUMENT

A document that stores and p rovides patch names and device modes

for one or more devices. There are th ree kinds of Patch Name

documents:

Typed-in name documents created u sing the Name Manager

Galaxy Bundles

Bund les created by another OMS 2.0-compatible librarian

There are subtle differences in the way the Name Man ager handles

each typ e of docum ent; these will be noted th rough out the rest of

this chapter.


4/35


C

URRENT

P

ATCH

N

AME

DOCUMENT

If a Patch Nam e docum ent is current, OMS thinks that th e patches in

the docum ent are loaded into the device. You can manually make a

docum ent current, or a librarian program like Galaxy might auto-

matically do it for you w hen send ing sound s to a device.

P

ATCH

N

AME

PROVIDER

An application that can create a Patch N ame d ocument read able by

the OMS Nam e Manager.

N

AME

S

ETUP

A map ping th at associates each MIDI device in you r current OMS

Stud io Setup docum ent with a specified Patch Name d ocum ent.

There is only one N ame Setup active at a time, and it lives inside

OMS, not the application.

Since the Name Setup is handled by OMS, changes mad e to the

Name Setup in Vision also affect the names seen by other OMS 2.0-

comp atible app lications. As you w ould expect, changes mad e in

other ap plications may affect the names seen in Vision.

When you save a sequence file in Vision, the current N ame Setup is

saved along w ith it.


5/35

Ch 2: Using the Names Window Using the OMS Name Manager pg. 5

CH 2: USING THE NAMES WINDOW

The Names Window is available within any OMS 2.0-compatibleapp lication. This chap ter discusses how to u se the Names Window.

OPENING THE NAMES WINDOW

To open the N ames Wind ow in Vision, choose Windows>Names

. If

youre using a d ifferent OMS-compatible app lication, see its owners

manu al to learn how to open the Names Window.

Figure 1: Anatomy of the Names Window


6/35


NAMES WINDOW ANATOMY

As you can see in Figure 1, the Names Window contains num erous

elements:

Device column

: This colum n shows the name of each MIDI device

contained in your current OMS Stud io Setup docum ent. You cannot

edit the contents of this column . Its contents change wh enever thecurrent Stud io Setup docum ent changes.

Devices stored in a N ame Setup but n ot defined in the current Studio

Setup ap pear in italics

.

Patch N ame Document column

: This colum n show s the Patch

Nam e docum ent referred to by each of the d evices. For more infor-

mation, see Patch N ame Document Colum n (pg. 6).

Device Mode column

: If a d evice sup ports m ultiple mod es, then this

column shows w hich mode it is using. You can change the mod e

directly in this column s pop -up m enu.

MIDI Channel column

: Some MIDI devices let you select d ifferentmod es on d ifferent MIDI channels. This colum n shows wh ich MIDI

channel uses the mode show n in the Device Mode

column . For more

information, see Channel and Device Mode Colum ns (pg. 9).

Name Setup control

: Use this pop-up menu to determine how

changes mad e in other ap plications affect the Nam e Setup . For more

information, see Name Setup Control (pg. 9).

The information contained in this window is saved w ith the

sequence file wh en using the File>Save

or File>Save As

commands.

The following sections d iscuss the Nam es Window in greater d etail.

P

ATCH

N

AME

D

OCUMENT

C

OLUMN

Use this column to select which Patch Nam e docum ent is referenced

by each MIDI device. This is called subscribing

to a docum ent. To

subscribe to a Patch Name document:

Click in the Patch Name Document column next to a MIDI device.

Select Names>Subscribe

.

Vision opens a standard Open dialog box.

For Windows, this dialog box is configured to show .ONM and .BNDfiles. Typed-in patch name documents have the .ONM extension.Galaxy bundles have the .BND extension.


7/35


Find the desired Patch Name document, then click OK

.

The column now shows the Patch Name document to which yousubscribed.

NOTE: If you dont know where to find Patch Name documents, readthe following section.

W

HERE

T

O

F

IND

P

ATCH

N

AME

D

OCUMENTS

There are three sources for Patch N ame d ocuments:

The Name Manager recognizes Bund les created by Galaxy and other

OMS-2.0 compatible librarians as Patch Name documents.

You can create your own typed-in Patch Nam e docum ents directly

from the N ame Manager.

To do so, dou ble-click in the Patch Nam e colum n to open the Patch

Nam e Editor. Use the Patch N ame Editor to create or ed it a Patch

Nam e document as described in Patch Name Editing (pg. 15).

Figure 2: Blank Patch Name Editor Window

Opcode supplies a collection of factory Patch N ame documents for

several popu lar synthesizers. If there is a factory Patch Name d ocu-

ment for your device, choosing Names>Use Factory/GM N ames

enables it. See Use Factory/ General MIDI Names (pg. 12).


8/35


C

URRENT

AND

M

ISSING

D

OCUMENTS

Figure 3: Name Setup showing current and missing documents

The Patch N ame Document column displays add itional information

about su bscribed d ocum ents by using italicized text and the small

x icon:

A small x appears before the name of each current

Patch N ame

document. A current Patch N ame d ocum ent is the docum ent that the

Nam e Manager uses to supp ly names to all OMS 2.0-comp atible

applications. For more information, see Nam e Setup Control (pg. 9).

In Figure 3, the K2000s Patch Name document is not

current. This

mean s that the patches actually resident in the K2000 dont match

the patches listed in the TEMP.ONM d ocum ent.

The Patch N ame document is italicized if the Name Manager cant

locate the d ocument. In Figure 3, the docum ent for the Proteus/ 2 is

missing.


9/35


N

AME

S

ETUP

CONTROL

Since the OMS Nam e Manager only references one Nam e Setup at a

time, changes m ade to the Name Setup in other applications can

affect Vision. Use the N ame Setup control to determine w hat h ap-

pens wh en changes are made to the N ame Setup:

Alw ays use current patches: Making Patch N ame documents cur-

rent in anoth er app lication changes the N ame Setup in Vision to

match.

Keep using these patches: Locks in the current Name Setup. Sub-

scriptions cant be changed in Vision by changing them in anoth er

OMS 2.0-compatible application.

This setting is not remembered betw een sessions. Whenever you

restart Vision, the control is reset to Alw ays use current patches.

CHANNELANDDEVICE MODE

COLUMNS

The Channel and Device Mode functions are interrelated an d are

described here together.

If a device supports m ultiple device mod es, then th e Device Mode

column contains a pop -up m enu listing all the possible modes.

Since each MIDI channel can access a d ifferent d evice mode, the Ch

(Channel) column displays which MIDI channels access which

device modes. You can v iew every enabled MIDI channel or just a

summary of all MIDI chan nels by clicking the d esired devices selec-

tor icon, then choosing Names>Show Channels.

Name Setup control

Device mode pop-up menu


10/35


Show Channels is a toggle whose value is changed by choosing it

repeatedly.

When Show Channels is checked (on), the Nam es Window displays

a separate row for every MIDI channel in that d evice (as assigned in

the OMS Stud io Setup docum ent). You can then select a device mode

for each MIDI chan nel.

When Show Channels is not checked (off), the N ames Wind ow dis-

plays a single row for that MIDI device and the Ch column is labeled

all . Changing the d evice m ode affects all channels simultaneously.

Figure 4: Channel mode indicators

Different Device Modesassigned to differentMIDI channels

The word various in the Device Modecolumn indicates that not all channels

are in the same mode.

The word all in the Chcolumn indicates thatShow Channels is off.


11/35


EDITING DEVICE MODESWHEN SHOW CHANNELSIS OFF

IfShow Channels is off and every MIDI chan nel is set to the sam e

device mod e, then that m ode appears in the Device Mode colum n.

IfShow Channels if off and different MIDI chann els use d ifferent

device mod es, then the d evice mod e column displays various, indi-

cating more than on e device mod e is active for this device (see

Figure 4).

EDITING PATCH NAME DOCUMENTSFOR MULTI-MODE DEVICES

If d ifferent MIDI chan nels reference different d evice modes, there is

only one way to edit each modes Patch Name d ocument:

Double-click a number in the Ch column.

Vision opens a Patch Name Editor for that MIDI channels mode.Patch Name Editing is discussed in Patch Name Editing (pg. 15).

IMPORTANT: This is the only way to edit the patch names for adevice with multiple modes.

Same device mode usedby all MIDI channels


12/35


NAMES MENU

The Names Menu is available whenever a N ames Wind ow is active.

Figure 5: Names Menu (Macintosh Version)

The following sections describe each command in the Names Menu.

SUBSCRIBE This command selects a Patch Nam e docum ent to which all selecteddevices are subscribed.

USE FACTORY/GENERAL MIDI

NAMES

If youre using a General MIDI synth, choose this comm and to sub-

scribe to the General MIDI Patch Nam e docum ent located in the

Factory N ames folder (FAC_NAM folder in your Window s

directory).

Also, some devices have p atches that cannot be altered. If you have

such a d evice, and if a Patch N ame d ocum ent exists for it in the Fac-

tory Names (FAC_NAM) folder, choosing this command

autom atically subscribes to that factory nam es docum ent.

If the d evice doesnt have an associated factory nam e file, the Gen-

eral MIDI patch names are used instead.

COPYSUBSCRIPTION

This comm and copies the subscription for the selected device(s) to

the Clipboard .


13/35


PASTESUBSCRIPTION

This comm and pastes subscriptions in the Clipboard onto the

selected device(s). Any p revious subscription is replaced and the

new Patch Name document becomes current.

CLEARSUBSCRIPTION

Removes the subscription information from selected device(s).

MAKE CURRENT When choosing this comm and , the following alert appears:

Clicking Dont Make Current retains the previous su bscription.

If the Send the patches option is available and checked, the Nam e

Manager attemp ts to transmit the patches to the device wh en you

click the Make Current button . The application that created the

Patch N ame d ocument m ust be capable of this operation. For exam-

ple, names obtained from a Galaxy bund le can be sent (if Galaxy is

available on your system), but typ ed-in name d ocuments cannot and

the Send the patches optionwont app ear in the alert.

USE CURRENTINSTEAD

Use Current Instead replaces the selected d evice(s) non-cur rent

subscriptions with subscriptions to the current Patch Nam e

document(s).

NEW PATCHDOCUMENT

Creates a blank, untitled Patch Name d ocum ent for the selected

device(s).

VIEW / EDITPATCH NAMES

Selecting a d evice and choosing th is comm and is equivalent to

dou ble-clicking a devices Patch Name docum ent column.


14/35


TELL PATCHPROVIDER

This menu item contains a sub-menu listing the comm and s that can

be sent to the Patch N ame Provider.

If the Patch Nam e Provider und erstands th e selected m essage, it per-

forms that action. For examp le, if pa tch nam es come from a Galaxy

Bundle and Send Patches To Device is the selected comm and ,

Galaxy sends the bun dled patches to the selected device.

SHOW CHANNELS Show Channels controls whether the Nam es Wind ow d isplays onerow per MIDI channel or a single row representing all MIDI chan-

nels. To assign d ifferent device mod es to different MIDI chann els,

this option m ust be enabled (checked). For m ore information, see

Channel and Device Mode Colum ns (pg. 9).


15/35

Ch 3: Patch Name Editing Using the OMS Name Manager pg. 15

CH 3: PATCH NAME EDITING

Use the Patch N ame Editor to display or edit Patch Nam edocuments.

OPENING THE PATCH NAME EDITOR

To open a Patch N ame Editor:

In the Names Window, double-click in the Patch Name Documentcolumn next to a device.

Figure 6: Double-click to open a Patch Name Editor

A Patch Name Editor opens for that Patch Name document. TheEditor shows all the Patch Names for that device.

Figure 7: Typical Patch Name Editor


16/35


If you open a Patch Name Editor for an unsubscribed device, a blankPatch Name Editor opens, which you may use to create a PatchName document. Documents created this way are called Typed-InPatch Name documents.

NOTE: If a Patch Name document contains multiple device modes,the Patch Name Editor displays names only for the selected chan-

nels current device mode. For more information, seeChannel andDevice Mode Columns (pg. 9).

PATCH NAME EDITOR ANATOMY

Figure 7 shows the various elements in the Patch Nam e Editor.

These are:

MIDI Program Number: The MIDI column in the Patch Nam eEditor displays MIDI representations of patches in the form bank0/

bank32/ patch n um ber (0-127). For examp le, if the current ban k

requires a ban k32 message with value 1 to be sent to access the

patches, each pa tch will have 1/ x as its program nu mber, where x

is the number w ithin the bank.

bank0 and bank32 are each omitted wh en not u sed, which is the case

for the d efault first bank. Consult your synthesizer documentation to

determine how bank0 and bank32 messages affect patch selection.

These nu mbers cant be changed d irectly, and if the Patch Name d oc-

um ent comes from an external librarian, they cant be changed at all.

If the docum ent in question is a Typed-In Patch Nam e document, the

numbers are affected by settings in the Bank Select/ Nu mbering

dialog box. See Bank Select/ Nu mbering (pg. 23).


17/35


Device Program Number: This column show s how the MIDIdevices internal program nu mbering corresponds to the actual MIDI

program number.

For examp le, some devices num ber their internal p rograms 1-128,

which corresponds to MIDI programs 0-127. This results in the pat-

tern shown in Figure 8 in the MIDI and Nu mbers colum n.

The device shown in this examp le, has hu nd reds of internal pro-grams, beginning at n um ber 001.

Figure 8: MIDI and device numbering

Patch Name: This column shows th e name of each p atch. New p atchnames can be typ ed d irectly into this column if this Patch N ame d oc-

um ent w as created in th e Nam e Manager (i.e.: Galaxy and other

librarian d ocum ents cant be ed ited from here). These nam es app ear

wh erever patch nam es are seen in any OMS 2.0-comp atible

application.

GM Equivalent: If this patch corresponds to a General MIDI patch,choose the relevant GM p atch from the pop-up m enu in th is column .

The Nam e Manager ap plies all attributes and benefits of General

MIDI group ings to that patch.

For example: assume you have a piano soun d in your Patch Name

docum ent, and you assign Grand Pno1 as its GM Equivalent. Then,

if you choose to display patch names by General MIDI Groups, this

piano sound app ears whenever you ask to see all the piano sound s

in your MIDI device. For more information about selecting patches

by General MIDI Group, see Using Patch Grou pings (pg. 28).

This column numbers patches as theyappear in the actual device.


18/35


Note Name Indicator: The OMS Nam e Manager can store customMIDI note names along with patch names. Custom n ote names have

many uses. For example, names can be assigned to the notes in a

drum kit patch, causing Visions edit wind ows to d isplay notes

nam ed kick, or snare, instead of C3 or D3.

This colum n u ses a small note icon to indicate that a p atch has

custom note nam es. The Note Nam e Editor can be opened by

double-clicking in this column. For more information, see Note and

Control Nam es (pg. 24).

Control N ame Indicator: The OMS Nam e Manager allows storage ofcustom MIDI control names along with the name of the patch.

Custom control names have many uses. For example, a MIDI effects

device might use MIDI control nu mbers to ed it its internal param e-

ters. By entering custom control names, Visions edit windows

display controls nam ed Reverb Time, or Pre-Delay, instead of

Control 48, or Control 37, making it easier to edit these d evices

with in Vision (or any other OMS 2.0-comp atible app lication).

This colum n ind icates that a patch has custom control nam es if itcontains a sm all knob icon. The Control Name Editor can be opened

by double-clicking in this column . For more informat ion, see Note

and Control Nam es (pg. 24).

Program Selector Dot: If you are pasting nam es into a typed-inname docum ent, you can select the range w here the nam es will be

pasted by shift-clicking or dragging over the Program Selector Dots.

If no d ots are selected, nam es are pasted starting at the top and

working d own un til the nam es on the Clipboard are exhau sted. See

Paste N ame List (pg. 20) for more information.


19/35


PATCHES MENU

The Patches Menu is available whenever a Patch Editor is active.

Figure 9: Patches Menu (Macintosh Version)

NOTE: Most of these menu items apply only to typed-in Patch Namedocuments; theyre disabled for Patch Name documents that comefrom other applications, such as Galaxy.

SAVE Choose this command to save any changes youve mad e to the cur-rent Patch Name document. If youve previously saved a docum ent,

then the Save comm and replaces the old document w ith the new

version. If you havent yet saved the active document, choosing Save

opens the Save As dialog box, in w hich you name the docum ent and

select a location in which to store it.

This comm and behaves differently depend ing on where the docu-

ment comes from:

Typed-In Patch Name documents are saved normally. Docum ents from Galaxy or other OMS-compatible Patch N ame pro-

viders are converted to Typed -In Patch Name d ocuments. For this

reason, the Save command is not available when you are in a librar-

ians document. In th is situation, only the Save As comman d is

available.


20/35


SAVE AS Use this comm and to save a copy of the active document using a d if-ferent n ame. Choosing Save As open s the Save As dialog box, in

wh ich you nam e the docum ent and select a location in which to store

it.

SAVING NOTE /

CONTROL NAMES

If Note or Control Names have been ad ded to a document created by

another ap plication, the Save N ote/Control Names commandbecomes available. This comm and adds the note and control nam e

information to the saved Patch Nam e document.

COPY NAME LIST Choose Copy Name List to copy the list of Patch N ames from aPatch Nam e document onto the Clipboard .

Nam es are copied to the Clipboard as text, and can be pasted into

other applications. For example, you can p aste names into a w ord

processor or database to format, search, or pr int nam e lists. Each line

is copied as:

Patch Number Patch Name

PASTE NAME LIST Choose Paste N ame List to copy text from th e Clipboard into thePatch Name Editor. If the lines of text conta in tabs, they are inter-

preted as:

Patch Number Patch Name

Otherwise, each line of text becomes a patch nam e. If you h ave

access to a scann er and OCR (optical character recognition) software,

you can scan p atch name lists for your synthesizers, convert them toword processing files, then p aste them into the Patch N ame Editor.


21/35


If any p atches in the Patch Name Editor are selected (tha t is, their

selector d ots are black), then pasting names overw rites only the

selected p atches. For examp le, if you have ten patch n ames on the

Clipboard , but select only th ree patches, only the first three nam es

on the Clipboard are used (see Figure 10).

Figure 10: Only patches 1-3 will be pasted over, no matter how manynames are on the Clipboard

CLEAR NAME LIST This command erases the currently selected name list, should youwish to start with a clean slate.

ADD MODE Choose Add Mode to create an entirely new device mode for thedocument, and open a new window to display it.

REMOVE MODE Choose Remove Mode to delete the device mode displayed in the

active window.

MODE NAME Choose Mode Name to nam e (or renam e) the device mod e displayedin the active window . The mod e name appears on the top line of the

window.

Mode name


22/35


DEFAULT MODES Choose Default Modes to open a window in which you select adefault mod e for each channel. Whenever this Patch Name docu-

ment is subscribed, the chann els are set to the mod es designated in

this window .

For example: General MIDI devices have two m odes: standard an d

drums. Channel 10 is always in dru ms m ode, and all other channels

are in standard mode. Figure 11 shows the default mod e screen setup for a General MIDI device.

Figure 11: Default Mode Window

ADD BANK Choose Add Bank to create a new bank of 128 patches following thebank containing the currently selected patch, or at the end of the doc-

um ent if there is no selected p atch. When you choose this comm and ,

the Bank Select/ Nu mbering d ialog box opens as discussed in Bank

Select/ Nu mbering (pg. 23).

REMOVE BANK Choose Remove Bank to d elete the bank in which th e selected p atchresides.

NOTE: If the device has less than 128 patches in a bank, leave theunused patches blankblank patches wont be displayed in patchselection menus and dialog boxes.


23/35


BANK SELECT/NUMBERING

Add ing a bank or choosing the Bank Select/Numbering command

opens the Bank Select/ Nu mbering d ialog box:

Figure 12: Bank Select/Numbering dialog box

Figure 12 displays the various elements in the Bank Select/ Nu mber-

ing dialog box. Specifically:

A Bank Select message may be specified by checking one or both ofthe Bank Select checkboxes, and by entering a bank select value inthe box to the right. Consult your synth esizer docum entation to

determine the app ropriate values for these boxes.

IMPORTANT: Each bank must have a unique combination of bankselect messages. A warning message appears if two banks have thesame bank select combination.

If the Automatically number patches in bank opt ion is checked, thepatches are automatically nu mbered according to the selected num -

bering convention:

0-127: Used for synthesizers with a 0 based nu mbering convention

1-128: Used for synthesizers with a 1 based nu mbering convention

A11-B88: Used for synthesizers with a ban k based num bering con-

vention (most Roland devices use this scheme)


24/35


Patch p refixes can be entered in the Prefix box. For examp le, a synthmay u se banks with names such as RAM1. The p atches could be

nu mbered RAM1-0 thru RAM1-127 by entering RAM1- in the

Prefix box and selecting 0-127.

Figure 13: Using the Prefix feature

If the Assign GM equivalents to all patches opt ion is checked , eachpatch is assigned a General MIDI patch equ ivalent. This sets each

patches nu mber equal to the GM equivalent. This is useful to config-

ure a bank to match the GM defaults withou t changing the names.

NOTE AND CONTROL NAMES

Double-click the Cntls colum n in the Patch Nam e Editor to open a

Control Names Window. Similarly, double-click the Notes column

to open a Note Names Window.

Figure 14: Note Names Window


25/35


Saving note names or control names adds them to the Patch Name

docum ent, regardless of whether it is typed -in or from another

application.

Note nam es are useful for dru m m achines or samp lers. For example,

its easier to ed it MIDI data for a d rum machine if notes appear in the

sequencer nam ed Kick or Snare rather than C2 or D2. Simi-

larly, if youre using a sampler to trigger sound effects, notes namedCrash or Gunshot are more useful than notes named G3 or

D5.

Control names are useful if you use a sequ encer to p erform real-time

edits to synth esizer of effects patches. For example, its easier to ed it

controllers named RevTime or H PFiltr than controllers named

Control 41 or Control 73.

DEFAULT NOTEAND CONTROL

NAMES

At the top of every Patch N ame d ocum ent is a line marked Default.

You can ad d a set of default note and controller names to a Patch

Nam e document by dou ble clicking in the app ropriate column and

typing names into the Note Nam es Wind ow or Control Nam es Win-

dow . These default Nam es are used for every patch that d oesnt

specifically override them.

Figure 15: Default Note and Control Names

In Figure 15, there is a set of default Note Nam es. All the patches in

this bank use these note names. How ever, the note icon in the row

for p atch num ber 2 ind icates that it has its own set of Note Names

that override the d efaults.

Default Note and Control Names row


26/35

Ch 4: Selecting Names in OMS-Compatible Applications Using the OMS Name Manager pg. 26

CH 4: SELECTING NAMES IN OMS-

COMPATIBLE APPLICATIONS

Once the Name Setup is configured prop erly, your OMS-comp atible

app lication d isplays names in all the appropriate places.

There are two w ays to view patch names in an OMS 2.0-comp atible

application:

The Patch Name Menu

This is a simple pop -up m enu of choices that app ears when you click

in a nam e field. For more informat ion, see The Nam e Browser

(pg. 27). The Name Browser

The Name Browser is a more soph isticated w indow that allows you

to view nam es num erically or alph abetically, or to group them by

keyword or patch type. For more information, see The Nam e

Browser (pg. 27).

The following sections d iscuss these two patch m enu method s in

detail, beginning with th e Nam e Browser.


27/35


THE NAME BROWSER

To open the N ame Brow ser in an OMS 2.0-comp atible app lication:

If youre using Windows, Control-click or Alt-click a name field toopen the Name Browser.

If youre using a Macintosh, option-click a name field to open theName Browser.

Figure 16: Opening the Name Browser

Select the desired patch from the right-hand scrolling patch namelist.

The selected patch is automatically called up in the actual MIDIdevice.

The Name Browser gives you many ad ditional viewing op tions, as

discussed in the following section.

MAC: option-click here...

WIN: alt-click (or control-click) here...

... to open the Name Browser


28/35


NAME BROWSERANATOMY

As shown in Figure 16, the Name Browser contains three elements.

These are:

Grouping area: Use this area to organize patch nam es into grou pswith common characteristics. For more information, see Using Patch

Groupings (pg. 28).

Patch list: Use this scrolling list to select a pa tch. The selections you

make in the Grouping area determine wh ich patch nam es appear inthis list.

Display options: To view patches alph abetically, click the By nameradio button. To view patches numerically, click the By number

rad io button. The selection you make is global and app lies to all

places where patch names are displayed.

USING PATCHGROUPINGS

Use the Grouping pop-up menu to organize patch nam es into

group s w ith common characteristics. For examp le, the General MIDI

Patch Name document contains three groupings:

None: Select this option to view all the patch n ames in the scrollingright-hand Patch list.

Figure 17: Viewing All Patches (No Grouping)


29/35


General MIDI Groups: Select this option to produce a list of group s

that contain patches with comm on soun d characteristics. When you

select a grou p, the Patch list displays all the patches in that g roup .

Figure 18: Viewing Patch Names by General MIDI Groups

General MIDI Patches: Select this op tion to p rod uce a list of General

MIDI patches (with full length nam es). When you click a n ame in the

Group list, the Patch list displays all the patches of that type.

Figure 19: Viewing Patch Names by General MIDI Patches

EXAMPLE:

Selecting Strings from theGroup list displays only string

patches in the right-handPatch list.


30/35


CREATING CUSTOM GROUPINGS

Custom group ings can be created with Galaxy, Opcodes patch

librarian by ad ding keyword s to your Bun dles. Also, Galaxy au to-

matically provid es useful group ings for certain synthesizers.

Group ings cant be created for Typed -in Patch Name d ocuments, but

the General MIDI group ings can be u sed by selecting General MIDI

equivalents for each p atch.

NAME BROWSERSNAMES MENU

When u sing the Name Browser, the Names menu shown in

Figure 20 becomes available.

Figure 20: Name Browser Menu

SORTBY NUMBER / SORT BY NAME

These comm and s du plicate the function of the By Name an d By

Number rad io buttons in the Browser Wind ow.

SHOW PATCHES IN ANY / ALL SELECTED GROUP(S)

With Show patches in any se lected group checked, shift-clicking

mu ltiple group ings in the Nam e Browser d isplays patches belonging

to any of the selected group s.

NOTE: For those with programming experience, this enables anOR

condition between multiple groups.

With Show patches in all selected groups checked, shift-clicking

mu ltiple group ings in the N ame Browser d isplays only patches

belonging to all of the group s.

NOTE: For those with programming experience, this enables anANDcondition between multiple groups.


31/35


For example, imagine there are groupings for bright and piano.

With Show patches in all selected groups checked, only bright

pianos are listed. With Show patches in any se lected group

checked, all bright patches and all piano p atches are listed together.

EDIT SELECTED PATCH

This comm and opens the Patch Nam e documents creator to edit the

selected p atch. (This command is not available when th e active Patch

Name document is a typed-in patch name d ocum ent.)

PLAY

If youre ru nn ing an OMS 2.0-compatible app lication, choose this

comm and to trigger its playback from w ithin the active application.

STOP

If youre ru nn ing an OMS 2.0-compatible app lication, choose this

comm and to stop its playback from w ithin the active app lication.


32/35


THE PATCH NAME MENU

You can view and select patches in an OMS 2.0-compatible app lica-

tion without op ening the Name Browser. To do so:

Click in a Patch Name field to open the Patch Name menu.

The menu that opens depends on how you last configured the NameBrowser.

If the Name Browser was last used with a Grouping of None, thenthe patch name menu contains the names of all the patches for theselected MIDI device (as shown in Figure 21).

Figure 21: Opening a Patch Name Menu (No Groupings)

If the Name Browser was last used with a Grouping, then the PatchName menu contains the names of all the groups with sub-menuscontaining names of patches within the groups (as shown inFigure 22).

Click here...

... to open a menu containingall the patch names for theselected device.


33/35


Figure 22: Opening a Patch Name Menu (With Groups)

Select the desired patch from the patch name menu.

The selected patch is automatically called up in the actual MIDIdevice.

OPENING FILES WITH DIFFERENT NAME SETUPS

Vision saves Name Setup s in its sequence files. When opening a file

containing a d ifferent Name Setup , the Name Manager needs infor-

mation to d etermine how to h and le the different assignments. This

section discusses the possible options.


34/35


The following d ialog box appears w hen the new sequ ence is opened

with a d ifferent Name Setup :

Figure 23: Different Name Setups - first dialog box

The following sections d escribe the tw o possible choices.

MAKE CURRENT This choice overrides all current N ame Setup information w ith theinformation from the file being opened .

It is normally desirable, wh en changing N ame Setup s, to send the

new patches to the synthesizers. The Nam e Manager an ticipates this

behavior by p resenting a d ialog box similar to the following:

Figure 24: Getting Ready To Send dialog box


35/35

At this point you shou ld make sure that the correspond ing patches

are loaded in the app ropriate devices.

ClickGo Back to return to the previous d ialog box.

DONT MAKE Clicking Dont Make leaves the current Nam e Setup u nchanged , butpresents another d ialog box with three choices:

Keep the document u nchanged without m aking its Name Setup

current.

Change the docum ent to use the current Nam e Manager subscrip-

tions. Saving the file without changing its name destroys any record

of the old su bscriptions.

Go Back return s to the previous d ialog box.

Figure 25: Dont Make Current dialog box