All graphics and text on this page and the product "MIDI Locator" © 2000 - 2010 by Frank Rittberger.

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 strips

Open a MIDI output device of your system by the "MIDI plug" icon in the toolbar.



Every open MIDI output device can be used to play your MIDI sequence and stays open inside MIDI Locator and is visible as a "device strip" until you close it.



So, avisible device strip represents an open MIDI output device and allows it to assign this device to any track in the track view.

Devices which were not opened, and which are not visible as a device strip can't be assigened to any track. The MIDI sequence can't be driven to a device which was not opened.

The device strip shows some of the current device states. Such as the current MIDI mode (GM, GS, XG or GM2) or which MIDI channels are currently in use for rythm.

Close a MIDI output device with the "close-cross" on the very right of the device strip. Because you could decide anytime to play a MIDI sequence, one MIDI output device has to be open, at last.

If you load a MIDI sequence, or if you create a new one by the new button, the currently selected default-device will be assigned to all tracks, automatically.

After load, or after creating a new MIDI sequence, every open device can be assigned to any track in the track view. The MIDI sequence's MIDI events of a track will be driven to the assigned device in that track. So you can drive any track of a MIDI sequence to a different MIDI output devices, or you could build groups of tracks which use the same device, or you could use one device for all tracks.

Reselect a track's device with the MIDI output device control in the track view, manually.



Just click on it and select the device.

The selected device information is not saved into the MIDI sequence's track data, automatically. If you selected another default-device when you reload the sequence, the new default-device will be assigned to the sequence's tracks.

MIDI event "META Device name"

So, if you want to save the current track/device assignment into the MIDI sequence, you have to insert the MIDI event "META device name" in such track. You can do this by setting the checkbox "Insert (and remove old) META event 'DeviceName' in the beginning of track" in the device selection dialog if you clicked the MIDI output device control.

Or you can insert such event in the MIDI event list editor, manually. Then you also have to enter the device's name (
value of MIDI event "META device name"). The text has to be the MIDI device's exact name. The name of every MIDI device is written in bold letters to the very left of the device strip, if you opened it.

MIDI Locator will try to open the named device the next time you reload the MIDI sequence, if you have inserted the "META Device name" event and the device is not already open. And it will select the device into the track where it appeared.

Fields of the device strip



  • MIDI Output device: the Windows system's device name of this MIDI output device

  • is default: yes/no: if you have opened more than one MIDI output device at the same time, you can switch any device to be "the default" MIDI output device. But only one device at the same time! If you load a MIDI file or if you create a new MIDI sequence (with the new button in the toolbar), this device will be assigned to all tracks, automatically.

  • MIDI mode: This is the last MIDI mode which was entered by a GM-mode-reset, a GS-mode-reset, a XG system enter or a GM2-mode-reset. Such mode can be entered by sending a MIDI mode-sysex-message to this device by your MIDI sequence. Or you can send such sysex message automatically by a click on the button of the "MIDI mode" field.

  • Supported MIDI standards: You can select which MIDI standard is supported by this MIDI output device inside the device strip's parameters (Parameter button on the device strip). This field only shows which MIDI standards were enabled by you.

  • MIDI Standard used by Trackevents: If you load a MIDI sequence or if you changed a MIDI sequence it is always checked for which MIDI standard fits to it. For example, if you use a MIDI mode reset "XG system enter" or if you use common controllers or bank selections which are only defined in Yamaha's XG MIDI standard, MIDI Locator will show "XG" in this field. If your MIDI sequence uses multiple controllers which are only defined in one MIDI standard and multiple controllers which are only defined in another standard, MIDI Locator has to compromise and will count which controllers appear the most and shows their MIDI mode as standard.

  • Rythm channels/parts: If the current device's MIDI mode is GS or XG, you can see which MIDI channel is directed to which part. And which part mode is "used for rythm". GS and XG sound-producing output ports are "parts", not "MIDI channels". By default every MIDI channel is assigned to the same part-number (MIDI channel 3 to part 3 etc.). Every MIDI channel can be mapped to a part number (which almost reach from 1 to 16). The background idea was a user-direction of mutilple MIDI channels to the same part. Such part mapping is possible by sysex massages in the beginning of a MIDI file. Here you can see which MIDI channels are mapped to which part, currently in your GS or XG device. In non GS- or XG-devices there is not such mapping, MIDI channels are the front-end of the sound-producing unit. But at least in GM2-devices it is possible to switch other MIDI channels than 10 to "rythm". So in GM and GM2 you won't see the "parts" row here, but you can see inverse displayed "rythm" channels in the MIDI channel row.

  • XG variation effect group: Beside Reverb and Chorus, XG compatible MIDI output devices have a 3. build-in effect, the "variation" effect. You can select different effects like flanger, wah wah etc. to this 3. effect-unit, and you can make this variation effect to be a "insert" or "system" effect. All this is possible by sysex-messages. Also there are sysex-messages which allow to define variation-effect-specific parameter's (like room-width etc.). Depending on the variation effect-type the same specific parameters can have different meanings. Effect type-groups have always the same meaning (Reverb group containing effect HALL1, HALL2, ROOM1, ROOM2, ROOM3, STAGE1, STAGE2, PLATE) has always a 1. parameter "Reverb time"). This field shows the current variation effect type group of a XG compatible MIDI output device.

  • Parameter: See topic MIDI output device parameter.

  • Load .igr file: This button is only visible on the device-strip of "MIDI Locator's Internal Sound Generator". An .igr file is a text file with a sample-map. It defines which .wav files have to be played if a specific program is active and you hit a specific key. The .wav files have to stay in the .igr-file's directory. You can edit an .igr file with an included editor: Select the menu-entry "Extras/Internal sound generator .igr file editor". There already exists an included .igr-file/.wav-file set below the "MIDI Locator"-directory in the "igr"-directory which is loaded the first time you start MIDI Locator, automatically.

  • Release .igr: Some data of the mapped .wav files is load to memory in the moment you have loaded the .igr file. To provide a fast access to the mapped samples (otherwise there would be too much latency if you hit a key until the sound is actually streamed from hard-drive). If you don't go to use the opened "MIDI Locator's Internal Sound Generator" next time, but you don't want to close it, you can release the loaded .igr file here.

  • Memory content: Get a list of currently loaded .wav data and .igr mapping.

  • MIDI to .wav: Only full version: With this button you can start to render the MIDI sequence into a .wav file. The same result as if you play the sequence in realtime could be expected in the destination .wav file.