MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
111
APPENDIX
A Troubleshooting
Expanders or synthesizers cut notes short for no apparent reason, and controllers are reset
Expanders or synthesizers cut notes short for no apparent reason, and controllers are reset
Expanders or synthesizers cut notes short for no apparent reason, and controllers are reset
Expanders or synthesizers cut notes short for no apparent reason, and controllers are reset
(e.g. volume to maximum).
(e.g. volume to maximum).
(e.g. volume to maximum).
(e.g. volume to maximum).
Problem:
Problem:
Problem:
Problem:
No MIDI message was sent down the cable for 300 milliseconds. The MIDI receiver has therefore
concluded that the MIDI connection has been broken, and switched off what it thinks are droning
notes, and possibly reset itself to its power-up condition (volume to max, etc.).
Explanation:
Explanation:
Explanation:
Explanation:
This bizarre behaviour usually happens because of “Active Sensing” in conjunction with the splitting
of MIDI data across more than one output or the use of data filters.
“Active Sensing” is sent roughly every 200 ms from a master (keyboard, sequencer, etc.) whenever
there is no other MIDI data to be sent. Its purpose is to let any connected instruments know that the
MIDI connection is still intact (a sort of “Hi there! Yes, I’m still here!” message).
The problem arises when a processor (such as an MPXX-W or PMM-88E) using Split or Filter
functions etc. is not allowing all of the data which the master is sending to reach an expander. The
master is happily sending lots of MIDI data (and therefore no Active Sensing), but not all of it is
reaching the expander, which can cause the above problem.
Solution:
Solution:
Solution:
Solution:
You should disable Active Sensing completely. If the master does not let you do this, use a global
Active Sensing filter at the corresponding input of the MULTIPLAYER. This works because a receiver
will only expect Active Sensing if it received it immediately after being switched on or reset.
Transmission of System Exclusive data from the MULTIPLAYER to the synthesizer or expander
Transmission of System Exclusive data from the MULTIPLAYER to the synthesizer or expander
Transmission of System Exclusive data from the MULTIPLAYER to the synthesizer or expander
Transmission of System Exclusive data from the MULTIPLAYER to the synthesizer or expander
is unsuccessful.
is unsuccessful.
is unsuccessful.
is unsuccessful.
Problem:
Problem:
Problem:
Problem:
The instrument is not capable of dealing with SysEx data mixed in with Real Time data.
Explanation:
Explanation:
Explanation:
Explanation:
If one of the MULTIPLAYER’s outputs has been designated as a synchronisation output, it will send
Clock events from this output at regular intervals, depending on the current tempo setting,
regardless of whether or not SysEx is being sent. This is because the MIDI specification makes it quite
clear that Real Time data such as MIDI Clock can be sent at any time, even in between the bytes of a
SysEx message. Even when the MULTIPLAYER is stopped Clock data is always sent, so that any
connected slaves can set themselves to the correct tempo even before a Start command.
Solution:
Solution:
Solution:
Solution:
The Sync function should be de-activated for the output which has the troubled instrument
connected, or the instrument must be moved to an output which never needs MIDI Clock (i.e. no
drum machines, sequencers, etc. on this socket).