Alesis ControlPad - Troubleshooting

30
Symptom Cause Solution
Footswitches or triggers
behave in an opposite
manner. For example,
pressing down the
footswitch generates a
Note Off message, while
releasing the footswitch
generates a Note On
message.
Footswitch or trigger
inputs were plugged in
after power was turned
on.
Turn the unit’s power off, wait a moment, and then
turn it on again. Please always make sure that
footswitches and triggers are connected to the
ControlPad prior to powering on the unit.
Notes sustain
continuously.
Stuck notes due to
incomplete MIDI data.
Turn the unit’s power off, wait a moment, and then
turn it on again.
Sensitivity is not set
correctly.
Set the pad sensitivity as described in the “Setting
Global Parameters” section of this manual.
Adjacent pad triggers
when pad is hit.
Edge of pad was hit. If a pad is hit near the edge, it is normal for it to
“crosstalk” with another pad. Hit the center area of
the pad to avoid this.
There is another device
on your computer’s
USB bus.
Try unplugging USB devices (especially high-
bandwidth devices like disc drives) from your
computer.
There is too much delay
or latency between the
time that the pad is hit
and the time that the
sound triggers on the
computer.
Your software’s latency
settings are not correct.
T
ry ad
j
usting the software settings on your computer.
Please note that not all software has these settings.
Please refer to the “Computer Installation” section of
this manual for more information on latency.
When using MIDI-OX
for SysEx transfers, the
ControlPad’s presets
become messed up.
MIDI-OX output
buffer is not set
correctly.
Alesis does not recommend using the MIDI-OX
software application for SysEx transfers. However, if
you choose to use MIDI-OX, please ensure that the
output buffer size is set to at least 2048.