CPU spiking 11.1.1

[wesm]

Just installed 11.1.1. A session with 24 tracks that played with plenty of headroom under 11.0.2 will instantly barf with "out of cpu" on 11.1.1.
PT thinks it is using 100% of all available CPU; Activity Monitor thinks it is using 120%, but that's over 8 cores, so really ~ 15% total cpu capacity.

This sucks.

Mac Pro, 3,1 (yeah, I know, unsupported)
OSX 10.8.5
2xquadcore 2.8GHz
22 GB ram
lots of 7200 rpm disk

Gotta change the sig...

[Darryl Ramm]

Kind of usual questions -

How did you upgrade to 11.1.1? Did you select "Replace" as Avid recommends?

What *exact* error message and error number do you get?

Does Activity Monitor show any anything else running using much CPU or memory other than Pro Tools?

Are there any "interesting" looking events/warnigns/errors in the system logs (in Console.app) around the time this happens?

Does this happen to only one session?

Does this happen with only one or a few specific plugins in any session? Which one/ones?

What happens if you disable dynamic plugin processing in the playback engine settings?

What happens when you remove all third party plugins from their AAX plugin folder? Yes even if they all appeared to work OK before the upgrade. They have to be removed, just not using them is not always enough. Can you make any session go CPU crazy then just with the standard plugins?

[wesm]

Found the problem: Avid's own MasterMeter plugin.

[wesm]

Originally Posted by Darryl Ramm

Kind of usual questions -

How did you upgrade to 11.1.1? Did you select "Replace" as Avid recommends?

What *exact* error message and error number do you get?

Does Activity Monitor show any anything else running using much CPU or memory other than Pro Tools?

Are there any "interesting" looking events/warnigns/errors in the system logs (in Console.app) around the time this happens?

Does this happen to only one session?

Does this happen with only one or a few specific plugins in any session? Which one/ones?

What happens if you disable dynamic plugin processing in the playback engine settings?

What happens when you remove all third party plugins from their AAX plugin folder? Yes even if they all appeared to work OK before the upgrade. They have to be removed, just not using them is not always enough. Can you make any session go CPU crazy then just with the standard plugins?

No, didn't do replace.
Activity Monitor pretty quiet, as I said, only 15% total cpu capacity used by PT, not much else going on. Only one session, the one with MasterMeter.

Thanks,
//w

[mrtomcat]

11.1 started having quite a few cpu spikes that I didn't have in 11.0.2 and 11.1.1 has not fixed those (still on Mountain lion)
I noticed that the Pitch III (or is it II? whatever the new pitch plug in for 11.1 is) is a huge cpu hog, I suddenly spiked like crazy and with the process of elimination that ended up being the culprit.
just to add to this thread...

[justus1900]

Originally Posted by wesm

Found the problem: Avid's own MasterMeter plugin.

I wrote about this the day PT 11.1 came out and I was ignored. http://duc.avid.com/showthread.php?t=348698

[wesm]

This is quite easy to reproduce:

Open a blank session.
Insert one stereo master fader track.
Insert MasterMeter on the master fader track.
Result: CPU usage reported by pro tools peaking at 100%.

Mac Pro 3,1
2x quadcore 2.8 GHz
22 G ram

Dear Avid Tech Support:
TL/DR;

Here's a thread dump from Activity Monitor:
Sampling process 9202 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Pro Tools (pid 9202) every 1 millisecond
Process: Pro Tools [9202]
Path: /Applications/Pro Tools.app/Contents/MacOS/Pro Tools
Load Address: 0x1075bf000
Identifier: com.avid.ProTools
Version: 11.1.1.195 (11.1.1d195)
Code Type: X86-64 (Native)
Parent Process: launchd [412]

Date/Time: 2014-01-07 08:55:33.671 -0800
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 7

Call graph:
(lots & lots of threads with MasterMeter:
! : | + 1 ??? (in MasterMeter) load address 0x138cc8000 + 0x3a696 [0x138d02696]
+ ! : | + ! : | + ! : | + ! : | 1 ??? (in MasterMeter) load address 0x138cc8000 + 0x691d9 [0x138d311d9]
+ ! : | + ! : | + ! : | + ! : | 1 ??? (in

etc.

[hd-native]

same here ....

can´t believe it is always the same since upgrading from 8-9-10-11-

and for a "HD-system" it´s just a shame

let´s wait for HD11.2 lol

[Darryl Ramm]

Same here as in it is with Master Meter -- or other plugins as well??

If it is only master meter I would try pulling it out of the AAX folder and try replacing it with the AAX file from the previous release. Hopefully PT 11 is not so smart to then try to replace this.