-9173 Errors due to Native plugins

[DJ Hellfire]

Originally Posted by deanrichard

Avid is the right company to contact. It's 99.99% that the problem is theirs, not Izotope's. When a new version of the software breaks plugins that formerly worked it is ludicrous to blame the plugin company, particularly when a whole slew of other plugins break at the same time.

In this case I don't know if Ozone 7 previously worked fine. I only purchased it just after updating to 12.7.1. And it only seems to be when using the one Limiter algorithm IRC III, which is extremely heavy on CPU. That one algorithm drives up the CPU meter by almost 25% alone and pushes the PDC over the limit if used on an aux mix buss. And when that algorithm is used, you can visually see the CPU meter spiking.

[treason]

Originally Posted by DJ Hellfire

...when using the one Limiter algorithm IRC III, which is extremely heavy on CPU ....

We recently split our "mastering functions" (using DMG Limitless & DMG Equilibrium as the primary processors - with auxiliaries of course) onto a physically separate CPU using VEP 6.

Huge benefits from doing this ... I state this to plant a seed should it work for you.

[Carl Lie]

One thing I find is that I don't get them with DSP plugs, just native. Makes me think they designed AAX for the card's DSP and tried to figure out a way to go native somewhat unsuccessfully.

C

[midnightrambler]

Have to add that I'm experiencing similar things here too. Mix sessions that shouldn't be much of a sweat throwing up periodic 9xxx errors, even though the CPU meters are way way down. Almost always within the first five minutes of booting up the session, and then it seems to settle down. I've also been using the Izo stuff recently and I'm pretty sure they were okay on 12.4. Depressing.

[Dot]

same thing here, since pro tools 12.5 there's a lot of 9173 errors and the worst out of them all is error 6. i narrowed some of them down to SPL plugins, Ozone 7 and some waves plugins (at least that's what it appears)

[DJ Hellfire]

Seems like my issue here was related to 12.7.1. Rolled back to 12.7 and the problem seems to have gone away.

[JFreak]

Guys, it's 100% clear that any plugin maker (whether Avid or 3rd party vendor) needs to be compatible with the AAX spec and TEST their plugins against EVERY version Avid's going to release. They do get beta builds before us, so if "a plugin breaks" it is totally plugin vendor's fault.

Avid didn't update their plugins since 12.1 until this ongoing 12.7 release. I wonder why?

Avid Support usually first tells you to move all 3rd party plugins to unused folder and test if the problem is resolved. I wonder why?

[Marsdy]

Originally Posted by JFreak

Guys, it's 100% clear that any plugin maker (whether Avid or 3rd party vendor) needs to be compatible with the AAX spec and TEST their plugins against EVERY version Avid's going to release. They do get beta builds before us, so if "a plugin breaks" it is totally plugin vendor's fault.

Avid didn't update their plugins since 12.1 until this ongoing 12.7 release. I wonder why?

Avid Support usually first tells you to move all 3rd party plugins to unused folder and test if the problem is resolved. I wonder why?

Absolute nonsense. These error messages have been passing through countless Pro Tools versions/various plug-ins/random plug-ins and Avid seems helpless to do anything about them.

There is code in Pro Tools that needs fixing like years ago.

And even if you were correct which you're not...ask yourself this. Why is Pro Tools so vulnerable to errant plug-ins? Surely a modern DAW should be FAR more bullet proof. One plug-in taking the WHOLE system down... Have you ever known any Apple app that requires prefs trashing so often? It is flat out ridiculous.

A note how the more staff Avid let go the worse it gets?

[JFreak]

FWIW, I asked plugin sandboxing when I was in the PT7-10 beta team. No dice.

[Marsdy]

Originally Posted by JFreak

FWIW, I asked plugin sandboxing when I was in the PT7-10 beta team. No dice.

Well Avid should have listened to you and done what most of its competition is now doing. As you say sandboxing AND just plain honest to goodness stability.