Skip to content
Logic ProFilesLogic ProFiles

Fix Problems

Logic Pro system overload — how to find the cause and fix it

A system overload alert means Logic Pro's audio engine couldn't finish its work in time — either the processor ran out of headroom or the drive couldn't stream audio fast enough. Apple's own article gives you a way to tell which: the Performance Meter. Check it first, then apply the fixes for that side.

Owen Hartley Owen Hartley Updated Checked for Logic Pro 13
Overloaded CPU meter in the red next to a music arrangement on a Mac screen

Applies to: Logic Pro 13, 12 and 11 for Mac (menu names may say Preferences in older versions).

Most likely causes

  1. CPU overload — a Processing Threads meter peaks (most common)
  2. I/O buffer too small for the project (most common)
  3. Heavy software instrument track selected during playback (common)
  4. Disk overload — the Drive I/O meter peaks (common)
  5. Sample-accurate automation or a high sample rate adding load (occasional)

CPU or disk? Read the meter

Performance Meter diagram comparing Processing Threads meters with the Drive I/O meter
If a Processing Threads bar peaks, it's CPU. If Drive I/O peaks, it's the disk.
Meter that peaks Likely cause Start with
Rightmost Processing Threads bar One track (usually the selected instrument) is too heavy Select an empty track, freeze, fewer voices
Several Processing Threads bars Overall CPU load Larger I/O buffer, Process Buffer Range Large, sends
Drive I/O Drive can't stream audio fast enough Dedicated SSD, Sampler VM off, lower sample rate — see disk too slow

To find a heavy track, Apple suggests opening the Performance Meter, selecting the track and playing. If the rightmost Processing Threads meter fills up, that track can cause overloads. On Intel Macs with Hyper-Threading each thread shows two meters.

Recording and mixing need different settings

Apple's advice pulls in two directions. For recording you want the smallest buffer that runs cleanly so you hear yourself without delay. For audio-only recording, Apple suggests turning off Software Monitoring in Audio > General and setting the buffer to 256 samples. For mixing you can raise the buffer and set Process Buffer Range to Large, because latency no longer matters. Our buffer latency calculator shows what each buffer size costs in milliseconds, and the latency guide covers the recording side.

If the alert shows an error code

Two coded versions of the alert are common: -10010 "Disk is too slow" points at the drive, and -10011 at the processor. Apple's overload article covers both causes, so the fixes on this page apply to either.

Fixes, in order

  1. 1. Open the Performance Meter

    In Logic Pro 11 and earlier, first turn on Enable Complete Features in Logic Pro > Settings > Advanced; in 12 and later all features are always on. Click the Display Mode triangle in the toolbar, choose Custom, then double-click the CPU or HD meter. Play the project and watch which meter peaks when the alert appears.

  2. 2. Raise the I/O buffer one step at a time

    In Logic Pro > Settings > Audio > Devices, raise I/O Buffer Size one step and test again. A larger buffer lowers CPU load but adds recording latency — use small buffers to record and large ones to mix.

  3. 3. Set Process Buffer Range to Large

    In the same pane, Apple recommends Large for Process Buffer Range. Higher settings add latency, so switch back if you're recording.

  4. 4. Select an empty track during playback

    A selected software instrument track or track stack header adds load. Click an empty audio track before you press play.

  5. 5. Freeze plug-in-heavy tracks

    Freezing renders a track so its plug-ins stop using the CPU. Skip freezing software instrument tracks if the overloads line up with Drive I/O peaks.

  6. 6. Move reverbs and delays to sends

    Put CPU-heavy reverbs and delays on a shared send, not on every track. If you need reverb on a single track, Apple suggests SilverVerb or PlatinumVerb.

  7. 7. Turn off sample-accurate automation

    In Audio > General, set Sample Accurate Automation to Off if you don't need it, or choose the option that covers only the parameters you automate.

  8. 8. Use fewer voices

    Set instruments to the number of voices you actually play. Apple's example is a Sculpture part that plays two notes at once and needs only two voices.

  9. 9. Try a lower sample rate

    Higher sample rates raise CPU and disk load. If disk activity triggers the alert, a lower rate can stop it.

  10. 10. Tune Sampler Virtual Memory

    In Logic Pro > Settings > Audio > Sampler > Virtual Memory, turn Active on if overloads match Processing Threads peaks and off if they match Drive I/O peaks.

  11. 11. Quit other apps

    Close everything except your audio interface's control or mixer software.

  12. 12. Use a dedicated SSD and more RAM

    Save high-track-count projects to a dedicated external drive such as a USB-C SSD formatted as APFS or Mac OS Extended (Journaled). Apple also suggests more RAM if you use 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 causes system overload in Logic Pro?

+

The audio engine can't process everything in time. Apple separates two causes: processor load, shown by the Processing Threads meters, and drive bandwidth, shown by the Drive I/O meter.

What buffer size should I use to stop system overloads?

+

There is no single number. Apple says to raise the I/O buffer one step at a time until the interruptions stop, and suggests 256 samples for audio-only recording with Software Monitoring off.

Can I hide the system overload message?

+

Yes. Deselect "Display audio engine overload message" in Audio > General. Logic Pro then stops playback without showing the alert, so the overload itself still happens.