Search on Sister site for "Scan Intel AU" it has been post yesterday. the app has been made specifically for Logic user to identify Intel component that are wrapped via rosetta while using logic natively. It's really handy, and you'b be surprise to see how many plugins are still not ported to ARM64. it will only list you the component which are intel only.

 

I'm using Logic for about 30 years now, did projects when it was MIDI only, with single core CPU, later the first audio plugins and so on. Today my small MacBook Air M1 is capable of doing everything we could ever have dreamt of 20 years ago including tons of hardware gear. But it's not advancing this fast anymore. Today stability is more important to me than how many instances of Diva I can run. And I really hate the "Recover or Quit" shit going on in Logic for a while now.

 

as I'm the one who made this app i double what Denshin suggested, check your binaries with "Scan Intel AU"

on top of that i would:

1 Check Logic>Preference>audio and be sure that processing threads match your CPU setting (avoid Automatic)
2 put your Buffer size at max (1024)
3 open activity monitor and check if any background application could cause heratic CPU Usage (other than logic and AUhosting service)

report us the result. also giving us the exact model of mac, OS and logic version is always handy in this kind of post.
i'm on M3 Max 14core (10 performance/4 efficiency) Logic 11.1 and honnestly i didn't find a way to overload the cpu so far.
as MyFanwy Stability of some plugin (which are more linked with intel Wrapped with rosetta or really bad optimisation like Madrona Labs) is more the issue right now.

ps: when you are in activity monitor if you go to menu>window click on CPU history, there you'll be able to monitor every single core separetly, which can also reveal some twisted behaviour.

Cheers

 

Cheers @Creme, just was over at the GitHub page, .... looks like a useful utility indeed. Thanks for creating, will definitely give it a run...

Thanks for creating and contributing.

 

CPU's don't have feelings and won't get hurt no matter what you say or do, that being said, you should still be nice to your computer and buy your CPU something nice, every now and again..

 

One plugin eating 15% CPU is the equivalent of fifty plugins eating 0.3% CPU each. In many cases, replacing the least efficient plugin with a better programmed alternative of the same quality will carve substantial headroom for more plugins.

 

First off, Thanks for the tool!

I ran it to which I didn't find anything I actually use actively in my sessions - I will get rid, but I don't see it making any change as I don't use them


im guilty of not looking at the activity monitor to which the AUHosting is concerning me.. is this right? 115.2!

I ran the below to test as just a mastering and it shat the bed instantly - I know its a lot but... I feel this machine should be able to keep up



Im on MBP M1 Max 32gb ram 10cores 8 high performance and logic 11.1.1 - my settings was already pushed to what you mentioned

 

Your CPU activity are absolutely fine. The AUhostservice is just a sansdbox that isolate the AU process from logic (for beter stability). 115% of CPU is absolutely fine as The CPU % shown in Activity Monitor is per core. On a multi-core processor, the total percentage can exceed 100% because it's a sum across all cores. (a 10-core CPU can reach up to 1000% total usage (100% per core)
What surprised me is your idle which seems high and could mean there is a real inefficiency in somewhere.

What i would do, go to Activity monitor>Window>CPU History (keep CPU History in front) and run the exact same test or even, open the same plugin chain one by one and check the cores activity live and evnetually your Idle Wake up to see how it goes.

Happy New Years!

 

Your CPU is like a tube amp, only works well if cranked. That's why, I recommend using only the original, bloated Acustica Audio plugins for that warm, saturated CPU sound.

 

Should the GPU time be that high for the AUhosting process also?

@liquidpeanut, Are you using a second display on your Macbook with it set to a resolution like 4K, 5K?

About the audio plugins, I tested and dumped that Unfairchild plugin immediately because of its performance vs sound. You have that Vision 4X plugin disabled but in your project; another I dumped in about 5 minutes testing also. A visualization plugin like that run amok could definitely present itself with your GPU anomaly. Izotope Insight 2 is much better, as are a number of others. Your channel strips are too narrow to see this, but are you running 2 full instances of Ozone 11? From an audio engineering perspective, not much about your session chain makes much sense to me.

That plugin Kraftur from Soundtheory? Has a known GPU problem on Windows machines, freezing, lagging, etc. I would go through your session and remove things one at a time. I would also send all your channels which are going to buses back to your Stereo Output for testing. Any lag, latency, or other performance issues are very easily compounded that way. Remember that Logic is going to be compensating for all that latency, unless you disable it in your preferences.

Going back to the original topic of the thread, you have answered your own question in a way. Your problem there is very likely stemming from a paid plugin. You need to troubleshoot it in a methodical way.

 

Last edited: Jan 1, 2025

Could be, but it's complicate to say as i don't have half of the plugin in his session, therefore i have no idea how much of those "rely"on GPU (rendering waveforms, spectrograms, live metering etc..)

 

I do but its not 4/5k, and ive on had it a matter of weeks so doesn't relate to this, and im not using full instances lol just the odd module, and I haven't had to many uses with Kraftur but I think the newer visual spectrum plugins tend to be on the problematic side, I just got mega oscilloscope and spectrum 2 so im hoping I can back off vision 4x, as the the main thing im after is the summed volume of busses, but this was a heavy session I don't usually use this much but I will test with activity monitor and monitor culprits

 

In all the years I've installed Waves Bundles I have never ONCE had a problem with them.. The only thing I can suggest is they can be fiddly to install, so possibly a faulty installation could be the problem, but with the plugins themselves? I started with Waves bundle version 4 and never had an issue.

 

None related to this I was planning to make a move to Studio one 7 and I feel this is the best move long term from logic at least from a mix master perspective, ill report back my findings here should I come across the main culprit of my bottle necks!

 

It does hurt the devs for sure ..

 

Logic is not perfect (as no DAW are perfect), but my feeling always made me think that Studio One was a risky option for the futur considering how badly presonus has been following with there driver update in the past. The most resilient one for me might still be Cubase, Logic and eventually Ableton.

 

I'm curious as well but not about CPU usage. I'm curious about Blue Cats Patchworx I think it is? What is this? I'd love a way to check plugins and not have to wait an hour for all 2100 to scan on a DAW LOL

 

I use Patchwork for that purpose more than I ever use it for in my actual projects. You can use the Standalone version even while your DAW is left open. You can kg stuff, test it, check other format plugins if there is a problem with the one you normally use, etc. It also lets you use k'd plugins of other formats in Protools.

You can use it to make preset chains to quickly load them also. If you like to use a template, but have not really pinned down what you want in a specific spot; you can load up a bunch of same-type plugins and bypass others. Like an A-B comparison tool. It is one of the best utility products around. Of course, I do not have anywhere close to 2100 plugins on my machine ever. Not even close. That causes Analysis Paralysis.

 

Sounds like I definitely need this tool, I found it on sister site

 

Don't forget to firewall the standalone application and the plugin versions you install. The same way as if you were running plugins in your DAW.