Skip to content
Logic ProFilesLogic ProFiles

Fix Problems

Logic Pro error -10011 — what it means and how to fix it

Error -10011 is the coded form of Logic Pro's system overload alert: the audio engine ran out of time to process the project. We found no Apple article that documents the code itself, but Apple's system overload article covers the cause and the fixes. They are below, CPU first.

Owen Hartley Owen Hartley Updated Checked for Logic Pro 13
Alert box with a stopwatch and an overloaded processor chip on a Mac screen
System Overload. The audio engine was not able to process all required data in time. (-10011)

Applies to: Logic Pro 13 back to Logic Pro X (wording as users report it).

Most likely causes

  1. I/O buffer too small for the number of plug-ins (most common)
  2. Selected software instrument track using one CPU core heavily (common)
  3. Many CPU-heavy plug-ins on individual tracks (common)
  4. Other apps or background tasks using the Mac (occasional)

-10010 or -10011?

Side-by-side comparison of Logic Pro errors -10010 pointing to the disk and -10011 pointing to the processor
-10010 usually means the drive; -10011 usually means the processor.
Code Alert starts with Where to look
-10010 "Disk is too slow or System Overload" Drive speed, project location, sample streaming — see disk too slow
-10011 "System Overload. The audio engine was not able to process…" Processor load — the fixes on this page

To be sure, open the Performance Meter as described in our system overload guide and see whether Processing Threads or Drive I/O peaks when the alert appears.

Older advice you'll still find

A widely shared 2014 blog post on -10011 adds tips that still make sense today: use stock plug-ins while you record, bounce software instruments to audio, and let Spotlight finish indexing before a session. It also suggested a buffer of no more than 128 samples for live recording. Apple's current article doesn't give a maximum — it suggests 256 samples for audio-only recording with Software Monitoring off — so treat 128 as a starting point, not a rule. The buffer latency calculator shows the delay each size adds.

Fixes, in order

  1. 1. Raise the I/O buffer

    Logic Pro > Settings > Audio > Devices > I/O Buffer Size. Go up one step, test, and repeat until the alert stops.

  2. 2. Set Process Buffer Range to Large

    Apple recommends Large in the same pane. It adds latency, so use it while mixing rather than recording.

  3. 3. Select an empty track before playing

    A selected instrument track is processed differently and adds load. Click an empty audio track, then press play.

  4. 4. Freeze heavy tracks

    Freeze tracks with lots of plug-ins so they play back as audio instead of running their effects live.

  5. 5. Share reverbs and delays on sends

    One reverb on a send uses far less CPU than a reverb on every track.

  6. 6. Turn off sample-accurate automation

    In Audio > General, set Sample Accurate Automation to Off if your automation doesn't need it.

  7. 7. Quit other apps

    Apple says to close everything except your audio interface's software.

  8. 8. Add RAM if you use many plug-ins

    Apple suggests more memory for projects with many plug-ins or Sampler instances.

Sources

Checked November 2026. Logic ProFiles is independent of Apple; menu names can differ slightly between Logic Pro versions.

Frequently asked questions

What does Logic Pro error -10011 mean?

+

The audio engine couldn't process all the data it needed in time. A 2014 blog post on the error describes it as the Mac lacking resources for real-time audio. Apple treats it as a system overload.

Is -10011 the same as -10010?

+

Both are overload alerts. -10010 adds "Disk is too slow" and usually points at the drive; -10011 usually points at the processor.