Pro Tools 11.3.1 Error Codes -9171 -9172 -9173 -9129 -9093

[priyatsomo]

Hello !

I am getting error codes -9171 -9172 -9173 -9129 -9093

I am running
Mac Pro
Early 2009
Processor 2.93 GHz Quad-Core Intel Xeon
Memory 16GB 1066 MHz DDR3 ECC
Graphics NVIDIA Ge Force GT 120 512 MB
Software OS X 10.9.5 (13F34)
Pro Tools HD 11.3.1
PCI HD Native Card (in slot 2)
Avid HD IO 16/16 Analog


I open a session and it idles around 20% then I play all the way through and the CPU shoots up to 100% and I get AAE 9173. The CPU then idles around 100%. Some times it falls back down to 20% but then when I press play, or arm a track to record it shoots back up and I get error codes.

The H/W Buffer Size is set to 1024 (but Ive tried everything) and the cashe is set to 1GB (also have tried everything).
I have tried doing a clean install of pro tools.
I have tried getting rid of all the plugins (this makes the CPU go down but then when I add back even just the Avid plugins that come with pro tools the CPU shoots back up)
I have tried getting rid of all elastic audio.
I have taken the computer into the apple store and they throughly checked out the hardware and OS and found nothing wrong.

Please!? Does anyone have any ideas of what I could try? I am pretty desperate.

Thank you!!
Best,
Priya
[email protected]

[ArKay99]

Not trying to be a smartass, but check the stickies at the top. Lots of us (all?) with your system (or very similar) are having those same issues... In the PT 11 | HD thread there is a hack that helped a few.

I have logged a bug report at Ideascale...maybe some votes would get it bumped up in prioirity.

[priyatsomo]

Thanks for responding!!!

what is the link to ideascale? I only found bug reports for during bounce (error code AAE -9173), and that was supposedly fixed in 11.3.1

also is this the hack you were talking about? https://www.dropbox.com/s/g3f839lxsc...audio.txt?dl=0

The avid customer service people and I have started to get to know each other pretty well, hopefully the developers will figure out something soon because currently its basically impossible to work.


....

ohhh I just found this http://protools.ideascale.com/a/dtd/153575-3779
was that you?

thank you!!

[midnightrambler]

It's sansamp that's doing exactly this on mine. Dither plug before the sansamps seem to sort it out....

[ArKay99]

Originally Posted by midnightrambler

It's sansamp that's doing exactly this on mine. Dither plug before the sansamps seem to sort it out....

Not on mine, unless you have to take it out of the folder... but I WILL try that as a workaround.

[ArKay99]

Originally Posted by priyatsomo

Thanks for responding!!!

what is the link to ideascale? I only found bug reports for during bounce (error code AAE -9173), and that was supposedly fixed in 11.3.1

also is this the hack you were talking about? https://www.dropbox.com/s/g3f839lxsc...audio.txt?dl=0

The avid customer service people and I have started to get to know each other pretty well, hopefully the developers will figure out something soon because currently its basically impossible to work.


....

ohhh I just found this http://protools.ideascale.com/a/dtd/153575-3779
was that you?

thank you!!

Yes, that was me. We need to get a lot of votes on that bug to elevate it's visibility. Also, yes, that was the hack. Since you have a 'dialog' with support, you have mine and many others, I assume, rooting for you.

[priyatsomo]

Originally Posted by midnightrambler

It's sansamp that's doing exactly this on mine. Dither plug before the sansamps seem to sort it out....

Yesterday I spent 2 more hours on the phone with avid and we figured out that this also solved my problem (at least currently). If your not using PSA1 in a session that is having CPU spikes try putting dither before other avid plugins that you are using. It seems like this was an old bug that they fixed in PT 9 or 10 and now it is starting to come up again in 11.

Also, there is no point in trying to take PSA1 out of the plug-ins folder because it is an Avid plug-in and Pro Tools will just regenerate it when it opens (I think).

Both Steve (the Avid person I was talking to) and I realize this is not a permanent fix however it made my sessions at least workable, which for me is a huge step. He took a lot of logs from my computer; when it was having the CPU spike, with the fix, and also took the session files that I was seeing the bug in, and submitted them to the developers so hopefully there will be a solution that has more finesse in the future.

Please let me know if you hear anything new with this issue, and if this works for you.

Good luck!!

[treason]

Originally Posted by priyatsomo

Yesterday I spent 2 more hours on the phone with avid and we figured out that this also solved my problem (at least currently). If your not using PSA1 in a session that is having CPU spikes try putting dither before other avid plugins that you are using. It seems like this was an old bug that they fixed in PT 9 or 10 and now it is starting to come up again in 11.

Also, there is no point in trying to take PSA1 out of the plug-ins folder because it is an Avid plug-in and Pro Tools will just regenerate it when it opens (I think).

Both Steve (the Avid person I was talking to) and I realize this is not a permanent fix however it made my sessions at least workable, which for me is a huge step. He took a lot of logs from my computer; when it was having the CPU spike, with the fix, and also took the session files that I was seeing the bug in, and submitted them to the developers so hopefully there will be a solution that has more finesse in the future.

Please let me know if you hear anything new with this issue, and if this works for you.

Good luck!!

You can remove Avid Core Plug-ins from the PT 11.x such that they do not regenerate. I use the Mac App "Find Any File" to search for MasterMeter, SansAmp PSA-1, etc (I have removed 7 of the Core Plugs) and (re)move those unwanted Core Plugs to an "x-Unused" folder within the Pro Tools 11 app.

You can find the Core PlugIns at:

Pro Tools.app:Contents:PlugIns:Core Plug-Ins

This must be done on each instance of Pro Tools 11, which means that when you update Pro Tools, you must re-perform this operation on the new version. If you do this before you ever run the new version of PT, you will not have those Core PlugIns installed in your PlugIns folder.

I have also replaced all instances of SansAmp PSA1 with SofTube's Saturation Knob plug.

[ArKay99]

Originally Posted by priyatsomo

Yesterday I spent 2 more hours on the phone with avid and we figured out that this also solved my problem (at least currently). If your not using PSA1 in a session that is having CPU spikes try putting dither before other avid plugins that you are using. It seems like this was an old bug that they fixed in PT 9 or 10 and now it is starting to come up again in 11.

Also, there is no point in trying to take PSA1 out of the plug-ins folder because it is an Avid plug-in and Pro Tools will just regenerate it when it opens (I think).

Both Steve (the Avid person I was talking to) and I realize this is not a permanent fix however it made my sessions at least workable, which for me is a huge step. He took a lot of logs from my computer; when it was having the CPU spike, with the fix, and also took the session files that I was seeing the bug in, and submitted them to the developers so hopefully there will be a solution that has more finesse in the future.

Please let me know if you hear anything new with this issue, and if this works for you.

Good luck!!

I wonder what process putting dither before a plug would do to alleviate the cpu spike...unless for some reson those plugs are still running on a bit depth other than 64 bit... just a guess, since it was fixed in 9...

If this is indeed the case as a workaround, does this occur in the native version of the plugs? i.e. if I convert them to non dsp will they still fail?

The thing that sux for me regarding this is, I usually use several if not 10's of those core plugs on any given session...to have to install dither on just every track I have a core plug on would be pretty expensive on the dsp engine...but if it's a viable work around, you have my devotion!

[Bill Denton]

Originally Posted by ArKay99

I wonder what process putting dither before a plug would do to alleviate the cpu spike...unless for some reson those plugs are still running on a bit depth other than 64 bit... just a guess, since it was fixed in 9...

If this is indeed the case as a workaround, does this occur in the native version of the plugs? i.e. if I convert them to non dsp will they still fail?

The thing that sux for me regarding this is, I usually use several if not 10's of those core plugs on any given session...to have to install dither on just every track I have a core plug on would be pretty expensive on the dsp engine...but if it's a viable work around, you have my devotion!

It's possible it's not even the "dither" process...it could well be some of the internal routing of the plugin that solves the problem.

There is a lot of possible weirdness that can occur in strange places!