No CPU Peak Solution (AAE-9173) in PT 12.7 ?!? :((((((

[Franklyn]

I've been working for over a year now wirth only 40% of me CPU because of the known CPU Peak bug.
And in 12.7 still no fix of this importand bug.
very disappointing

[JakeBirch]

It's crazy. I'm at about 25% usage and am getting so many spikes I can't work!

[squareneck]

I'm having a lot of AAE-6101, 9093 and 9172. PT 12.6, OS X 10.12, Mackbook Pro 2015 15". I can even produce the CPU spikes without any session open, just dropping the Buffer Size to 32 and then the CPU meter starts to jump.

They have to do something about it...NOW! But I guess the more people that tells them about this CPU spike bug, the faster the problem gets solved. So come on now everybody. Continue this thread...

[ejinbc]

I was also having CPU spikes at lower buffer settings (e.g. 64 or 128 @ 24/96kHz) in Pro Tools 12.6.1. To settle the CPU meter down I changed the processor affinity for Pro Tools using the command line:

cmd.e x e /c start "ProTools" /affinity FC "C:\Program Files\Avid\Pro Tools\Protools.e x e"

<remove spaces in ".exe" above>

This starts Pro Tools with 6 of 8 cores. The other 2 cores are then left to the system. If you look at the CPU usage in Windows the freed up cores can be quite busy - actually higher activity than the Pro Tools cores at 64 buffer.

This solved the spikes for me. As long as I don't try to run too many plugins at low latency (i.e. when recording), 6 of 8 cores on a 3770K @ 4.5 GHz is plenty of processor.

Hope that helps.

[Extreme Mixing]

Is there a terminal command for that on a Mac?

Steve

[littlesicily]

Same issue here. Sucks!!

[tomorrowstk]

In OS X it doesn't set processor affinity the same way as on a Windows OS. The issue with that in OS X is that we get the process handling all over the physical and virtual cores. Example: Lets say you have a mac pro 3,1 with 2 physical quad core processors. We get the errors from PT because the application looks to the kernel for processor affinity. That kernel tells it to spread the workload across all 8 cores of the 2 physical quad core processors. The errors that we get it PT are due to the fact that the kernel doesn't tell PT to handle threads on the same core from the same physical processor. Ok so this is getting hard to explain but if some of you folks want to mess around with processor affinity in OS X in a round about way you can.

1. boot in to the recovery partition of the mac or boot from an install USB or DVD.

2. Open the Terminal.

3. Enter this code in the Terminal. Keep in mind that you will need to know the physical processor and cores per processor. The command below would make your mac think it only has 1 physical CPU. You can test by changing the number up or down between the number of cores as well.

sudo nvram boot-args="cpus=1"

then click enter. Then quit terminal and reboot.


Anyhow you must only mess with this stuff at your own risk.

My old 8 core 3,1 mac pro runs PT great as it sits, but I have tried this in the past and I must say that when I had the system only using 1 physical processor with its 4 physical cores running that the CPU spikes were gone.

Anyway this is not a fix but for the guys that like to tinker and find out on their own this is a good start.

Thanks for listening.

[lesbrunn]

It helps tremendously when I disable core 0 on my 6-core Windows 10 system, but it doesn't stop entirely. A few spikes still find their way through...

[YYR123]

Wow interesting Remedy did it fix it?

PS doesn't appear to have helped at low buffer settings....


Maybe it's time for me to jump to 12.7.1?

[guitardom]

Windows users need to run latencymon and find out what drivers are causing the issues. This is not normal behavior and is symptomatic of drivers calling the CPU and causing interrupts (dpc latency), or problematic 3rd party plugins. I don't know the Mac equivalent software, but this is more about system problems than PT, it is just terribly sensitive to them.