Logic Pro 11 and System Overloads on a 9 audio track project

Question

Level 1

4 points

Logic Pro 11 and System Overloads on a 9 audio track project

Using a Mac Mini with a M2Pro processor running OS Sequoia 15.6 with a Universal Audio Interface Modell Twin X Gen 2 Quad DSP

Introduced Izotope Neutron 5 and other Izotope plugins into the tracks. No Logic Pro plugins used. Using the Universal Audio Control Panel only in the Unison box that provides specific Preamp.

No issues with system and software capacity until I introduced Neutron 5. The wierd thing is there is NO System Overload during several full project playbacks. But I do get System Overloads in the same location (1/2 way through the song/project). I've increased threads to the maximum of 10 (6 high capacity cores). Using 1024 for playback.

I'll get the System Overload then I'll start the playback from the beginning and it plays through without any System Overload. When there is an Overload...the Performance Meter using 3 threads reads about 60%.

Apple Advisors have been great. They've walked me through making several of the changes mentioned in this Help Request. However, the Advisor does not understand why I'll get a System Overload on some playbacks of the same project and not at other times.

The Advisor thinks that the issue is in Logic but that it is a combination and not just one factor causing this.

Izotope is a CPU hog and can achieve 60 to 70% CPU capacity. I watch the Logic Performance monitor to observe the Threads... Only 3 threads are being used by the Logic Pro System. I read that Logic will increase the number of threads automatically if needed. So 3 threads even though it is set to 6 threads.

We all share frustrations when the passion of recording is interrupted by overloads and that a permanent fix can't be achieved. There are work arounds in the workflow such as freezing some of the tracks but there shouldn't be a need to do this given the processing power of my computer.

Those of you familiar with UA interfaces = when a Native plugin like Neutron is used, the UA interface does not process the plugin using its internal DSP. Instead, the Native plugin is passed through to the computer and the DAW for processing.

H E L P

Mac mini (M2 Pro, 2023)

Posted on Sep 7, 2025 6:06 PM

Reply

Answer 1

Top-ranking reply

yoyoBen

Level 4

3,403 points

Sep 8, 2025 1:20 AM in response to Alanw313

Alanw313 wrote:

Using a Mac Mini with a M2Pro processor running OS Sequoia 15.6 with a Universal Audio Interface Modell Twin X Gen 2 Quad DSP

This setup should run fine.

Introduced Izotope Neutron 5 and other Izotope plugins into the tracks.

I don't own Neutron 5. So I can't say anything about it. But you could do pretty complex routings and processes with the plugin which may cause high cpu load. What other izotope plugins are you using? If you are using RX then you should bounce your tracks.

But I do get System Overloads in the same location (1/2 way through the song/project).

If it's always on the same spot, then it's because the plugin starts to work here heavily. You know better what is happening in your arrangement here.

I've increased threads to the maximum of 10 (6 high capacity cores). Using 1024 for playback.

Set your Processing Threads always at "automatic"

I read that Logic will increase the number of threads automatically if needed. So 3 threads even though it is set to 6 threads.

There is a characteristic in Logic's programming, some call it a flaw. Logic does NOT distribute the cpu load across all cores equally.

M4 Pro MacBook Pro: HUGE Leap for Music Production | M4 Pro vs M3 Pro vs M2 Pro vs M1 Pro

There is another strange thing you can try. Try selecting a different track while playing. There is a strange relationship between the selected track during playback and the CPU load. There are several threads describing this phenomenon.

How much free space is left on your system drive and the drive you are working on?

Reply

Answer 2

yoyoBen

Level 4

3,403 points

Sep 8, 2025 6:25 AM in response to Alanw313

the Sweat water advisor said that was incorrect and I should set up a bus for each track and reserve individual tracks for neutrons individual modules

Yes, this is the preferred method to lower cpu load. Don't use send here, just rout the outputs to the bus with Neutron inserted. Similar to that you should put the reverb and delay on busses, but in these cases use sends.

bouncing— I use bnc of course but the bounces seem to lose some of the tone compared to when I play the track directly before bnc

I mean either bounce in place (the tracks!) or just freeze the tracks. Freezing gives you the opportunity to make changes easily, actually this is more convenient than bouncing tracks. Keep in mind "freezing" only works on individual tracks but not on busses and auxes.

Reply

Answer 3

Alanw313 Author

Level 1

4 points

Sep 8, 2025 5:34 AM in response to Alanw313

Thank you for your thorough and excellent response.

mMy Mac Mini has a 1T of storage with 50% remaining.

I will go back and set threads to Automatic as suggested by you.

Izotope neutron 5 and Nectar 4 for verb and delay are the 2 plugins being used by me.

Neuton 5 has a Mother Ship that contains all of the plugin modules in addition to an Automatic feature that reads each track for about 3 seconds and then graphically shows a wire curve suggesting an optimal eq for the track. In addition you can also activate all or some of the modules or some of them — such as eq, Compression, execitor, density, and others. When the Automatic feature is selected it also suggest settings for selected modules. Each of these modules are provided in the package and can be activated separately on a track or tracks.

per the manual, I put the mother ship on rack of the audio channels to get this suggested beginning point. In addition initially I had dome individule modules on tracks

this feature is important to me because I lost some hearing capacity — highs from years of playing guitar in bands in venues so I have hearing aids.

So gettin an initial adjustments on individual tracks is a frustrating multi week effort. So Neuton 5s Automatic feature takes me to 60% and from there I can make tweaks.

Using this approach on the 8 audio tracts caused system overloads almost immediately.

the Sweat water advisor said that was incorrect and I should set up a bus for each track and reserve individual tracks for neutrons individual modules

i set that up as a template last evening and got a system overload half way in at the beginning of the guitar lead. 4 threads logic assigned were only at 60%. Played song recording again and didn’t get any overloads with threads at the same level. But I did not use the automatic feature on the busses.

yes, I can do workarounds and hopefully get it to work correctly. I don’t want to compromise the production snd totals mix

lastly, a major concern of mine is what happens to the system when I insert some plugins into the master bus and what happens to my ability to Master and use the Neutron Master component

bouncing— I use bnc of course but the bounces seem to lose some of the tone compared to when I play the track directly before bnc