Logic Pro Bluetooth Headphones Latency: The 135 ms Problem (and the Better Way to Hear Your Mix on AirPods)
By David Payette · audio engineer, professional musician · About →
If you’ve ever switched Logic Pro’s audio output to your AirPods to listen to a session, you know the symptom: everything goes sluggish. Plugin meters lag visibly. The transport feels weirdly delayed. If you tried to play in time with what you’re hearing, you couldn’t.
The number people quote is around 135 ms of output latency the moment Logic Pro switches to a Bluetooth audio device, up from around 7 ms against a USB interface. That number comes from the long‑running Logic Pro Help thread on the topic, and it lines up with Apple’s own support documentation on Bluetooth audio and the independent measurements on Stephen Coyle’s site. It is real, it is reproducible, and there is no Logic Pro setting that fixes it.
This page explains why the latency exists, what its boundaries are, and the workflow that lets you hear your mix on AirPods without paying that 135 ms tax inside Logic.
Why the latency happens
Three things change when Logic Pro hands its output to a Bluetooth device.
1. The audio buffer doubles up. Bluetooth audio profiles batch samples into ~10–20 ms windows for transmission, and the receiving headphones need their own buffer to absorb radio jitter. The combined “send + buffer + decode + DAC” path inside the AirPods sits around 80–150 ms even before macOS gets involved. AirPods Pro 2nd‑gen and AirPods 3rd‑gen are independently measured at 80–144 ms depending on the test condition.
2. macOS adds its own audio session overhead. Switching audio devices in Core Audio is not free. The OS reconfigures the route, re‑negotiates the stream format, and hands control to the Bluetooth audio agent. That handoff alone can add 20–40 ms.
3. The codec degrades. macOS frequently defaults to SBC against AAC‑capable headphones and requires manual coaxing (Bluetooth Explorer, defaults write flags) to force AAC. There’s a 9to5Mac walkthrough on enabling AAC on macOS, but the workaround is fragile and macOS Sequoia has been observed forcing SBC even on speakers that advertise AAC (Apple Discussions thread). SBC sounds noticeably worse than AAC at the same headphones.
The combined number is the 135 ms region people see in Logic Pro Help. That’s not a bug in Logic. It’s a bug in the path.
What you can do inside Logic Pro
Honestly: not much. The latency is below Logic’s level — it lives in Core Audio and the Bluetooth stack. You can:
- Set Logic’s I/O Buffer Size to the lowest available value. Won’t change the Bluetooth latency itself, but won’t make it worse.
- Disable plugin delay compensation on the master bus when monitoring. Saves a few milliseconds of internal compensation. Doesn’t touch the Bluetooth radio.
- Force AAC over SBC using Bluetooth Explorer (Apple’s developer tool) if you’re committed to using the Mac’s Bluetooth path. Reduces the codec quality penalty but not the latency. Fragile across macOS versions.
- Use AirPods’ “Tools for Developers” mode if you have access to it. Apple’s Vision Pro plus H2‑equipped AirPods can drop into a low‑latency lossless mode, but that path is currently Vision Pro–only and not available on iPhone or Mac for music monitoring as of April 2026.
None of these gets you below the 80–100 ms floor imposed by the Bluetooth radio itself.
The better way: skip the Mac’s Bluetooth stack entirely
The Mac’s role is to run Logic Pro. The Mac’s role is not to be a Bluetooth audio source for your AirPods. Your phone is purpose‑built for that role and is much better at it.
Here’s the workflow.
- Keep Logic’s audio output set to your USB interface. Do not change anything in Logic Pro’s audio settings.
- Install Auxfeed. Free download — the plugin is AU, VST3, and AAX, and it works on every macOS Logic version from 10.7 forward.
- Drop the Auxfeed plugin on your master bus, post‑fader. It runs alongside your other master plugins. You do not have to remove anything.
- Open the Auxfeed app on your iPhone. Free on the App Store. Tap your Mac’s name in the source list. Audio starts streaming to the phone.
- Pair your AirPods to the iPhone the way you normally would. They’re now playing the live mix from Logic.
Logic Pro thinks nothing changed. Your USB interface is still the audio output. The 135 ms penalty doesn’t apply to Logic — it only applies to the Auxfeed → AirPods leg, which the iPhone handles natively with AAC.
The total round trip from “engineer hits play in Logic” to “you hear sound in your AirPods on the couch” is in the 200 ms range — Auxfeed adds tens of milliseconds for the network hop, and the iPhone‑to‑AirPods Bluetooth radio adds the rest. Still not tracking‑grade. Perfectly fine for checking, mixing playback, reference listening, and walking around the room.
What this fixes
- Logic Pro itself stays responsive. No 135 ms output latency. No transport feeling sluggish. Plugin meters update in time.
- You can use a real interface and AirPods at the same time. The interface is the studio reference. The AirPods are the consumer reference. No route switching.
- The codec is consistent. iPhone always sends AAC to AirPods. No SBC fallback, no Bluetooth Explorer wrestling.
- Your monitors keep working. Speakers stay live; the AirPods stream is parallel. A/B’ing is a tap in the Auxfeed app.
What this is NOT
- Not a way to track on AirPods. 200 ms is unusable for tracking. Use wired in‑ear monitors for tracking.
- Not a substitute for proper mastering on calibrated monitors. AirPods are a consumer reference point, not a mastering monitor.
- Not a fix for Logic itself if you genuinely need Logic’s output to go to Bluetooth (e.g., for some multi‑output configuration). For that case there isn’t a clean answer; you live with the latency.
Why the phone path is better than the Mac path
This is worth being explicit about. Why is your iPhone’s Bluetooth stack noticeably better than your Mac’s for this exact job?
- iPhone always sends AAC to AirPods. Every AirPods model only supports AAC and SBC, and pairs AAC automatically with iPhone. There is no setting. There is no fallback to worry about. The Mac, by contrast, can and does fall back to SBC depending on the macOS version and headphone firmware.
- iPhone audio sessions are designed for music playback. iOS handles route changes (AirPods in/out of the case, switching between AirPods and built‑in speaker, sharing audio between two pairs of AirPods) without any application involvement. The Mac requires Core Audio reconfiguration each time.
- iPhone owns the codec choice. No third‑party app on iOS can override the system codec to AirPods. That sounds like a constraint but it’s a feature: the codec is always the right choice for the headphones you’ve paired.
- The phone is portable. AirPods are a portable consumer product. Letting them connect to the device they were designed for — your phone — is the path of least resistance. Routing them through your Mac was always swimming upstream.
DAW‑agnostic note
Everything on this page is the same on Pro Tools, Cubase, Studio One, Ableton Live, REAPER, FL Studio, and Bitwig. The number quoted (135 ms) is from the Logic Pro Help thread because Logic Pro users have been the most vocal about it, but Cubase users see the same shape on the Steinberg Forums Bluetooth Headphone Latency thread and Pro Tools users see it on the Avid DUC AirPods Pro as Playback Engine thread. The cause is the same in every case (the OS Bluetooth path) and the workaround is the same (don’t use the OS Bluetooth path).
If you’re on a different DAW and looking for the same fix, see the per‑DAW guides:
- Pro Tools + AirPods workflow (the only free AAX plugin in this category)
- Cubase Bluetooth headphones
Try it
The download is free. The iPhone or Android app is free. The whole setup takes under two minutes for a Logic user who already has the plugin installed.
You’ll wonder why you were ever pointing macOS’s Bluetooth at your AirPods.
See also:
- How to check your mix on Bluetooth headphones (the workflow that actually works) — the cross‑DAW pillar.
- Phone as second meter screen for Logic Pro — same plugin, different use case.
- Mixing on AirPods — when the consumer reference becomes part of the workflow.