Diagnosing Dead Keys on a MIDI Keyboard

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).

What a dead key looks like in the log

  • MIDI note 60 — no Note On at any pressure
  • first contact starts the timer, second contact stops it
  • one contact works, so every press logs nearly the same velocity

A key that lights up only under very hard presses has a worn but functional contact strip, not a fully dead one.

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

Dead Key Diagnosis: Find Unresponsive Keys on a MIDI Keyboard

Dead keys are keys that send no MIDI output on any press. Diagnosing them takes under a minute in Chrome. Connect your keyboard, grant MIDI access, and press every key in order. The virtual piano lights each key as Note On messages arrive, and any key that stays dark after a firm press is not transmitting. You get the exact MIDI note number for every dead key, which you can report directly to a repair technician or include in a warranty claim.12

A dead key on a MIDI keyboard is almost always a hardware issue, not a software one. The three most common causes are a failed contact strip section (the rubber layer under the keys that completes the circuit on press), debris lodged under the key preventing full contact, or a damaged contact board.34 A browser test distinguishes a dead key from a velocity-related issue. A key that registers only at hard pressure has a worn but functional contact strip, not a fully dead one.

What causes a dead key

Most MIDI keyboards use a two-contact system under each key. The key depresses a rubber dome with two conductive strips: one contact closes early in the press, and the second closes later. The time between the two contacts determines the velocity value.3 When the contact strip fails, one or both contacts stop conducting. A key where neither contact conducts produces no Note On at any pressure. That is the definition of a dead key. A key where only one contact conducts produces a Note On but always at the same velocity, regardless of how hard you press.

Separating dead keys from fixed velocity

A fixed-velocity key is not the same as a dead key. It still sends Note On, but the velocity stays nearly identical because one contact is missing. If the log shows the same velocity on every press, check the contact strip before replacing the whole keyboard. The practical difference matters because a fixed-velocity key needs only a contact cleaning while a dead key may require a full strip replacement.

The browser test makes this distinction visible without opening the keyboard. Watch the velocity column in the event log as you press the questionable key at a range of force levels. A healthy key reports a spread of values, while a fixed-velocity key returns a tight cluster that barely moves no matter how hard you press.

Running the dead key sweep

Press every key from the lowest note to the highest at medium pressure, firm enough to trigger a note if the key is functioning but not so hard that you miss keys that require extra force. Watch the virtual piano for dark keys. Any key that does not light up during the sweep is a candidate for dead key status.

Confirming a dark key before labeling it dead

For each dark key, press it several more times at increasing force levels. A key that remains dark at maximum force is truly dead. The contact is not conducting at all. A key that lights up only with very hard presses has a worn contact strip that is still functional but degraded. Furthermore, compare the velocity logged for surrounding keys at the same pressure to determine whether the questionable key is reporting lower-than-expected velocity even when it does register.

Next steps after identifying dead keys

For keyboards under warranty, a dead key is a valid warranty claim. Screenshot the event log showing no Note On for the specific MIDI note number and email it with the warranty request. The note number identifies which physical key is affected without requiring the manufacturer to reproduce the issue.

For out-of-warranty keyboards, contact strip replacement is a common repair. A repair shop can source and install a replacement strip covering the dead key zone for a fraction of the keyboard cost. Before sending for repair, try cleaning the contact board and contact strip with isopropyl alcohol when debris or buildup is visible; this can restore keys affected by contamination before parts are replaced.4

Contact strip zones and diagnosing group failures

Adjacent dead keys can indicate a shared contact strip or contact-board section rather than separate key faults. When one section fails, every key above that section can stop transmitting MIDI simultaneously. The repair is usually one strip or contact-board section replacement rather than multiple individual key fixes. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

To confirm a strip zone failure versus an isolated fault, note the exact MIDI note numbers of all dark keys from the event log. Look up the contact layout for your specific keyboard model in the service manual or manufacturer parts documentation. If the dead keys align with a known strip boundary, the diagnosis is confirmed.

Individual key failures versus strip zones

A single isolated dead key surrounded by healthy keys on both sides can indicate debris lodged directly under that key rather than a strip zone fault. Before sending for repair, remove the key cap and inspect for visible debris. Clean the contact surface with a cotton swab and isopropyl alcohol, then retest before booking a service appointment. If the key responds to cleaning, you avoided an unnecessary repair visit.

When to use this

Run this test when a key produces no sound in your DAW, when a chord feels uneven because one key consistently drops out, or when you want to document a dead key in the log before a warranty claim or repair appointment.

Examples

Middle C (note 60) stays dark during a full-range sweep

The event log shows no Note On for note 60 even at maximum pressure. The contact strip at this position is not conducting. Note the MIDI note number and use it to identify the exact key in a warranty claim.

A key registers only at very hard pressure with velocity always above 110

One of the two contacts in this key is functional but the other is not closing until very late in the key travel. This is a worn contact strip, not a dead key. The velocity is high because the gap between the two contact times is very small.

Sources
  1. 1.

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

  2. 2.

    MIDI Association, "MIDI Octave and Note Numbering Standard," midi.org, accessed June 2026. https://midi.org/community/midi-specifications/midi-octave-and-note-numbering-standard

  3. 3.

    MIDIbox, "MIOS32 Tutorial #029: Fast Scan Matrix for velocity sensitive Keyboard," github.com, 2012. https://github.com/midibox/mios32/blob/master/apps/tutorials/029_keyboard_velocity/README.txt

  4. 4.

    iFixit, "Korg MicroKORG Key Contact Strip Repair," ifixit.com, July 2018. https://www.ifixit.com/Guide/Korg+MicroKORG+Key+Contact+Strip+Repair/77141

FAQ