Logic Settings
-
- KVRian
- 807 posts since 7 Aug, 2015 from H2O
I have a late 2012 Mac Mini with 2.6 GHz quad i7, 16 GB memory. It runs great, cpu-wise at 128 buffer, though I usually have it at 256 - with many instances of "high-cpu" plugins such as Bazille or Diva. The problem is when I start adjusting any plugins, volume, e.q., whatever, and then it spikes with popping. Even at 512 buffer it does this. I'm hoping there's something I can change in my settings to stop this?
-
- KVRAF
- 2473 posts since 25 Sep, 2014 from Specific Northwest
Do you mean adjusting from the mixer?
Make sure that multi-core is enabled on your u-he plugins, as well. That should help distribute the CPU load better.
Make sure that multi-core is enabled on your u-he plugins, as well. That should help distribute the CPU load better.
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
-
- KVRian
- Topic Starter
- 807 posts since 7 Aug, 2015 from H2O
No, sorry, poorly described - it's when I'm adjusting anything on a plugin's UI. But I just learned something a few minutes ago that I didn't know - from this article: https://support.apple.com/en-us/HT201838 -
that when you have a track highlighted, it's prepared to play each plugin "live," which really hits the cpu. What I don't understand, is that when I had a dual core Mac Mini with only 8 GB of memory and an i5, this never happened...
Bottom line - I no longer have this problem if I have an audio track selected while working with a different' track's plugin's UI. The slightest inconvenience of a different work pattern than what I've gotten accustomed to, so, unless someone has some advice, it's my work-around.
Edited to add: For my setup, choosing 8 processing threads instead of the automatic setting seems to have been my issue. I don't find this anywhere in searches online, which is odd, but just through experimentation. Now Logic is behaving just fine even if I have a synth track chosen/highlighted and using it's UI - (with buffer at 128). Problem solved.
that when you have a track highlighted, it's prepared to play each plugin "live," which really hits the cpu. What I don't understand, is that when I had a dual core Mac Mini with only 8 GB of memory and an i5, this never happened...
Bottom line - I no longer have this problem if I have an audio track selected while working with a different' track's plugin's UI. The slightest inconvenience of a different work pattern than what I've gotten accustomed to, so, unless someone has some advice, it's my work-around.
Edited to add: For my setup, choosing 8 processing threads instead of the automatic setting seems to have been my issue. I don't find this anywhere in searches online, which is odd, but just through experimentation. Now Logic is behaving just fine even if I have a synth track chosen/highlighted and using it's UI - (with buffer at 128). Problem solved.