Akai MPK249 MIDI Test

Akai MPK249 MIDI Test: Dead Keys, MPC Pads, and Arpeggiator Check

For the MPK249, start by connecting the USB-B cable before opening this page. Chrome can read it as a class-compliant MIDI device with no driver installation.¹ Click "Enable MIDI", approve permission, and the keyboard appears in the dropdown. Akai ships the MPK249 with 49 semi-weighted keys, 16 velocity-sensitive MPC pads with aftertouch, 16 assignable knobs, and a built-in arpeggiator and chord mode that can generate multiple MIDI messages per keypress.

The arpeggiator is on by default in some factory presets. When active, holding one key generates a rapid sequence of Note On and Note Off events in the event log. This looks similar to ghost notes but is the arpeggiator working as designed. Disable the arpeggiator (ARP button LED off) before running the dead-key sweep to ensure that each key press produces exactly one Note On and one Note Off per physical press.

Specifications¹

Connection and browser setup

Connect the MPK249 via USB-B (the square printer-style connector) before opening this page. Chrome detects it as "MPK249" in the MIDI input dropdown after you grant MIDI access.²³ If a MIDI DIN device is connected to the 5-pin output, it appears as a separate entry. Select the USB entry for direct keyboard testing.

Separating USB and DIN inputs

Choose the USB entry when testing the MPK249's keys and pads. A DIN source connected to the 5-pin output is useful for external gear checks, but it can look like a second keyboard in the dropdown. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

Close Akai MPC Beats or any DAW before testing to avoid exclusive port conflicts. The keyboard powers from USB. Hot-plugging is supported. Disconnect and reconnect at any time and the dropdown refreshes automatically. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

Common issues with this model

The built-in arpeggiator generates rapid Note On bursts that mimic ghost notes in the event log. If the ARP button LED is on, every held key produces a stream of Note On events at the arp rate. Disable it before testing and confirm the log shows exactly one Note On per key press. Similarly, Chord mode generates multiple simultaneous Note On events per physical key press. Disable Chord mode (CHORD button LED off) for a clean dead-key sweep.⁴

The USB-B port can loosen over years of cable plug-in cycles. A loose USB-B port causes intermittent MIDI dropout. The keyboard drops from the MIDI input dropdown mid-session. Try a different USB-B cable first. Furthermore, the 16 MPC pads have aftertouch: pressing harder after the initial pad strike generates additional MIDI events, which appear in the event log as follow-up messages after the Note On.

What the test covers

With the arpeggiator and Chord mode disabled, the virtual piano reflects each physical key press directly. Press all 49 keys and identify any that remain dark. Dead contacts do not transmit Note On at any pressure. The event log shows note number, velocity, channel, and lag for each event. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

Confirming pads and knobs after the key sweep

The 16 knobs generate CC messages on rotation. The data wheel generates CC 06 by default.⁵ The 16 MPC pads generate Note On events with velocity and aftertouch. Tap each pad and watch the event log for the Note On; press harder after the initial strike to see the aftertouch data (0xA0 polyphonic aftertouch messages).⁶ Because this keyboard has both USB and MIDI DIN outputs, the DIN output appears as a second MIDI device in Chrome if a DIN cable is connected.²

Polyphonic aftertouch and arpeggiator timing verification

Testing polyphonic aftertouch on the MPK249 pads requires a different approach from velocity testing: to test MPK249 poly aftertouch per pad, tap a pad at normal velocity to generate the initial Note On, then press harder on the same pad surface without releasing. The event log should show a 0xA0 (Polyphonic Key Pressure) message with the note number of that specific pad and a value increasing from 0 as you apply more pressure. Each pad has its own aftertouch sensor, so the 0xA0 message carries the individual pad's note number rather than a global channel pressure value.⁴

Check all 16 pads for aftertouch response by repeating this on each one. Pads that generate Note On events but produce no 0xA0 messages at any pressure have failed aftertouch sensors. Pads that require extreme force before any 0xA0 message appears have sensors with high threshold settings; adjust pad sensitivity through the Akai MPC Beats companion application.

Arpeggiator timing accuracy via event log timestamps

With the arpeggiator enabled and a key held, the event log timestamps let you verify arpeggiator rate accuracy. At 120 BPM with 1/8 note rate, consecutive Note On events should arrive approximately 250 ms apart. At 1/16 note rate they should arrive approximately 125 ms apart.⁷ Consistent drift in the timing suggests the arpeggiator clock is decoupled from USB MIDI timing rather than running at the correct rate.