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

[Recording Room]

For BFD3 I agree it's been a dog for stability. They have a public beta, make sure you get that because it is a lot more stable than any previous releases. I couldn't use a previous release for more than 10 minutes before it crashed. Now I can at least work for a bit and then export tracks to audio and disable the plugin completely.

[jafejo]

Ihad the same problem with the spikes, im on a mbp i5 mid 2010, 8 gb ram, ssd osx and apps, optibay for files 7200rpm, i don't know what it could be the reason of this problem. my session it's at 30% and randomly spikes to 100%.

salutes !

[drumster]

I've done quite a bit of testing today on 11.2, and in my particular setup (Retina MBP, Mac OSX 10.8.5 & HD Native Thunderbolt) I may have isolated the problem to the Sans Amp plugin. Deactivating this plugin in the session seems to bring more CPU stability and gets rid of the random spikes that hit 100%.
Hopefully, this bug gets addressed in the next update.

[fsavell]

I have a particular session where I get spikes roughly every 20 seconds, while the Total CPU averages around 30-40%.

I removed Blue Cat Audio MB-7 (which was running the ever problematic Slate VCC) and the session now no longer has CPU spikes. More to the point, it seems mostly isolated to me running a stereo instance of MB-7 with two Slate VCC Mix buss plugins within it on my stereo Aux. If I inactive the MB-7 on my Stereo Aux, it appears, for me at least, to solve the spiking issue.

Upon reinstallation all the spikes returned. What's interesting is that I noticed a lot more spiking while the Disk Cache was loading, where even the Disk Cache meter itself was spiking. Once the Disk Cache meter had turned green, there were a lot less spikes, but they still occurred every minute or so.

Anyone else running Slate VCC within MB-7? I'm still scratching my head over it though, as I have had hundreds of other sessions running this plugin combo without the intense spiking issue. Maybe it was always there and i've been putting up with it, only just investigated because of this thread.

Forrester

PT11.1.3 HDX2 MacPro 12-core OSX10.9.3

[YYR123]

I had one recently and it was UAD's live mode

[Righty27]

Relieved to come across this thread - surprised I hadn't seen it earlier! Another regular 'spiker' here - can't reliably set aside some time to work on a project as, around half the time, I end up battling with continuous cycling/peaking red line/100% problems. I initially thought the last PT upgrade had resolved this issue but this wasn't the case.

I too have tried to rule out specific plugins - reading through this thread actually suggests that this is unlikely to be the issue. As I try to get by with an unqualified system, I've stopped short of complaining too much as I'll inevitably end up with a list of other things to fix first.

My current focus is on sleep/standby (which I know should be 'off') - I use a utility (Caffeine) on my Mac to temporarily disable this but find that, when I am working on a session without issue and leave it for a while then return, the spiking sometimes returns.

It would be great to just get PT11 working reliably, as advertised and with all my plugins available ... just used Slate VTM the other day for the first time since giving up with it in PT10 so now waiting just for VCC but still have to consider PT completely unreliable unfortunately. If this only gets fixed in a major update e.g. the Avid Everywhere version with track freeze, Avid would be seen to have treated their first 64-bit users as little more than beta-testing financing for an intermediary version 11. I can't believe this problem is not acknowledged on their release notes as a known issue - evidently none of us here have opened a support ticket?!

[Rosco1969]

Definitely Schlate VCC with Patchwork for me. Remove it and the problem is fixed. Oh, and before the Steven Slate brown tounguers get on their high horse, Patchwork with ANY other VST plug works fine, so there is only one common denominator. At least on my system.

[jafejo]

i tried deactivate sans amp plugin that i was using and it's solved at the moment the spikes.....

weird....

[Darryl Ramm]

Originally Posted by jafejo

i tried deactivate sans amp plugin that i was using and it's solved at the moment the spikes.....

weird....

Could you please do everybody a favor and do the experiment of sticking the dither plugin in front of Sansamp and see if it behaves better (try dither at say 20 and 16 bits just for grins)? That helps see if this is our old nemesis denormilization.

[writeroxie]

Originally Posted by Rosco1969

Definitely Schlate VCC with Patchwork for me. Remove it and the problem is fixed. Oh, and before the Steven Slate brown tounguers get on their high horse, Patchwork with ANY other VST plug works fine, so there is only one common denominator. At least on my system.

Could be something there. I had all hell breaking loose on 11.2 until I reinstalled OS & everything. I left Slates VCC & FGX out this time around and it's much more stable. Its not the ONLY thing different about my install, but I'd put Slate on the short list (with, according to recents posts, Sans Amp). With that said, people are having this similar CPU issue and say they have ZERO 3rd party plugs installed... so I'm still looking at Avid.