Constant 9173 error's PT 12.6 *solved*

[DJ Hellfire]

Originally Posted by Franklyn

1. Is it my job to test every single plug in if it works 100% fine with this very sensible AAX engine? NO !!!
I payed so much money for the PT HD 10/11/12 Software and updates.
Avid, please do your job. I have 100s of Plug ins of renowned manufacturers.
Waves, Soundtoys, Slate, Sonnox, McDSP, Softube, UAD.
It takes hours to check every plug in. Thats no solution.Yes,

2. I can confirm that some plugs work better than others,
but these plug ins works much better in every other DAW. I thought some years ago we changed the plug in format from rtas to aax to get better compatibility with plug ins. But today many plug ins works 50 or 80% "fine". I think its a Pro Tools Problem. Such a "unclear" Problem exsisted in any other previous version of Pro Tools.
Please integrate a clear AAX Plug in verification in Pro Tools that show us if a plug in work correct or not.
these CPU peaks are so frustrating.
I have a lot of Sessions where i can not work on."9173 error" all the time.
But I have to finish a album.
Terrible !
Please, please, please help us !!!
Aaaaaavid Heeeeeelloooooo !!!

1. Actually, it kinda is your responsibility the check the plugins you install. Avid cannot test every plugin in the world and they don't require you to have 3rd party plugins to use Pro Tools. So if you choose to install plugins other than what Avid manufactures, it's your job to troubleshoot them and keep them up to date. Sure, Avid can test some of the more popular plugins, but ultimately it's the plugin manufacturers responsibility to make sure it works properly with Pro Tools before they release them. That's between you (the plugin user) and the plugin manufacturer.

2. Again, the fact that the same plugins work in another DAW does not mean it's Pro Tools' fault. Those DAW's use an entirely different plugin file/format. So it's possible there is just a problem with the AAX version of the plugin, not necessarily with Pro Tools.

I would say the first step for you would be to try to figure out which plugin is causing the problem. Then see if others are having the same problem with that plugin in Pro Tools. This will help more determine if it's the actual plugin or something in your system configuration.