View Single Post
Old 03-03-2020, 08:34 PM
Darryl Ramm Darryl Ramm is offline
Join Date: Nov 2010
Location: USA
Posts: 14,394
Default Re: yet another cpu overload thread

In addition to systems details you also don't describe your interface, or the session sample rate, or what Disk Cache is set to. We also have no idea what drive you are recording to, a stupidly slow drive can cause CPU overload errors.

Looking at CPU meters rarely provides any useful insight.

Trying to upgrade OS versions was likely a waste of time. I really hope you did not do an in-situ upgrade. That is really never recommended, and if you system is having problems/deeply messed up it may not fix things or may make them worse.


There is a pretty standard approach to tackling CPU overloads that you should have tried/be trying now:

As always start with trashing prefs, and checking your system is properly optimized and then trash prefs periodically as you do other troubleshooting, use Peter Gate's tools to help you trash prefs.

And you always then assume plugins are the cause of CPU overloads and try to find suspect plugins. Move *all* .aaxplugin files from the plugin folder to the unused folder and trash prefs. Pro Tools will put back the default ones. See how that works, you won't have many of the plugins you want, but it's a quick test to see... if things are still having problems then you have some other issue. Then try moving about half your 3rd plugins back, trashing prefs, testing if that works. Keep splitting third party plugins groups into half adding or removing them to do a binary search to try to find the problem plugin (or plugins). It may be more likely it's a plugin you are using... so you can start testing with those, but as pointed out it may be a plugin (or several plugins) you are not even using. Your goal is to make large dramatic changes, not slowly step through stuff, to quickly see if you can try to identify posible causes.

If removing all plugins did not solve the issue the it's lower probability stuff like possible corrupted sessions (test with a new empty session), bad interface drivers (test using Built In Output as the playback engine), stranger corrupted prefs of other things (create a new admin user and test from that account). If nothing there helps and can try a full clean reinstall of Pro Tools. Still stuck, then grab a spare drive or partition and do a clean full install of macOS and Pro Tools and ILM and nothing else and test that with Built-In output and then install device drivers and third party plugins, testing as you go. If that all works OK then clone over your old boot drive/partition.

There are many many posts on DUC outlining this standard troubleshooting approach, unfortunately people here really never guesses what a CPU overload cause is. So asking here won't help you, you need to work through this troubleshooting stuff yourself. And if you then are still stuck and need help post here with all you system info, and a clear description or exactly what troubleshooting you have done.
Reply With Quote