How to Detect and Fix MIDI Feedback Loops on Mac
Last updated: March 2026
A MIDI feedback loop is one of the most disruptive problems in any MIDI setup. It happens when MIDI data cycles endlessly between devices or applications — causing stuck notes, parameter chaos, and sometimes a frozen DAW. This guide explains what causes MIDI feedback loops on macOS, how to identify them, and how to fix them. We also cover how Midilize can automatically detect loops for you in real time.
What is a MIDI feedback loop?
A MIDI feedback loop occurs when the MIDI data transmitted by a device or application is routed back into itself as input. The device processes the incoming data and sends it out again, which gets routed back in again, creating an infinite cycle. Each pass through the loop adds more messages, and within milliseconds the loop can generate thousands of MIDI messages per second.
Think of it like audio feedback from a microphone pointed at a speaker. The microphone picks up the speaker's output, the speaker amplifies it, the microphone picks it up again, and the sound grows into a screech. MIDI feedback works the same way, except instead of sound you get a flood of Note On, Control Change, and other MIDI messages that overwhelm your system.
The consequences are immediate and obvious:
- Stuck notes — notes sustain indefinitely because Note Off messages are lost in the flood, or the loop keeps retriggering Note On
- Erratic parameter changes — CC values (volume, pan, filter cutoff) jump wildly as the same control change cycles endlessly
- DAW becomes sluggish or freezes — the MIDI processing thread is overwhelmed by thousands of messages per second
- CPU spikes — every message triggers processing in your synth, plugin, or DAW
- Audio glitches — the CPU overload causes buffer underruns, producing clicks, pops, or silence
Common causes of MIDI feedback loops on macOS
MIDI feedback loops almost always come from routing mistakes. Here are the most common causes on a Mac:
1. IAC driver loopback
The macOS IAC (Inter-Application Communication) driver is a virtual MIDI bus that lets applications send MIDI to each other. A feedback loop happens when an application has the same IAC bus enabled as both its MIDI input and its MIDI output. The app receives its own output, processes it, sends it out again, and the loop begins.
This is especially common with DAWs that default to accepting MIDI from all available sources, including the IAC driver. Ableton Live, for example, has a global MIDI input setting that can include the IAC bus — if that same bus is also configured as an output, you have a loop.
2. MIDI Soft Thru in your DAW
Most DAWs have a "MIDI Thru" or "Soft Thru" feature that echoes incoming MIDI to the selected output. This is useful for playing a software instrument live: your keyboard sends MIDI in, the DAW routes it to the plugin, and you hear the sound. But if the output goes to a hardware synth that is also feeding MIDI back into the DAW (via USB or a MIDI cable), the DAW receives its own echo and sends it out again.
3. USB MIDI and two-way communication
Traditional 5-pin DIN MIDI cables are one-directional: one cable for MIDI Out, another for MIDI In. USB MIDI, however, is inherently bidirectional — a single USB cable carries both input and output. This makes feedback loops much easier to create accidentally, because there is no physical separation between the send and receive paths. With DIN cables, you could simply unplug one cable to break the loop. With USB, both directions are always connected.
4. Hardware synth with Local Control On
When a hardware synthesizer has Local Control set to On (the default), its keyboard is directly connected to its sound engine. When you press a key, two things happen: the synth plays the note internally, and it sends a MIDI Note On message out via USB or DIN. If your DAW has MIDI Thru enabled, it echoes that Note On back to the synth, which plays the note a second time and sends another Note On out — creating a loop.
5. Multiple MIDI routing apps
If you run multiple MIDI routing utilities simultaneously (IAC driver, a MIDI patchbay, virtual ports from different apps), it is easy to accidentally create a circular path where MIDI flows from App A to App B to App C and back to App A. Each hop adds latency and processing, making the loop harder to trace.
How to detect a MIDI feedback loop
The symptoms of a MIDI feedback loop are distinctive, but confirming the diagnosis requires observing the actual MIDI traffic. Here is a systematic approach:
Observe the symptoms
If you experience stuck notes, runaway parameter changes, or a frozen DAW that recovers when you disconnect a MIDI cable or disable a virtual port, a feedback loop is the most likely cause. MIDI activity LEDs on your interface or controller flashing rapidly without any input is another strong indicator.
Check the Local Control setting
If you are using a hardware synthesizer with USB MIDI and a DAW with MIDI Thru, try setting Local Control to Off on the synth. If the problem stops, you have confirmed a feedback loop through the synth. With Local Control Off, the keyboard no longer triggers the internal sound engine directly — instead, MIDI goes out to the DAW and back, playing the note only once.
Isolate by disconnection
The fastest diagnostic technique is to disconnect MIDI connections one at a time. Unplug a cable or disable a virtual port and see if the problem stops. When removing a specific connection fixes the issue, you have identified the link that completes the loop. Start with the IAC driver — disable it as an input in your DAW's MIDI preferences, since it is the most common accidental loop source on Mac.
Use a MIDI monitor
Open a MIDI monitoring tool and watch the message flow. In a feedback loop, you will see the same message (or very similar messages) repeating at impossibly high rates — hundreds or thousands per second, far faster than any human could play. The messages will typically share the same status byte, note number, or CC number, and they will keep flowing even when you are not touching any controller.
On macOS, you can use MIDI Monitor (a free third-party app) to watch individual MIDI sources. However, tracing which route carries the loop requires checking each source and destination separately, which is tedious.
Use Midilize Radar for automatic detection
Midilize's Radar view watches all MIDI sources and destinations on your Mac simultaneously and correlates the traffic between them. When it detects that the same MIDI data is cycling between endpoints at abnormally high message rates, it automatically flags the route as a feedback loop and highlights the involved endpoints in red. You do not need to manually check each source — Radar shows you the exact loop path instantly.
Radar also distinguishes between a genuine feedback loop and a fast but legitimate MIDI source (like a sequencer running at high speed). It only flags routes where correlated data is cycling between a source and a destination, not simply any endpoint with high traffic.
How to fix a MIDI feedback loop
Once you have identified the loop, breaking it requires removing one link in the circular path. Here are the most common fixes, depending on the cause:
Fix IAC driver loops
Open your DAW's MIDI preferences and disable the IAC bus as an input if you are also using it as an output (or vice versa). In Ableton Live, go to Preferences > Link/Tempo/MIDI and set the IAC driver's Track and Remote inputs to Off. In Logic Pro, open Preferences > MIDI > Inputs and uncheck the IAC port, or check the Environment window for circular connections. If you need IAC for cross-app routing, use separate buses for each direction: for example, IAC Bus 1 for sending and IAC Bus 2 for receiving.
Disable MIDI Soft Thru
If your DAW echoes incoming MIDI back to an external device, and that device feeds MIDI back in, disable the DAW's MIDI Thru setting for the relevant track or globally. In Ableton Live, set the track's MIDI output to "None" instead of the external device, or turn off Monitor on the track. In Logic Pro, disable "Auto demix by channel if multitrack recording" and check your External Instrument configuration.
Set Local Control Off on hardware synths
If you are using a hardware synthesizer with a DAW, set the synth's Local Control to Off. This disconnects the keyboard from the internal sound engine. The keyboard sends MIDI out to the DAW, the DAW echoes it back, and the synth plays the note once via the incoming MIDI. Most synths have this setting in their Global or System menu. Consult your synth's manual for the exact location.
Use a USB-to-MIDI interface to break the path
If you are connecting a hardware synth via USB and experiencing feedback, try using a USB-to-MIDI DIN interface instead. This gives you physical control over which direction MIDI flows: connect only the MIDI Out cable from the interface to the synth's MIDI In, and leave the other direction disconnected. This physically breaks the feedback path.
Filter messages in the routing chain
If you need bidirectional MIDI communication but want to prevent loops, insert a filter that blocks specific message types from completing the circle. For example, allow Note On/Off to flow from your keyboard to the DAW, but block Note On/Off from flowing back. Let only CC messages flow in the return direction. Midilize's Modular tab makes this easy: add a Filter node between your MIDI In and MIDI Out nodes to block the message types that would create the loop.
Preventing MIDI feedback loops
Prevention is easier than diagnosis. Follow these practices to avoid feedback loops in the first place:
- Use dedicated IAC buses for each direction. If App A sends to App B on IAC Bus 1, have App B send back on IAC Bus 2. Never use the same bus for both input and output in the same app.
- Disable inputs you do not need. In your DAW's MIDI preferences, only enable the specific MIDI inputs you intend to use. Disable "All Inputs" or "Any" settings that include virtual ports.
- Set Local Control Off by default on hardware synths when using them with a DAW. This eliminates the most common source of hardware MIDI loops.
- Draw your signal path. Before building a complex multi-app MIDI setup, sketch the routing on paper. Follow each MIDI message from source to destination and check whether any path leads back to the source.
- Use Midilize Radar to monitor. Keep Radar open while building your routing setup. It shows you every active MIDI connection on your system in real time, so you can spot circular paths before they cause problems.
- Test one connection at a time. When setting up a new MIDI route, add connections one at a time and test after each addition. If a loop starts, the last connection you added is the culprit.
Emergency: how to stop a loop right now
If you are currently experiencing a MIDI feedback loop and need to stop it immediately:
- Disconnect the MIDI cable or USB connection from the device involved in the loop. This is the fastest physical break.
- Disable the IAC driver in Audio MIDI Setup if virtual MIDI is involved. Open Audio MIDI Setup, go to MIDI Studio (Window > Show MIDI Studio), double-click the IAC Driver, and uncheck "Device is online."
- Send All Notes Off to silence stuck notes. In Midilize, use the Panic tool which sends CC 123 (All Notes Off) on all 16 channels to all connected outputs. Most DAWs also have a Panic or All Notes Off button.
- Quit and restart your DAW if it is frozen. On macOS, use Force Quit (Cmd+Option+Esc) if the application is unresponsive.
Once the immediate crisis is resolved, use the diagnostic steps above to identify and permanently fix the loop before reconnecting.
Frequently asked questions
What is a MIDI feedback loop?
A MIDI feedback loop occurs when MIDI data is sent out from a device or application, routed through other devices or virtual ports, and arrives back at the original sender as input. The sender transmits it again, creating an infinite cycle that produces stuck notes, erratic parameter changes, and can freeze your DAW or crash your system.
How do I know if I have a MIDI feedback loop?
Common symptoms include: notes that sustain indefinitely even after releasing keys, parameters jumping wildly on their own, your DAW becoming sluggish, MIDI activity indicators flashing constantly without any input, and CPU usage spiking. If these symptoms stop when you disconnect a MIDI cable or disable a virtual MIDI port, you likely have a feedback loop.
How do I fix a MIDI feedback loop caused by the IAC driver?
Open your DAW's MIDI preferences and make sure the IAC driver is not enabled as both an input and an output for the same track. In Ableton, disable IAC as an input in Preferences > MIDI. In Logic Pro, check the Environment window and remove circular connections. Use separate IAC buses for each direction if you need cross-app routing.
What does Local Control Off do?
Setting Local Control to Off on a hardware synthesizer disconnects its keyboard from its internal sound engine. Notes are only sent as MIDI output, not played locally. The DAW receives the MIDI, echoes it back, and the synth plays the note once. This breaks the loop because the synth no longer plays the same note twice.
Can Midilize automatically detect MIDI feedback loops?
Yes. Midilize's Radar view monitors all MIDI traffic on your Mac and correlates messages between sources and destinations. When it detects data cycling between endpoints at abnormally high rates, it flags the route as a feedback loop and highlights the involved endpoints. This lets you identify loops instantly without manually tracing cables or settings.