Windows®, Windows XP®, Windows Vista® and Windows 7® are registered products of the Microsoft® Cooperation.

The General MIDI System Level 1 and Level 2 specifications (GM, also GM1 and GM2) are owned by the MIDI Manufacturers Association (MMA).

XG™ is a registered trademark of Yamaha Corporation.

GS™ is a trademark of Roland Corporation.

Manual

MIDI output device strips
MIDI output device parameter
Track controls
Karaoke
Settings
List editor
ML's Internal Sound Generator
Audio record
Wave editor

MIDI output device parameter

The first thing you should do if you have installed MIDI Locator is to configure your MIDI output devices. The most parameters don't need to be changed, but set the right "Supported MIDI standards" parameter. This only has to be done once, MIDI Locator will remember this configuration in the future.

After you have opened the MIDI output device, click on it's Parameter-button and the parameter dialog of the device opens.



Supported MIDI Standards

It is important to set this parameter, because MIDI Locator wants to prevent you from sending MIDI events of a MIDI standard to a device, which doesn't understand them.

Unless MIDI Locator doesn't get the right device's "Supported MIDI Standard" configuration of a device which is able to understand GS, XG or GM2, it will filter out too much of GS, XG and GM2 sequences and shrink them at output to a naked GM-sequence.

Therefore, set the parameter for devices which are GS, XG or GM2 compatible.

Set all relevant "Supported MIDI Standards" check marks. Look into your MIDI device's manual if you are not sure. You can also select multiple standards but either GS or XG. Because they are competing standards of ROLAND and YAMAHA devices. If you load and play a MIDI sequence with MIDI events of a MIDI mode which wasn't enabled here, MIDI Locator will tell you that a song isn't compatible to your device, at load time - and flashes a red light, and higher-level MIDI events in your song are suppressed, at playtime.

You can also select combinations of different MIDI modes, if your device really understands different modes.

MIDI Locator supposes that every MIDI device is able to understand at least the standard GM MIDI mode (that channel 10 is a drum channel and so on), so this checkbox is always marked and disabled for unchecking.

Power on MIDI mode

The "Power on MIDI mode" is important for telling which MIDI mode should be entered at your device, if MIDI Locator is starting up. Or if a device is fresh opened by the MIDI Device plug-icon click in the menu bar. MIDI Locator then sends a GS-reset, XG-reset etc. whatever you have selected here.

If you have external MIDI devices (Yamaha, Korg or Roland keyboards etc.) connected to your system and you go to use and open such device inside MIDI Locator, always turn your device on before you start MIDI Locator. Otherwise the automatic sent Power-On reset has no affect, and there could be a mismatch between the actual current MIDI mode in your device and the controller and program names MIDI Locator is thinking about to be active.

Running status supported

Always check the "Running status supported" checkbox, because nearly every device supports it. It says the MIDI data flow to your device can be reduced to a minimum. Older MIDI devices didn't understand such transfer. If you have set the check mark, and your devices doesn't respond to anything in a normal way, just remove the mark again. This is the reason why it is delivered unchecked. It would be confusing if you are a new user, try to play a sequence with a MIDI output device a first time which doesn't understand it, and you hear nothing usefull.

Universal realtime and non-realtime Device ID

Two hexadecimal characters defining the Device ID. This Device ID should enable you to target different physical devices behind one "MIDI output device", if you have chained different physical MIDI devices by MIDI cables. So you could set different device IDs at your physical sound modules and the one would respond which carries the sysex message's device ID. All universal realtime sysex messages (like GM reset, GM2 reset, Keybased instr. controller etc.) have to name it.

So the device ID you entered here will be automatically taken and named if you insert a new GM or GM2-sysex event inside the list editor.

Also the Device ID will be taken if you define the type of a controller-knob to a GM2-keybased instrument controller and send it by turning the knob. Or if you send a GM or GM2 mode reset with the "MIDI mode" button on the device-strip.

Existing Device IDs in a loaded MIDI sequence are not exchanged in realtime if you only change this "universal Device ID"-parameter and play the sequence! You need to exchange it in every relevant existing sysex-message in the list editor, if you want to change it (SyxDevId).

Set this value to 7F for default behaviour (target all devices).

Non-universal Device ID

One hexadecimal character (if "XG supported" is checked) or two hexadecimal characters (if "GS supported" is checked) defining the Device ID used if you insert a new GS or XG-sysex event the sequence.

Also this Device ID is used if you define the type of a controller-knob to a Common Controller, NRPN or Drum NRPN and you turn the knob while the device is in GS or XG mode. Or if you send a GS or XG mode reset with the "MIDI mode" button and by the "dirty controller adjustment" when you start a sequence.

Like with "universal Device ID" existing Device IDs in a MIDI sequence are not exchanged in realtime only by changing this parameter.

Set this value to 0 if the device supports XG or to 10 if the device supports GS for default behaviour (target all devices).

Non-universal Native Model ID

Only for XG supporting devices

Two or four hexadecimal characters preserved for future use. Currently without function.

MIDI Locator's Internal Sound Generator - MIDI channel / DirectSound device - map

This parameter is only enabled on the dialog of the "MIDI Locator's Internal Sound Generator" device parameters.

"MIDI Locator's Internal Sound Generator" is a sample-player which allows it to play own .wav files triggered by "Note on" events. Here you can select the "wave output device" of Windows which has to be used for notes of a specific MIDI channel. You could drive .wav files triggered by MIDI channel 1 to another wave device than .wav files triggered by MIDI channel 2 for example (or you could use same wave device).

In addition, you can specify a note-key for each MIDI channel if you want. So it is possible to drive different drum key notes to different wave devices.

You can create several entries for one MIDI channel, to list all MIDI channel/key combinations you need.

If you want to drive all keys of a MIDI channel to the same wave device, select the * (joker) device.

The entries are red in order of appearance, the first true combination MIDI Locator finds for a triggered key of a MIDI channel will be taken.

So if you first list several key-specific .wav devices you should enter the * combination at the end, to catch all remaining keys.

Don't set the * in the first entry, if you specifiy different keys. The keys would never be checked, because MIDI Locator would find a valid entry with the * combination.

If a MIDI channel is not used for rythm, allways enter only one entry: MIDI channel/*.

If there is no entry for a MIDI channel and a "Note on" is triggered, the "MIDI Locator's Internal Sound Generator" will give a warning message in it's display.

GM2 Global parameter control

Only enabled if you have set a mark into the "supported MIDI standard" GM2-checkbox.

In GM2 the GS- and XG-non-universal sysex messages which control effects and different device-internal-parameters are sorted out into regular universal sysex messages.

Those messages are organized in slotpathes. There is one slotpath for reverb effects, one slotpath for chorus effects etc. The slotpath is a simple 4 digit "street-number" where multiple paramters are grouped. This "street-number" and the parameter-number for each parameter inside a group is defined by the "MIDI Manufacturer association" and no invention of MIDI Locator. You can see all supported slotpathes and parameter numbers in your GM2 device manual.

For example "Reverb time" can be found in slotpath "0101", parameter number #1. In all GM2-devices.

So if you check the GM2-supported checkbox, the MIDI Locator-known slotpathes and parameter-number of GM2 are declared for you, visible and editable here in the "GM2 Global parameter control" area of the device parameters. You can see 2 selectable slotpathes and its parameters.

If GM2 will be expanded, or if your GM2-device knows more than the shown parameters, you can expand them here for beeing translated in MIDI Locator's list editor.

But please be carefull with "unchecking" the GM2-support checkbox, because the definitions are not needed anymore and will be erased again.

There are two different kinds of GM2 global parameters: type lists and free values.

For example the kind of the reverb-type-parameter of slotpath "0101 Reverb" is type-list, because you only can select between different specified "reverb types" later, if you insert the sysex-message into your sequence (room, hall etc.).

The "reverb time", for example is a free value, because you cannot only select predefined single reverb times later, you can set a flowing integer value between 0 and max reverb time.

If you switch the kind of a new parameter to "free value" you have to enter the unit (only a simple free text which will be placed beside the calculated result) and the formula, which defines how MIDI Locator should calculate the "real world value" by the entered value later in the list editor.

For example, the formula of reverb time is "2.71828^((val-40)*0.025)" where val is the actually stored value-part of the sysex-message "GM2 reverb time".

So if you later insert the value 33 in a GM2 global parameter sysex for parameter reverb-time, MIDI Locator will calculate and show the result: 0.83 seconds.

The value actually sent value to your device will be 33. But your GM2-device will adjust the reverb time to 0.83 seconds.

Always use "val" as the placeholder for the stored (and editable) value. The calculation of the "real world value" uses simple left to right arithmetic, please don't suppose automatic multiplication-leads-addition-order. If you want an order of an expression please use brackets.

The list editor will later show the stored integer value of "val", the calculated result and the unit all together in the row of your sysex-event message.