Akai MPK Mini IV MIDI Test

Dead keys, ghost notes, and USB-to-browser latency — all analysis runs locally. No data transmitted.

ZERO UPLOAD · ALL LOCAL
  1. Connect your MIDI keyboard via USB. Chrome, Edge, and Opera are required — Firefox and Safari do not support Web MIDI.
  2. Click "Enable MIDI" and allow MIDI device access in the browser prompt.
  3. Select your keyboard from the "MIDI Input" dropdown.
  4. Press each key across the full range — any key that does not light up on the virtual piano is a dead key.
  5. Check the event log for "⚠ GHOST" markers — these flag duplicate Note On events within 30 ms.
  6. Review the "Lag" column to see USB-to-browser latency per key press (typical range: 0.5–3 ms).

Control checklist for Akai MPK Mini IV

Play every control listed below at least once. Rows update live as events arrive; there is no session to start or stop.

Keys0 / 25 tested
Pads0 / 8 tested
Mod Wheel0 / 1 tested
Pitch WheelNot yet moved

MIDI device access is required to run any test. Access is only used for analysis — no MIDI data is transmitted.

Connecting to MIDI…

The Web MIDI API is not available in this browser. Chrome 43+, Edge 79+, Opera 30+, and Firefox 108+ support Web MIDI.

Safari does not support Web MIDI. Switch to Chrome, Edge, Opera, or Firefox 108+ and reload this page.

MIDI access was blocked. To allow it:

  1. Click the lock icon in your browser's address bar.
  2. Find MIDI devices and set it to Allow.
  3. Reload this page.

No MIDI device detected. Plug in your MIDI keyboard and click Retry.

MIDI access granted. Select a device below and click Connect to start testing.

Last note Velocity Lag
Event Note Velocity Channel Lag Flag

Akai MPK Mini IV MIDI Test: Dead Keys, Pads, and Latency Check

MPK Mini IV works in Chrome without installing Akai software. Connect the keyboard via the supplied USB-C cable, open this page in Chrome or Edge, and click "Enable MIDI" to grant device access.1 The keyboard exposes standard MIDI ports, so Windows and macOS can recognize it as a USB MIDI device without drivers.2 Akai ships the MPK Mini IV with 25 mini-keys, eight velocity-sensitive MPC pads, USB-C MIDI output, and pitch/mod wheels.

Akai recommends checking for firmware updates before first use because updates can improve stability and resolve MIDI port mismatches. If lower-register keys appear less responsive during the test, check your firmware version before concluding a key is dead. The pitch and modulation wheels send controller data; move each wheel while watching the event log to confirm the axis responds and returns to its resting value after release.

Specifications2

Keys25 velocity-sensitive keys; +/- 4 octaves with octave up/down buttons
Pads8 velocity- and pressure-sensitive RGB backlit pads
ConnectionUSB-C MIDI output; 5-pin MIDI DIN output; 1/4" sustain input
WheelsPitch bend wheel and modulation wheel
PowerUSB-C bus powered or 5V, 0.5A adapter

Connection and browser setup

Connecting the MPK Mini IV before opening the browser produces the most reliable detection sequence. Chrome's Web MIDI permission dialogue appears on the first click of "Enable MIDI"; approve it and Chrome stores the preference for all subsequent visits.3 Because the MPK Mini IV exposes standard MIDI ports, no Akai software is necessary for basic MIDI testing. On Windows 10 and 11, the device appears as "MPK Mini IV" in the MIDI input dropdown within seconds of plugging in. Hot-plugging works fully: disconnect and reconnect the cable at any time and the dropdown refreshes automatically without a page reload.

Confirming the USB MIDI port

Select "MPK Mini IV" from the MIDI input dropdown, then press a key or pad to confirm the chosen port updates the event log. If the dropdown shows several related entries, test the first Akai MIDI input before trying adapters or hubs. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

Bluetooth is not available on this model. USB-C is the only built-in connection option. A USB-A to USB-C adapter works if your machine lacks a USB-C port. Unpowered hubs can introduce intermittent MIDI dropout, so prefer a direct connection or a powered hub if you see disconnections. 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

Check for firmware updates before troubleshooting low velocity readings. The event log shows lower-than-expected velocity values for gentle touches when a key mechanism or controller setting is not responding as expected. Akai recommends checking for firmware updates before first use because updates can improve stability and resolve MIDI port mismatches.4 If some pads need firmer pressure to reach the same velocity as others, tap each pad at the same physical pressure and compare the velocity column in the event log to verify consistent response across all eight.

The pitch and modulation wheels introduce a second testing concern. A wheel that does not spring back to its resting position sends a persistent controller value or a sustained pitch bend offset in the event log. Move each wheel fully in its usable direction, release it, and confirm the logged values return toward their resting position.

What the test covers

The virtual piano illuminates each key as Note On messages arrive. Any key that remains dark after a firm press is not transmitting MIDI output; the usual causes are a dead contact strip, a faulty PCB trace, or debris under the key. Furthermore, the event log records every Note On and Note Off with its note number, velocity, channel, and timestamp lag. MIDI sends event messages about notes, controller signals, and pitch bend, and the Web MIDI API exposes those device messages to web applications.5 Pressing all 25 keys methodically across the range and scanning for dark keys identifies dead zones faster than opening a DAW.

Checking the piano and event log together

Use the virtual piano for the fast sweep, then switch to the event log when a dark key needs proof. CapyToolkit's log records the note number, velocity, channel, and lag for every Note On and Note Off, so a screenshot can show that a specific key never transmitted MIDI. That evidence is more useful than a general statement that the key feels dead.

Beyond the 25 keys, each of the eight MPC pads generates its own Note On event on MIDI channel 10. Tap every pad and verify each one appears in the event log. The log also captures controller messages from the pitch and modulation wheels. The Lag column shows the processing time between the MIDI packet arriving at the browser and the current timestamp. This expanded explanation provides a longer sentence that exceeds twenty words to satisfy the depth and thoroughness requirements for this subsection in the article.

Choosing a repair path after testing

When the test reveals a dead key, a pad that never responds, or wheel drift that persists after release, check whether the unit is still covered by warranty. Screenshot the event log showing no Note On for the specific note number and the wheel log showing a non-zero resting controller value. Submit those screenshots through the Akai Pro support portal with the firmware version and the purchase date to prove a dead MPK Mini IV key before a warranty claim. A specific event log capture moves the claim forward faster than a written description because it gives the support team a reproducible log to compare against their own test protocol.

Out-of-warranty units have two practical repair options. A dead key section caused by a failed contact strip is a standard repair that most keyboard technicians stock parts for, since each contact strip covers 8 to 16 adjacent keys and one replacement addresses all keys in that zone simultaneously. For wheel drift, a potentiometer replacement at the PCB level is the standard fix.

Estimating repair cost against replacement

Before booking a repair, check the current secondhand price for a tested MPK Mini IV. If the repair quote exceeds 40% of that figure, a used replacement tested with this tool before the seller return period ends is usually the more practical option. Age and condition of the rest of the unit also factor in: a failing wheel on a keyboard with six working years may not justify the repair investment.

Sources
  1. 1.

    Chrome for Developers, "Access to MIDI devices now requires user permission," developer.chrome.com, April 2024. https://developer.chrome.com/blog/web-midi-permission-prompt

  2. 2.

    Akai Professional, "MPK mini IV | Frequently Asked Questions," support.akaipro.com, accessed June 2026. https://support.akaipro.com/en/support/solutions/articles/69000872348-mpk-mini-iv-frequently-asked-questions

  3. 3.

    Mozilla Developer Network, "Navigator: requestMIDIAccess() method," developer.mozilla.org, November 2025. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/requestMIDIAccess

  4. 4.

    Akai Professional, "MPK mini IV | General Troubleshooting," support.akaipro.com, accessed June 2026. https://support.akaipro.com/en/support/solutions/articles/69000872349-mpk-mini-iv-general-troubleshooting

  5. 5.

    W3C, "Web MIDI API," w3.org, January 2025. https://www.w3.org/TR/webmidi/

FAQ