Identifying and Fixing MIDI Ghost Notes

MIDI Ghost Notes: Identify and Fix Duplicate Note Triggers

When a DAW records two notes from one physical key press, the extra event is usually a ghost note.¹ It can sound like a double-trigger, a thicker note, or a sequencer step with stacked velocity. The cause is often a bouncing contact strip: a key press that completes the electrical circuit twice within a few milliseconds because the contact material flexes slightly before settling.² Identifying which key causes the ghost and whether it happens consistently narrows down whether the fix is a firmware update, a filter, or a hardware repair.

This tester flags any Note On message arriving within 30 ms of a previous Note On for the same pitch with a red ⚠ GHOST marker in the event log. The 30 ms threshold is a conservative tool window; debounce and duplicate-note filters use configurable time thresholds rather than a universal standard.³ Intentional re-presses are separate musical events, not duplicate events from one press.

What causes MIDI ghost notes

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

Seeing bounce before the DAW hides it

The browser log catches the duplicate Note On before DAW plugins, instruments, or quantization can disguise it. If the same key produces paired events under 30 ms, you have evidence of contact bounce rather than a musical timing issue. DAW software often applies its own note-deduplication or quantization that masks the raw hardware behavior, which is why a browser-based test reveals the problem first.

The 30 ms window is generous on purpose. A deliberate second press at musical speed is almost always wider than that, so the flag rarely catches intentional playing. When you see the marker, read the logged gap first: a value of a few milliseconds is the signature of mechanical bounce, not human timing.

How this tester identifies ghost notes

Every Note On event that arrives within 30 ms of the previous Note On for the same pitch is flagged with a ⚠ GHOST marker in the event log.³ The marker shows both the original event and the ghost, along with the time gap in milliseconds. For a bouncing contact strip, the gap is typically a few milliseconds, far shorter than a deliberate second press.

Capturing repeatable ghost-note evidence

To test for ghost notes, play each key at different velocities. Ghost notes on contact strip wear tend to appear at specific pressure ranges, usually soft or medium pressure, where the contact bounces most. Building on this, check whether the ghost appears on every press or only occasionally. Intermittent ghost notes point to a borderline contact strip that will fail more consistently as it wears further. CapyToolkit's marker and time gap give you evidence you can screenshot before changing firmware, filters, or hardware.

Fixing MIDI ghost notes

Start by checking whether the manufacturer publishes firmware or driver updates for the keyboard. Firmware can affect how raw switch transitions are debounced before the controller sends MIDI messages. Download the latest firmware from the manufacturer website and install it according to their instructions, then retest. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

If firmware does not resolve the issue, a MIDI filter plugin in your DAW can suppress events arriving within a configurable window. This masks the ghost without fixing the underlying hardware but keeps the keyboard usable while you arrange a repair. For persistent ghost notes on specific keys after a firmware update, replacing the contact strip section covering the affected keys is the definitive hardware fix. This is a common repair that most keyboard technicians can perform.

DAW-side mitigation while awaiting hardware repair

Until the hardware fix is complete, a MIDI filter plugin in your DAW lets you suppress ghost notes with a DAW filter and keep the keyboard usable for recording. Most major DAWs support MIDI effect chains or event-filter plugins that can suppress incoming Note On events arriving within a configurable time window after the previous event on the same pitch. A short debounce window removes most contact-strip bounce while leaving deliberate rapid re-presses audible.

Each DAW has a slightly different implementation, but the principle is identical: suppress the second of two identical notes arriving within the ghost-note window. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details. Further details and practical considerations round out this discussion with additional relevant information for the reader to consider carefully.

Ghost note markers as diagnostic evidence for repair

Save a screenshot of the event log showing the ⚠ GHOST markers with their time gaps before implementing any filter. The gap value in milliseconds is the critical measurement. A gap in the single-digit to low-double-digit millisecond range is consistent with contact-strip bounce, whereas gaps above 30 ms may indicate a different hardware issue. Very short electrical chatter may benefit from firmware or hardware repair rather than software mitigation. Include the screenshot with a warranty claim or repair appointment to give the technician a reproducible baseline.

When to use this

Run this test when you hear double-triggers in your DAW, when a sequencer records two notes on the same beat from a single key press, or when a chord sounds thicker or phase-shifted compared to adjacent chords because one key is doubling up.

Examples