AAE -9173 Issues

[Park Seward]

I noticed something similar when I upgraded to 11.2.1. PT11 would not load. I removed PT10 app and everything worked fine.

There are still remnants of PT10 in the system so I guess the best rout is to uninstall all PT stuff and re-load 12.2.1

Originally Posted by deadshot

If you ran pt10 and upgraded to OS x on your Mac, they do not play well together. Pt10 needs to be removed in every way. This can cause all kinds of issues. this seemed to be the real fix, I had some residuals left over and not sure why they didn't get removed. Also just placing them in your trash does not kill them, you need to empty them out.

[CygnusX-1Bk2]

So the fix is a defeated purpose of having co-installs of 10 and 11? WTF?!?!?

[mesaone]

Originally Posted by CygnusX-1Bk2

So the fix is a defeated purpose of having co-installs of 10 and 11? WTF?!?!?

Well, co-install is not supported on Mavericks. The consolation is that most plug-ins are now available in AAX 64 bit, so the transition from PT10 to PT11 is mostly seamless for many people. There are a few stragglers in the plug-in world, but such is life.

Deadshot didn't specify whether he removed PT10 prior to upgrading to Mavericks, but if he did not then that might explain the issues he experienced... Although to be honest, his issue was exceptionally strange and I can completely empathize with his frustration.

[CygnusX-1Bk2]

But it is supported on 10.8.5 where the problem originated for me. And the uninstaller for 10 doesn't work in Mavericks. This is a serious cluster [bleep][bleep][bleep][bleep] on Avid's part.

[CygnusX-1Bk2]

Manually uninstalled 10 from my Mavericks drive as directed by the Avid knowledgebase doc. Still -9173 during bounce.

[H.Slin]

I signed up for DUC specifically to post on this issue. I have all these same exact problems in both Pro Tools 10 and 11. I have tried every suggested "fix", and put up with reading all the ridiculous posts from the people who think they know everything about what me and others with the same problem are doing "wrong". My system is more than tough enough to handle the sessions it is crashing on. I've removed the plugins from their folder, replaced them, unplugged all peripherals, tried aggregates, built-in audio and interfaces, uninstalled, re-installed both os and PT, trashed the preferences…..not to mention the likelihood that all my neighbors are now terrified of me from the rampant screaming and swearing incessantly pouring from my home. There seems to be absolutely no answer to fix the problem. It seems clearly to be a bug, and the program is close to unusable. Bounce to disk in real time? forget it. So the question is very quickly becoming not "when will this problem be addressed", but what other DAW should I transition to. I really prefer Pro Tools and have been working with it since version 5, but man, this is not looking good.

[mesaone]

Originally Posted by H.Slin

I have all these same exact problems in both Pro Tools 10 and 11. I have tried every suggested "fix", and put up with reading all the ridiculous posts from the people who think they know everything about what me and others with the same problem are doing "wrong".

We're just trying to help. Sorry you had to read some forum posts that didn't help fix your problem. Since this error is not present for everyone, not even present for everyone on similar systems, then it's always possible that it is user error or third-party incompatibility.

On the other hand, you can't expect people to intuit your situation if you don't post anything specific. That's the reality of troubleshooting.

[CygnusX-1Bk2]

Rolling back to 11.1.3 solved the problem for me. We'll see what the next "fix" breaks/resolves. Hopefully this is in the mix.

[H.Slin]

Don't get me wrong, I greatly appreciate the people genuinely trying to help, which is why I spend hours on here reading and trying out the suggestions. The reason I never joined before is because I can usually find the answer to my problem fairly quick, so there has really been no need for me to ask questions. I've read enough on this subject now, to where it seems (to me) pretty clear that it's a bug, and not user error, which is why I did not post any specifics about my system. So, I guess I was just trying to sympathize with others having this same problem, as well as adding my voice to the need of it being resolved. You do have to admit that it is frustrating to come across a comment rudely suggesting to someone that all you need to do is increase the playback buffer or the like (not in this thread, but countless others both here and on other forums). I'd just like to see this problem resolved so I can get back to work, and if I come across anything that helps I will gladly share that information.

[john1192]

Cygnus .. are you still using 11.1.3 ??