Quote:
Originally Posted by Keidiek
Playback IO buffer size was sitting at 1028. I also raised it to 2056 but that didn't seem to change things. I changed the Disk cache as per your suggestion(there isn't much recorded audio in my session, just a single comped flute track.)
I'm recording to the internal SSD.
|
OK great a very large buffer size, so that's excluded.
And in this case the fast internal NVMe SSD is the place to record to, I just wanted to make sure a slow external drive is not involved here (they can trigger CPU errors at times), but since you don't have much audio recorded it's likely not an issue. And neither is likely disk cache, but you might as well leave that set to say 2GB... but that takes 2GB away from system memory... which you might need later if you run out of memory for VIs.
Quote:
|
I removed the plugins from the session; I couldn't find a plugin folder within the DAW. When you say remove them from the plugin folder, do you mean I should delete them from the folder on my computer that Pro Tools is referencing to load them up? (I beg your patience if that is an ignorant question.)
|
I mean exactly what I said. You remove the plugin files from the plugin folder. You were a google away from knowing what the plugins live in C:\Program Files\Common Files\Avid\Audio\Plug-Ins. Quit Pro Tools. Move *all* .aaxplugin files in that plugin folder elsewhere (anywhere, but the Unused folder is a good place) and restart Pro Tools. It will automagically put back the default Pro Tools plugins.
I've pretty much already described what to do then... but start by seeing if you can reproduce the problems you have seen, if say that needs leaving the computer alone for a while. (and you should have already disabled all computer, disk drive and USB sleep/suspend behavior) Then put back the third party plugin files in batches, starting with some of the ones you are using/needing most and seeing if you can then reproduce the problem again. The problem may not be so much you get an immediate CPU error, it may be that you get a sequence of things happen that then cause CPU errors (with what sounds more and more like a corrupt session).
As suggested before you should investigate if those sessions are corrupt. Again, try importing the session content into new sessions.
Remove all instances of the DVerb plugin while you do all all these other tests (you don't need to uninstall the DVerb .aaxplugin file, just remove the DVerb plugin insert inside Pro Tools, you can't just remove the plugin as Pro Tools will keep putting it back.). That makes sure you are not being hit by denormalization problems with DVerb. I doubt that is an issue, but it;s trivial to exclude so just do it. You can google denomalization if you want to learn more. Put back DVerb only once you have everything else working great.
Quote:
If I create the session from scratch everything is fine, but if I walk away for two minutes and come back, I hit play and it's irreparably stuck in this CPU glitch. This workaround requires a lot of time, too, since I'm loading up an orchestra's worth of sample libraries, routing them, etc...
From what you're saying I'm wondering if something is wrong with my plugins. In this new version that just "broke" today, I was only using PLAY, Kontakt 5, and one little DVerb on an aux track.
|
Who knows... but again you should always start by suspecting plugins. Did you check that the versions of all the plugins you have are up to date/compatible with the Pro Tools and OS version you have? That's called out in the troubleshooting steps. If you did not do that start there before doing detailed plugin troubleshooting. If you have any suspicion about what is installed grab the correct plugin installers, uninstall the plugins and run them again. It's very easy to mess this up if you have a say a pile of old plugin installs for other DAWs (including having installed aaxplugins plugins) and then drop a Pro Tools install on top of that.
And plugins can cause all kinds of CPU and memory problems by just being installed in a DAW, you don't even need to instantiate them, just have them in the plugin folder. It's more likely that plugins you actually have instantiated in a session will cause problems (esp. ones that corrupt sessions), but don't assume they have to be... except DVerb and other plugins that can have denormalization problems, that issue needs to plugins to be instantiated in the session not just installed.
---
Jeez I made the mistake of looking over the standard troubleshooting steps, these are in bad need of being cleaned up and updated.