11.1 and 11.2... still getting CPU spikes?!

[kilroyrock]

So i saw there was an 11.2 update so i held off posting until I got the latest version, as it said it fixed some mastermeter spiking...


Has anyone else been seeing their processors at 30-40%, and getting intermittent 100% spikes, that cause drop outs? It then drops back to 45% and everything's fine, and then 5 seconds later, jumps back up to 100% and then back to nothing, over and over again. It's driving me nuts! Didn't start happening until the last few updates this year..

2.5ghz core2quad, 16 gigs ram, dedicated firewire card... i've got the horsepower.

Suggestions?

[drumster]

I just started using Protools 11 and have been experiencing exactly what you've described above. I'm on Mountain Lion 10.8.5 with an early 2013 Retina MBP and the CPU spikes cause error messages when playing back the demo song session that comes with Protools 11. Everything plays fine in PT 10. The other thing I've noticed is that one of the 8 cores available to Protools is spiking significantly more than the others in the system usage window. In my particular case, this happens to be the 4th core. Adjusting the recording buffer in Protools does not make a difference. The spikes can happen even when there is no audio playing and the transport is completely stopped.

[Intransit]

What could be causing this… Certain plugins in certain orders.

I found months ago after moving all my plugins one by one that with HD Native any Sound Toys Plugin placed after NI Massive causes Cpu spikes with literally nothing else in the session.

https://www.dropbox.com/s/mr5egdq8lq...undToys_NI.png

So try deactivating your plugs one by one and see if it stops. If so you know which one it is.

[Intransit]

Originally Posted by kilroyrock

drops back to 45% and everything's fine, and then 5 seconds later, jumps back up to 100% and then back to nothing, over and over again

BTW. That's exactly what mine was doing until I moved all my NI Massive processing to Aux tracks and bused there. It's just ST and Massive that don't get along. My test was only with HD Native.

I've also seen similar with Waves Gate placed before Sugar Bites WOW2.

[kilroyrock]

I am definitely using ST's microshift ... I will look into that! Stinks too, cause they just released an update and it didn't fix it there either.

[bluemoa]

Originally Posted by drumster

I just started using Protools 11 and have been experiencing exactly what you've described above. I'm on Mountain Lion 10.8.5 with an early 2013 Retina MBP and the CPU spikes cause error messages when playing back the demo song session that comes with Protools 11. Everything plays fine in PT 10. The other thing I've noticed is that one of the 8 cores available to Protools is spiking significantly more than the others in the system usage window. In my particular case, this happens to be the 4th core. Adjusting the recording buffer in Protools does not make a difference. The spikes can happen even when there is no audio playing and the transport is completely stopped.

It happens to me with Melodyne and Sansamp PSA-1 plug-in in PT 10 and PT 11.2 and 11.1.3. It was working fine until I upgraded from os x 10.9.2 to 10.9.4 as well as the latest PT versions. It was working well before that. Pretty lame, serves me right for trying to update something that wasn't broke.

[Intransit]

Originally Posted by kilroyrock

I am definitely using ST's microshift ... I will look into that! Stinks too, cause they just released an update and it didn't fix it there either.

At least you can toggle the analog mode without issue and the midi sync update is VERY welcome. Tremolator was driving me nuts every time it past a meter change.

But ya, No Cpu issue fix. I've been talking to someone there about it though. So they do know.

[JFreak]

10.9.4 isn't supported yet. Hopefully I heard the rumors right and the 11.2.1 maintenance release is right around the corner.

[kilroyrock]

So it's even across Windows and Mac, cause I'm on Windows 7.

[Rosco1969]

I have exactly the same thing happening. Every few seconds, for no reason the CPU would hit 100%, Protools would drop out then the CPU would go back to around 36%. Then a few seconds later, the same thing.

I managed to track it down to VCC Mixbuss (VST), through Patchwork.
As soon as I made all the instances of that inactive it stopped spiking. I have the VCC channels all over the place and they seem to fine. Only the Mixbuss.

Through an instance of Satson Mixbuss in it's place and all seems to be ok so far.

Interestingly enough though, it seemed to happen more when tracks were soloed.

Might be worth trying that.

Rosco.