Another CPU overload thread

[aaronbagby]

Hello out there. I am desperate to solve my current overload problem (AAE -9173).

I am using PT 2019, on a 2018 MBP with 2.9gHz i9 processor with 32 GB RAM running Mojave.

The overloads are happening while trying to print a fairly articulate passage of drums coming from Steven Slate Drums 5 (a full verse of a snare roll, marching band style). The spike to 100% happens at nearly the same spot EVERY pass, with literally every non-related track/bus made inactive and every single plugin disabled. Buffer size is maced at 2048, and I've tried various dick cache sizes. No luck.

The spike is coming down thread six in System usage. Drum samples are stored on a Lacie 2TB external, while audio is being recorded to a separate 2TB SSD. Session is 24bit/96kHZ, which may be a factor. But I'm really hoping I can solve this, it is literally destroying my workflow because I can't get past this verse. Thanks in advance for any insight here.

[massivekerry]

Originally Posted by aaronbagby

Hello out there. I am desperate to solve my current overload problem (AAE -9173).

I am using PT 2019, on a 2018 MBP with 2.9gHz i9 processor with 32 GB RAM running Mojave.

The overloads are happening while trying to print a fairly articulate passage of drums coming from Steven Slate Drums 5 (a full verse of a snare roll, marching band style). The spike to 100% happens at nearly the same spot EVERY pass, with literally every non-related track/bus made inactive and every single plugin disabled. Buffer size is maced at 2048, and I've tried various dick cache sizes. No luck.

The spike is coming down thread six in System usage. Drum samples are stored on a Lacie 2TB external, while audio is being recorded to a separate 2TB SSD. Session is 24bit/96kHZ, which may be a factor. But I'm really hoping I can solve this, it is literally destroying my workflow because I can't get past this verse. Thanks in advance for any insight here.

It's a crap solution, but did you try cutting that part into it's own Clip, selecting the Clip, and right-clicking to Commit that clip, and then muting the MIDI part of that clip in the Instrument track? That might at least get you past that hump.

[jeffro]

Have you tried the changes suggested in avid.force.com/pkb/articles/Troubleshooting/AAE-9093-9173-and-6101-Errors-on-Mac?

[Sam Bell 9]

Although my system config is different, the only time I ever experience the overloads is when using SSD5. My workaround has always been to print out individual drum tracks - 1 at a time (ugh) - and then make the Instrument track with SSD5 inactive. That seemed to brute force me pass the CPU overloads.

Not sure if SSD5.5 will be better, but here's hoping it is when it's finally released.

[JFreak]

Originally Posted by Sam Bell 9

Not sure if SSD5.5 will be better, but here's hoping it is when it's finally released.

Slate is pretty famous for his "coming soon" promises...

[aaronbagby]

Originally Posted by Sam Bell 9

Although my system config is different, the only time I ever experience the overloads is when using SSD5. My workaround has always been to print out individual drum tracks - 1 at a time (ugh) - and then make the Instrument track with SSD5 inactive. That seemed to brute force me pass the CPU overloads.

Not sure if SSD5.5 will be better, but here's hoping it is when it's finally released.

This is something I would try, depending on the workflow, if I can’t get around it anyway else. How does it free up CPU? Surely if the kit is loaded in SSD5, the system reads the load whether the track is recording or not? I can’t even get it to PLAY this passage half the this.

[aaronbagby]

Originally Posted by jeffro

Have you tried the changes suggested in avid.force.com/pkb/articles/Troubleshooting/AAE-9093-9173-and-6101-Errors-on-Mac?

I have tried this, yes, with no avail. Thanks though, it was the first time I'd seen that info