"Pro Tools ran out of CPU power" message, then unusably glitchy playback afterwards

[Oneland]

I too have the same issue since I've upgraded to Protools 12.4. I use a Macbook Pro 15" 2.2GHz i7 with 16GB and a 256GB System Drive and record onto a Lacie Rugged SSD Thunderbolt.

I record at least 16 tracks at the time at 24bit 96kHz and I keep getting error messages aae 6101, 9073 at random times. The buffer is always set to the largest as Latency is no concern. The Cache size is set to maximum (12GB).

I though for a while the issue came from my setup somehow but I tried to do the same thing using Reaper (with default settings) and it worked with no problem.

I've tried trashing the preferences, disk repair but no luck.

Any ideas? It's the fist time I have a Protools system that's so unstable and makes recording so unreliable.

[cmbourget]

Originally Posted by Oneland

The Cache size is set to maximum (12GB).

With my system (WIN 7), the maximum cow is bad (it removes capacity to the system). It's better to let PT manage the cache with the standard or "normal" option.

[john1192]

i have had this happen a couple of times now .. toggling Buffer Settings usually helps !!

write some new F'ing Code that works PLEASE !!!!!!

[YYR123]

Originally Posted by john1192

write some new F'ing Code that works PLEASE !!!!!!

This is a down side to the quick release scheme > not enough time for internal beta testing

[spaceman]

Getting this too, even when the CPU is not being taxed. It then sometimes results in distortion across all tracks only solved by relaunch of PT or full restart.

[mustgroove]

Originally Posted by spaceman

Getting this too, even when the CPU is not being taxed. It then sometimes results in distortion across all tracks only solved by relaunch of PT or full restart.

Yep it's the same for me here - happens when CPU usage isn't really high at all... and sometimes when there's barely any plugins in the session at all

[dr_daw]

What buffer setting are you at? Every since trashing prefs, disk repair and FULL reboot I've only had this happen once and it's because I opened a session that was set to 32, and it was a plugin heavy track.

Try moving all your plugins to the unused folder and see if it still happens. Then put the Avid plugins back, leaving out all third party and Avid VI's. Test that, then add each VI one at a time and test. I've had problems with some of the AIR instruments in the past.

[mustgroove]

Originally Posted by dr_daw

What buffer setting are you at? Every since trashing prefs, disk repair and FULL reboot I've only had this happen once and it's because I opened a session that was set to 32, and it was a plugin heavy track.

Try moving all your plugins to the unused folder and see if it still happens. Then put the Avid plugins back, leaving out all third party and Avid VI's. Test that, then add each VI one at a time and test. I've had problems with some of the AIR instruments in the past.

512 samples... not exactly small.

Will see if I get the time to do an exhaustive elimination test like this, in the meantime I'll see if disabling Dynamic Plugin Processing has any effect

[dr_daw]

Originally Posted by mustgroove

512 samples... not exactly small.



Will see if I get the time to do an exhaustive elimination test like this, in the meantime I'll see if disabling Dynamic Plugin Processing has any effect

I'm pretty sure you mentioned earlier that you did a prefs trash and disk repair right? But I vaguely remember you saying that you're recording/playing back from a SSD system drive, correct?

I would try to move the sessions to an external drive that's qualified.

[spaceman]

Sessions on external qualified Avatar drive. Buffer at 512 or above. Same issue.