AAE 9173 Pro Tools ran out of CPU power

[Shifted Music]

Originally Posted by Kinh

The reason I went for AIR plugins is because they're made for Pro tools!

Mee tooo initially..

BUT they are broken too... in some way... mainly the ones I mentioned and to a lesser or more degree, structure seems the most stable of the bunch.

This plug ins cause me havoc for a couple months with my set up.

IN the end I was told AVID reproduced the problem and have it logged. Not exactly what the problem is but thats what I was told...

Try setting up the PT aggregate audio driver (as that made the threshold where the AAE errors would happen would be raised.) also NO wireless.

And also try the plug in process that has been recommended to see exactly what it is causing your issue.

If you are actually having the same issue as me then the audio driver and wireless things helped... and NOT saving during playback also is the main link to making the error crash my system...

But doing the plug in testing might also reveal another variable that potentially is adding to the problem...

[Kinh]

Well its not an AIR plugin issue. Its happened with Komplete plugins.
http://www.gearslutz.com/board/pro-t...l#post10240947

[Darryl Ramm]

Have you verified that removing the latest/up to date NI Komplete plugins from your Pro Tools 11.2 system fixes your Pro Tools CPU errors?

[musicman691]

Originally Posted by Kinh

Well its not an AIR plugin issue. Its happened with Komplete plugins.
http://www.gearslutz.com/board/pro-t...l#post10240947

Do you have any Arturia plugins? Their MiniMoog emulation sometimes kicks up a 9173 error even on small sessions in any version of PT11.

[CygnusX-1Bk2]

I was getting this error bouncing a mix (real time) last night (-9173) despite playing back properly with no issues and a CPU reading of less than 50%. Had to close the session and reopen to resolve to bounce. The error would return the longer the session was open. Plugs include AutoAlign, Waves, AltiVerb Little Primal Tap, MH channel and K Meter.

Personally I am suspicious of dynamic processing because of where the error pops up on this particular song. If the System Usage window didn't freeze during real time bounce I could tell more.

[Kinh]

Have you verified that removing the latest/up to date NI Komplete plugins from your Pro Tools 11.2 system fixes your Pro Tools CPU errors?

Komplete plugins crashed on someone else's system, not mine.

The point I was making is it crashes (and judging by these recent comments) on many different plugin manufactures, not just AIR...
Komplete, AIR Transfuser, Artura, Waves, sound radix.

So obviously it has little to do with them and more to do with the 11.2.

[Darryl Ramm]

Originally Posted by Kinh

Komplete plugins crashed on someone else's system, not mine.

The point I was making is it crashes (and judging by these recent comments) on many different plugin manufactures, not just AIR...
Komplete, AIR Transfuser, Artura, Waves, sound radix.

So obviously it has little to do with them and more to do with the 11.2.

You have nowhere near enough information to cast aspersions on 11.2, this is how it has always been, many (or most?) problems are caused by plugins, accelerated by all the changes/new code involved in AAX-32 and AAX-64. There have been lots of instability from lots of plugin vendors going back to Pro Tools 10. So are you just sitting around or have you actually done any of the plugin removal tests yourself? The first stop with a suspected plugin problem is the plugin vendor, in most cases it is in their code, if its a problem in Pro Tools the vendor contacts Avid.

[Kinh]

You have nowhere near enough information to cast aspersions on 11.2, this is how it has always been, many (or most?)...

So how much more information do you recommend before casting aspersions?

The first stop with a suspected plugin problem is the plugin vendor, in most cases it is in their code, if its a problem in Pro Tools the vendor contacts Avid.

So what you're saying is its the plugin vender's problem if Pro tool's new version is incompatible with their product? hmm interesting.

[Darryl Ramm]

When the plugin vendor or Avid fesses up to who created a problem, if ever, then you know. i don't get the sense you are a software developer or that technical yet you seem more intent on focusing on casting blame on Pro Tools, or claiming you know its a Pro Tools 11.2 problem. You don't, nobody does, maybe it is, maybe it is not. Instead why don't you try to debug your problem and see if you can find a work around or track down a fix. I just do not understand the point of whining about stuff instead of trying to do something, anything, about it. How many days has this dragged on for? Extensive troubleshooting would have taken how many hours?

You started this tread with a simple wrong argument that you knew it was a bug in 11.2, even though you have classic symptoms of plugin problems, and you've not really listened to anybody's advice here. My mistake I assumed you were having problems and came here to get help.

[Kinh]

Instead why don't you try to debug your problem and see if you can find a work around or track down a fix.

And how do I 'debug' my problem? Ive already taken some axx plugins out of my folder. It seems all you've done is suggest the venders are at fault yet the evidence suggests the opposite. Maybe I should take all plugins out of my folder that way I wont get any errors..will that fix the problem?...No!

So how do I dubug? What are the steps, taking the plugins from the folder? OK great, then what?