
Restrictions
- Displayed workspace area
The workspace display
reaches fix from measure 1 to 600. Nevertheless the time position
of a MIDI event can be layed outside this range and it will even
be played and saved.
- Saving MIDI files back
to disk
If you save a MIDI file back to disk it is always saved as a
SMF file of type 1. You can't save it as type 0 (1 track format).
- Fine controller ajustment
(LSB)
The MIDI specifications define that the value of one MIDI controller,
e.g. such as panorama, could be set by 1 controller event or
a controller event pair (2 controller events belonging together)
:
1. event CONTROLLER / PANORAMA MSB / VALUE 0 - 127
or optional
1. event CONTROLLER / PANORAMA MSB / VALUE 0 - 127 and
2. event CONTROLLER / PANORAMA LSB / VALUE 0 - 127
A controller could be set by only sending the first event, or
both. If a user sends the 2. event, the MIDI device has to understand
it as a fine adjustment of the set value between 0 - 127 in the
first event. In usual MIDI files the 2. event is hard to find.
This is the reason, why MIDI Locator doesn't support controller
LSB's for normal controllers like volume, pan and so on.
Inside MIDI Locator we only work with e.g. one single
panorama controller event, of which value can be set between
0 and 127.
When opening a file with additional LSB values to their correspondig
MSB value, these LSB controller events are simply not loaded.
In worst case this could result in audible steps in controller
flow.
If you manually record MIDI data, LSB's are also kept out. The
MIDI mixer always produces MSB data when turning a knob.
After checking hundrets of MIDIs of foreign authors we think
these LSB controllers are very rare, so they are just kept out.
Nevertheless bank LSB or necessary NRPN LSBs are supported !
- External time master
MIDI Locator does'nt
listen to external time clock signals. MIDI Locator is
always itselfs master. But it can produce a MIDI time clock signal.
See settings.
- Sending MIDI events to different
MIDI output devices at one time
Only one MIDI output device can be accessed at one time. All
tracks can only be routed to one output device.
- Synchronization
MIDI Locator can't
read MIDI files with SMPTE timecode, and can't write a file with
SMPTE timecode. Nor it does listen to incoming SMPTE timecode
at the MIDI input device.
- Sysex restriction
MIDI Locator reads
and displays sysex data of a MIDI file and lets you edit or send
it to the MIDI output device, but it skips incoming sysex data
at the MIDI input device. So it can't record sysex data, nor
manage or send sysex bulkdump banks.
- Selections inside the MIDI
event editor
You can't build selections inside the MIDI event editor. Only
one event can be changed, inserted or deleted at one time inside
the editor (But many could be selected and changed outside of
it).