Logic Pro Troubleshooting: Fix Audio, MIDI and Crashes
Start with the symptom, isolate one boundary at a time, and keep your project and custom settings safe while you test the fix.
Fixes by symptom
Choose the problem you can see or hear, then follow the checks in order.
Logic Pro No Sound: Find Where the Signal Stops
Meters moving but nothing coming out of your speakers? The last meter that moves shows where the signal stops, so these 8 checks start there and cover silent playback, a mic you can't hear, silent MIDI tracks and projects that went quiet after an update.
Read the guide
Logic Pro Slow to Open Projects? Find What It’s Loading
6 min read
Logic Pro Metronome Not Working? Fix the Missing Click
6 min read
Logic Pro Crackling Audio: Find and Fix Clicks and Pops
6 min read
Logic Pro MIDI Services Not Available: Fix the CoreMIDI Error
11 min read
Logic Pro Missing Audio Files: Relink and Recover
7 min read
Why Logic Pro Bounce Sounds Different From Playback
7 min read
Track Protect vs Freeze in Logic Pro: Lock the Right Thing
9 min read
How to Freeze Tracks in Logic Pro and Save CPU
8 min read
How to Update Logic Pro Safely
9 min read
MIDI Keyboard Not Working in Logic Pro: 9 Fixes
11 min read
Audio Interface Not Showing Up in Logic Pro: Fix Detection First
9 min read
Logic Pro Keeps Crashing: Find the Cause and Fix It
10 min read
Logic Pro Plugins Not Showing Up: Fix Missing Audio Units
9 min read
Logic Pro System Overload: Find the Bottleneck and Fix It
11 min read
Logic Pro Not Recording Audio: Fix the Signal Path
10 min read
How to Fix Latency in Logic Pro: Follow the Signal Path
10 min read
Why Is My Mic So Quiet in Logic Pro? 8 Fixes
14 min readFix one boundary at a time
Pick the symptom you can reproduce, then run the shortest safe test. Random preference changes just add variables. Reinstalling Logic Pro rarely fixes an interface driver, a damaged project, or an incompatible Audio Unit.
If both the one-time-purchase and Apple Creator Studio versions of Logic are installed, first confirm which app opens the problem project. Record that app and its version alongside macOS before repeating the test. Apple’s troubleshooting instructions distinguish the two apps; if a reset is eventually needed, follow the procedure for the app you are diagnosing.
- Protect the session.Save a copy and note what changed before removing devices, plugins, or settings.
- Repeat one short test.Use the same project section, track, or input so each change produces useful evidence.
- Cross a boundary.Try a new empty project, built-in audio, or a session without third-party Audio Units. To skip those plug-ins, quit Logic Pro, open it again and immediately hold Control before a project opens, then click Launch Without Audio Units in the alert.
- Change one thing.Do not reset settings, update several drivers, and rebuild routing in the same pass.
- Keep the result.Record the working device, buffer, plugin, project, and macOS state before restoring extras.
Apple’s current Logic Pro troubleshooting sequence also starts with backups, updates, compatibility, external devices, built-in audio, and third-party Audio Units before destructive steps. If your projects or Sound Library sit on an external drive, Apple says to make sure it’s formatted as APFS. Copy anything you want to keep off that drive before you reformat it.
Logic Pro troubleshooting FAQ
What should I check first when Logic Pro stops working?
Save a copy, note what changed, restart, and repeat one short test. Then try a new empty project to separate a project fault from an app-wide problem.
Should I reset Logic Pro settings immediately?
No. Reset only after simpler isolation tests and after recording custom preferences and exporting key commands. A reset can hide the original cause and create extra setup work.
When should I reinstall Logic Pro?
After device, project, plugin, and settings tests point back to the application itself. Reinstalling does not repair incompatible hardware, drivers, or third-party plugins.
Why does a problem happen in only one project?
The project may contain a damaged asset, unusual routing, a problematic plugin instance, or a project-level setting. Duplicate it and remove one boundary at a time.