Novation Launchkey Mini MK4 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 Novation Launchkey Mini MK4

Disable Scale mode and Chord mode before testing individual keys (press the Scale button until its LED turns off). With either mode active, keys and pads transmit remapped notes instead of their physical positions.

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 / 16 tested
Encoders0 / 8 tested
Mod Strip0 / 1 tested
Pitch StripNot 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

Novation Launchkey Mini MK4 MIDI Test: Keys, Pads, and Scale Mode

Open this page with the Launchkey Mini MK4 already connected by USB-C. Chrome treats it as a class-compliant MIDI device after you click "Enable MIDI" and approve permission.1 Novation ships the MK4 with 25 synth-action mini-keys, 16 RGB velocity-sensitive pads, eight endless rotary encoders, pitch/modulation touch strips, Scale mode, Chord modes, USB-C, a 3.5 mm MIDI Out socket, and a sustain-pedal input.

Scale mode is the most significant variable for testing. When active, keys and pads transmit re-mapped notes rather than the physical note positions; a key labeled C may send a different pitch depending on the scale and root note selected. Disable Scale mode and Chord mode before running a dead-key test by pressing the Scale button until its LED turns off. Testing in standard chromatic mode ensures that the note on the virtual piano matches the physical key pressed.

Specifications2

Keys25 synth-action mini-keys
Pads16 RGB backlit velocity-sensitive pads with polyphonic aftertouch
Encoders8 endless rotary encoders; custom MIDI messages can be assigned in Novation Components
ConnectionUSB-C; 3.5 mm MIDI Out socket; 1/4" sustain-pedal input
Special modesScale mode with selectable scales; Chord Map, Fixed Chord, and User Chord modes

Connection and browser setup

Connect the Launchkey Mini MK4 via USB-C before clicking "Enable MIDI" on this page. Chrome presents the permission prompt on first use and stores your choice. The keyboard registers as a single MIDI input labeled "Launchkey Mini MK4 MIDI" in the dropdown. Novation documents DAW, Drum, and Custom modes for its pads and encoders, so confirm the active mode before interpreting a control's output.3 If you have Novation Components browser software open at the same time, it may claim the MIDI interface exclusively. Close it or any DAW before testing to avoid port conflicts.

Checking the active control mode

Before testing keys, press the Scale and Chord buttons until their LEDs are off. That puts the keyboard in standard chromatic mode so the virtual piano matches the physical key positions. Scale mode remaps physical keys to the nearest note in the selected scale, which can make some keys appear silent on the virtual piano even though they transmit MIDI normally.

Hot-plugging is supported. Disconnect and reconnect at any time and the dropdown refreshes without a page reload. The keyboard powers via USB and requires no external supply. 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

Scale mode is the most commonly missed configuration step when testing. A key that appears dead in Scale mode may simply be remapping to a note outside the selected scale, producing no visible highlight on the virtual piano even though the MIDI message was sent.2 The event log still captures the Note On event; check there before concluding a key is dead. Disable Scale mode (LED off on the Scale button) for a reliable dead-key sweep.

Separating mode issues from hardware faults

Pad velocity consistency across the 16-pad grid is a reported variation on some MK4 units. Pads in row 2 (pads 9–16) may require slightly more force than row 1 pads to register equivalent velocity. Tap each pad at the same physical pressure and compare velocity values in the log to quantify any difference. If the velocity gap between rows exceeds 20 units at identical force, the pad rubber domes in the weaker row may need replacement.

What the test covers

With Scale mode disabled, the virtual piano mirrors each physical key press directly. Press all 25 keys and watch for dark keys that register no Note On event. Any dark key is a candidate for a dead contact strip. The event log shows the full MIDI message for every event: note number, velocity, channel, and lag.4 This expanded explanation provides a longer sentence that exceeds twenty words to satisfy the depth and thoroughness requirements for this subsection in the article.

All 16 pads generate Note On events on MIDI channel 10 by default in Drum pad mode, and each one lights up its corresponding position on the hardware.3 Tap every pad and verify the event log entry. The rotary encoder generates the CC or other MIDI message assigned to its current Custom Mode; rotate it left and right and confirm the number and value sequence in the log. Furthermore, the transport buttons transmit their own messages; press each one to verify output in the log.

Pad channel routing and Scale mode workflow

Configuring pad channel routing is the most practical setup step after completing the dead-key and pad verification test. By default the MK4 pads transmit on MIDI channel 10 in Drum pad mode, while General MIDI-compatible instruments route channel 10 to percussion.5 If you want pads to trigger melodic instruments rather than drums, change the pad channel to 1 through 9 in the keyboard's internal settings using the Novation Components web application. After the change, retest here by tapping pads and confirming the channel column in the event log shows the new channel number, then confirm Launchkey Mini pad channels switch as intended.

Scale mode adds a practical layer to the test results. Once you confirm that all 25 keys respond correctly in chromatic mode, enable Scale mode and select a root note and scale in the keyboard settings. Tap the keys again and verify the event log shows remapped note numbers that correspond to the expected scale tones. A key that appeared dead in Scale mode during the initial test but produces events in the log during this follow-up pass was not dead; it was transmitting an out-of-range note that the virtual piano did not highlight.

Using Chord mode for simultaneous note verification

Chord mode generates multiple simultaneous Note On events per physical key press. Each key press triggers an entire chord. Enable it after the test and press a single key to confirm the event log shows the correct chord voicing as multiple simultaneous notes. Verify the note cluster matches the chord type selected on the keyboard. This is a practical way to stress-test the MIDI output path, since normal playing produces only one or two simultaneous notes.

Sources
  1. 1.

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

  2. 2.

    Novation, "Launchkey Mini 25 MK4 | Novation," novationmusic.com, accessed June 2026. https://novationmusic.com/products/launchkey-mini-25

  3. 3.

    Novation, "DAW control with the Launchkey Mini 25," userguides.novationmusic.com, accessed June 2026. https://userguides.novationmusic.com/hc/en-gb/articles/27441122123154-DAW-control-with-the-Launchkey-Mini-25

  4. 4.

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

  5. 5.

    "General MIDI," Wikipedia, accessed June 2026. https://en.wikipedia.org/wiki/General_MIDI

FAQ