Sysex
System exclusive MIDI messages are translated to eloquent text inside the MIDI editor.
MIDI editor showing sysex
events which are known and sysex events which are unknown
If you open a MIDI file with sysex messages which are not known
by MIDI Locator, they are only not translated to text.
Instead you will see the pure data in hex format in the MIDI editor,
which is editable.
In that case MIDI Locator doesn't know the belonging value's data length, minimum and maximum. It just knows the total length of the full sysex message including the sysex address.
MIDI Locator could then neither show the eloquent
text nor check if a value is right entered inside the MIDI editor.
Roland checksum
When editing a sysex message belonging to messages of the GS standard,
which is known by MIDI Locator and therefore translated
to text the ROLAND checksum is calculated automatically. If sysex
messages are unknown to MIDI Locator and therefore shown
as hexadecimal bytes, you have to calculate checksums of messages
for ROLAND devices and to insert it into your hexbyte sequence
by yourself.
Device ID
When editing a sysex message which is known by MIDI Locator
and therefore translated to text the device ID is alway set to
10h by MIDI Locator. This is because we want to prevent
the user from beeing confused about setting device ID's. Normally
a MIDI device's ID is 10h, if you don't use two devices of the
same model. But if sysex message absolutely don't response confirm
that there is no conflict to the settings inside your MIDI device.
The current version of MIDI Locator knows hundrets of sysex messages but not all of the newest MIDI products. For example equalizer settings are not coded yet. The devices which were taken for programming are Yamaha CBX-K1XG (MU50) and Boss's Dr. Synth (SOUND CANVAS).