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.
When Logic Pro stops recording, loses audio, ignores a MIDI keyboard or crashes on launch, random preference resets make the problem harder to understand. A better order is: protect the project, reproduce the symptom, separate app-wide problems from project-specific ones, and change one variable at a time.
Use the table below to reach the right guide. If the problem started immediately after a Logic Pro, macOS, plug-in or driver update, write down the exact versions before changing anything. That one note often explains more than a reinstall.
Start with the symptom
| What you see or hear | First boundary to test | Detailed guide |
|---|---|---|
| The project plays but nothing reaches the speakers | Output device, Stereo Out, mute/solo and routing | Logic Pro has no sound |
| The track is armed but no waveform is recorded | macOS permission, track input, record enable and interface channel | Logic Pro is not recording audio |
| The microphone records, but the signal is too quiet or noisy | Mic type, preamp gain, pad, distance and double monitoring | Why the mic is too quiet |
| The performer hears a delayed copy | I/O buffer, plug-in latency and the monitoring path | Fix recording and MIDI latency |
| The audio interface is missing | macOS detection, cable/power, driver and Logic audio device | Audio interface not showing up |
| The MIDI keyboard is connected but does not play the instrument | macOS MIDI visibility, track selection, channel and control-surface assignment | MIDI keyboard not working |
| An Audio Unit is absent or failed validation | Plug-in format, architecture, authorization and Audio Unit scan | Plugins not showing up |
| Logic quits, hangs or shows a system overload | Project versus app, third-party Audio Units, buffer and one overloaded channel strip | Crash diagnosis · System overload fixes |
The safe troubleshooting order
- Save a copy before testing. Do not troubleshoot the only copy of a client or release project.
- Write down the environment. Record the Logic Pro build, macOS version, Mac chip, audio/MIDI hardware, driver and the plug-ins used when the symptom appears.
- Restart and test the same action. A restart is useful only if you repeat the same short test afterward.
- Test a new empty project. If the symptom disappears, the fault is probably in the project, routing, an asset or a plug-in instance rather than the whole application.
- Remove third-party boundaries one at a time. Try built-in audio, disconnect external devices, then launch without third-party Audio Units when the symptom points there.
- Reset settings late, not first. Apple notes that a settings reset keeps projects, presets and patches but removes custom preferences. Export key commands and record your settings before that step.
- Reinstall last. Reinstalling does not repair a bad cable, incompatible driver, unauthorized plug-in or corrupt project asset.
This order follows the isolation logic in Apple’s current Logic Pro troubleshooting procedure, while keeping the project and custom workflow recoverable.
Audio and recording problems
No sound and no recorded waveform are different faults. Playback follows the project’s output routing; recording follows the input device, physical interface channel, track input, record enable and macOS microphone permission. A quiet microphone is different again: moving a channel fader does not add clean preamp gain to the recorded signal. Use the symptom router instead of applying every audio fix to every problem.
For latency, decide whether the performer hears Logic’s software-monitored path, the interface’s direct path, or both. Lowering the buffer can reduce software-monitoring delay, but a high-latency plug-in on the active signal path can still make a take uncomfortable. Low Latency Mode is a diagnostic and recording tool, not proof that every plug-in remains audible.
Interfaces, MIDI devices and plug-ins
If a device disappears after an update, confirm that macOS can see it before changing Logic settings. An interface that does not appear to the operating system cannot be selected inside Logic. For third-party Audio Units, check the developer’s current macOS and Apple-silicon support, license state and plug-in format. Apple’s own guidance recommends verifying compatibility before an operating-system or Logic update, especially when a project depends on external hardware or older Audio Units.
Crashes, hangs and system overload alerts
A crash on launch, a crash while opening one project and a system overload during playback require different tests. Launching without Audio Units helps with startup failures; a fresh project helps separate app-wide instability from a damaged session; the Logic performance meter helps identify a single heavy channel strip. During recording, a smaller buffer favors latency. During a dense mix, a larger buffer, freezing or bouncing demanding instruments, and removing unnecessary live plug-in paths can restore headroom.
What to record before asking for help
- the exact symptom and the shortest sequence that reproduces it;
- Logic Pro and macOS versions plus Mac model/chip;
- audio interface, MIDI device, driver/firmware and connection type;
- whether the problem occurs in a new empty project;
- whether built-in audio or launching without Audio Units changes the result;
- the exact alert text or a screenshot with private project information removed.
Logic Pro troubleshooting FAQ
What should I check first when Logic Pro stops working?
Save a copy, note what changed, restart, then repeat one short test. Next, try a new empty project to separate a project fault from an app-wide problem.
Should I reset Logic Pro settings immediately?
No. Reset settings after simpler isolation tests and after recording custom preferences and exporting key commands. A reset can hide the original cause and creates unnecessary setup work.
When should I reinstall Logic Pro?
After device, project, plug-in and settings tests point back to the application itself. Reinstalling is a late step because it does not repair incompatible hardware, drivers or third-party plug-ins.
Why does a problem happen in only one project?
The project may contain a damaged asset, unusual routing, a problematic plug-in instance or a project-level setting. Duplicate the project and remove one boundary at a time rather than rebuilding the original blindly.