How to Debug MIDI Devices on Mac

Last updated: March 2026

This guide explains how to debug MIDI devices on Mac and diagnose common MIDI problems on macOS. If your MIDI controller is not working, sending wrong channels, or producing stuck notes, you need a way to inspect the raw MIDI messages your device sends. Midilize is a MIDI debugging and monitoring tool for macOS that shows you every byte in real time — so you can find the problem fast and know exactly what to fix.

Common MIDI problems

These are the most frequent MIDI issues that require debugging:

• No MIDI signal — your device is connected but nothing happens in your DAW
• Wrong MIDI channel — your controller sends on channel 1 but your app expects channel 10
• Stuck notes — Note On messages without matching Note Off, causing notes to sustain indefinitely
• Wrong CC numbers — knobs and faders sending unexpected control change numbers
• Duplicate messages — one key press generates multiple Note On events
• Velocity issues — notes always at maximum or minimum velocity regardless of touch
• SysEx errors — firmware updates or patch transfers failing silently
• MIDI clock problems — external devices not syncing correctly to your DAW

How to inspect MIDI messages

The key to debugging MIDI is seeing the raw data. Every MIDI message is a sequence of bytes: a status byte (which encodes the message type and channel) followed by one or two data bytes. For example:

• 90 3C 64 — Note On, channel 1, note C4 (60), velocity 100
• B0 07 7F — Control Change, channel 1, CC 7 (volume), value 127
• 80 3C 00 — Note Off, channel 1, note C4, velocity 0
• E0 00 40 — Pitch Bend, channel 1, centered position

A MIDI monitor shows you these messages decoded into human-readable form as they arrive — note names, CC labels, channel numbers, and precise timestamps.

Using monitoring tools on macOS

macOS does not include a built-in MIDI message monitor. Audio MIDI Setup shows connected devices but does not display message data. For actual debugging, you need a dedicated tool.

Options include terminal-based tools (limited readability), Xcode's MIDI testing utilities (require a large developer download), or a visual application like Midilize. Midilize provides both a Monitor Mode for inspecting raw messages and a Flow Mode for testing signal routing — no developer account or terminal experience needed.

Debugging workflow with Midilize

Here is a systematic debugging workflow that works for virtually every MIDI problem:

Diagnosing specific problems

Stuck notes in detail: Filter the monitor to Note On and Note Off. For every Note On (velocity > 0), there should be a corresponding Note Off (or a Note On with velocity 0) on the same note number and channel. If a Note On has no match, the note will sustain. Causes include: a MIDI cable unplugged mid-session (the Note Off never arrived), a controller firmware bug, or a filter node in the signal chain blocking Note Off messages.

To fix stuck notes immediately, use Midilize's Panic tool, which sends All Notes Off (CC 123) on all channels. To prevent recurrence, ensure Note Off messages are not being filtered out anywhere in your signal chain.

Wrong CC numbers: If a knob or fader sends an unexpected CC number, the controller is likely in the wrong preset or mode. The monitor shows the exact CC number for every message. Compare the received CC to your expected mapping and update the controller's mapping or your DAW's assignment to match.

Velocity stuck at maximum or minimum: If velocity is always 127, the controller may have velocity sensitivity disabled in its settings, or the MIDI channel's velocity curve is set to maximum. Check the controller's global settings. In Midilize, you can add a Velocity Modifier node to apply a velocity curve and restore natural dynamic response.

Hardware vs software: how to tell

Midilize acts as a neutral diagnostic layer between your hardware and your software. Use this to pinpoint whether a problem is hardware-level or software-level:

If messages appear correctly in Midilize Monitor — the hardware, cable, and macOS driver are working correctly. The problem is in your DAW's MIDI configuration, plugin settings, or routing.

If messages are missing, wrong, or erratic in Midilize Monitor — the problem is upstream of the software: the device itself, the MIDI cable, the USB connection, or the driver. Try a different cable, different USB port, and restart the device.

Signs of hardware problems: messages appearing without any key presses, notes triggering only after multiple attempts, signal only working when the cable is held at an angle. These indicate physical fault.

Signs of driver or OS problems: device disappears from Audio MIDI Setup after a macOS update, or messages appear but with incorrect data compared to what the device should be sending according to its documentation.

Debugging tips

• Stuck notes: Every Note On must have a matching Note Off. If not, add a Panic send or use Midilize's Panic tool.
• Wrong channel: The channel is encoded in the lower 4 bits of the status byte. 90 = Note On channel 1, 91 = Note On channel 2, up to 9F = channel 16. Add a Set Channel node to force the correct channel.
• Timing/latency: Midilize timestamps messages with microsecond precision. Compare timestamps between consecutive messages to identify jitter or unexpected delays in the signal chain.
• SysEx integrity: SysEx messages start with F0 and end with F7. If the inspector shows an incomplete SysEx (no F7), the device dropped bytes mid-transmission. Check cable quality and USB connection.
• USB power: Some controllers behave erratically on unpowered USB hubs. Connect directly to your Mac or use a powered hub.

When the device is not detected

If your MIDI device does not appear in Midilize's Sources panel:

1. Check the USB or Bluetooth connection
2. Try a different USB cable (some cables carry charge only, not data)
3. Try a different USB port, or connect directly to the Mac without a hub
4. Open Audio MIDI Setup and check if macOS sees the device in MIDI Studio
5. In MIDI Studio, use the rescan option to refresh the device list
6. Check the manufacturer's website for macOS drivers if the device requires them
7. Restart your Mac with the device connected

For a complete troubleshooting checklist, see our dedicated guide: MIDI interface not detected on Mac.

Testing with a known-good reference

One of the most effective debugging strategies is to introduce a known-good reference at each point in the signal chain. If you are not sure whether a problem is in your controller, your cable, your MIDI interface, or your DAW, test each component in isolation:

• Test the controller alone: Connect the controller directly to your Mac and open Midilize. Enable the device in Sources and watch Monitor Mode. Press every key, turn every knob, move every fader. If messages appear for every control in the correct range, the controller and its USB connection are working correctly. If some controls are missing or showing wrong values, the fault is in the controller itself.
• Test a different cable or port: If the controller does not appear in Sources, swap the USB cable and try a different port. Use a cable you have confirmed works for data transfer on another device. Connect directly to a USB port on your Mac rather than through a hub.
• Test in a minimal DAW session: Open a new, empty session in your DAW with a single software instrument track. If MIDI works there but not in your main session, the problem is in the main session's configuration — a specific track setting, a MIDI FX plugin, or a routing loop.
• Test on a different Mac: If you have access to another machine, connecting your controller and testing it immediately reveals whether the fault is device-specific or Mac-specific (driver, permissions, USB hardware).

MIDI problems after a macOS update

macOS updates occasionally break MIDI functionality, most commonly for devices that rely on proprietary drivers. The symptoms vary: the device may disappear from Audio MIDI Setup, messages may arrive but with incorrect data, or the device may appear but produce no output at all.

When this happens after an update, the first step is to check the device manufacturer's website for a driver update that supports the new macOS version. Most major manufacturers release updated drivers within days or weeks of a macOS release. If no driver is available, check whether your device has a class-compliant mode — many devices that normally use proprietary drivers also support the USB MIDI class specification as a fallback, which does not require a driver and works on any macOS version.

Class-compliant operation can usually be enabled through the device's menu or by holding a specific button combination at startup — refer to your device's documentation. Once in class-compliant mode, the device should appear in Audio MIDI Setup and in Midilize without any driver installed.

Frequently asked questions