Logic Pro only using three threads (despite threading-friendly project structure, afaik)

Question

Level 1

4 points

Logic Pro only using three threads (despite threading-friendly project structure, afaik)

I'm on a new (Nov. '23) Macbook Pro. M3 Max chip, 36GB RAM, 14 cores (10 high performance, 4 efficiency). I have a project that's been running fine, so I haven't been watching the Performance Meter. But it started giving "System Overload" messages. Turning on the Performance Meter shows that it's only using three threads (the first one overloads, the second is under 75%, and the third is under 50%). Other projects I load use all ten threads that Logic allots when the "Processing Threads" setting is set to "Automatic (Recommended)."

I did just get some new, probably CPU-heavy-ish plugins that I've been using liberally. But my project has 10+ tracks (treating those bussed exclusively to a single aux track as one) (a mix of audio and MIDI), plus a few aux tracks for sends. So even if a single channel strip (with the output set to "Stereo Out") has to go to a single thread, it doesn't make sense (from my understanding of how Logic's threading works) that several tracks (with "Stereo Out" outputs) would be allotted to a single thread until it overloads, while available threads go unused.

This all happens even if I select an empty audio track (though I don't think that trick would really relate to this issue).

Any help is appreciated.

MacBook Pro 16″

Posted on Nov 17, 2024 7:33 PM

Reply

Answer 1

avrvae Author

Level 1

4 points

Nov 20, 2024 2:06 PM in response to avrvae

Update: sorry if it wasn't due diligence to try this before posting, but there is one track I can power down or freeze, and if I do that, all the processing threads start being used. That track has no plugins on it that aren't on other tracks too. If I duplicate the track (and the new track isn't powered down or frozen), some of the unused processing threads come back online, but not all of them.

So I don't know. I've had problems with Logic's threading before, but it seems like I'm on track resolve this. But it may just be some form of bug or corruption.

Reply