Skip to content
MappleCare Community ↗

MappleCare Community

Reply To: [Solved] How to fix Logic Pro ‘System Overload. The audio engine was not able to process all required data’ caused by CoreAudio thread scheduling buffer underrun with third-party AU plugins (-10011) on MacBook Pro 14″ M3 Pro

Find answers from other Apple users or start a discussion about your device.

All Forum Rooms

Home › Forums › Logic Pro, Final Cut Pro & Pro Apps › [Solved] How to fix Logic Pro ‘System Overload. The audio engine was not able to process all required data’ caused by CoreAudio thread scheduling buffer underrun with third-party AU plugins (-10011) on MacBook Pro 14″ M3 Pro › Reply To: [Solved] How to fix Logic Pro ‘System Overload. The audio engine was not able to process all required data’ caused by CoreAudio thread scheduling buffer underrun with third-party AU plugins (-10011) on MacBook Pro 14″ M3 Pro

#12419
Harper Bryant
Community Contributor
Apple Recommended / Verified Community Solution
This canonical solution was verified and marked as solved in the Apple Support Community archive.

Increasing I/O buffer sample size, maximizing processing threads, and freezing high-CPU synth tracks.

Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

  1. Navigate to Logic Pro > Settings > Audio > Devices and set I/O Buffer Size to 512 samples (or 1024 for mixing).
  2. Set Processing Threads from ‘Automatic’ to the maximum available performance cores.
  3. Enable Track Freeze on tracks with resource-heavy synthesizers or convolution reverbs.

Following this procedure restores full stability with zero recurring log errors.

Mac Studio M2 Max (64GB) | Neumann KM184 Pair | Logic Pro 11 | Bristol, UK
Apple Certified Support Professional (ACSP) | Classical Pianist & Spatial Audio Arranger