AAE -9173 Issues

[CygnusX-1Bk2]

Originally Posted by Torchlight

For the life of me I have no idea why Avid decided NOT to include an uninstaller with PT 11.

11.3 is the only 11 installer that has an uninstaller. It's the only one that doesn't drag and drop to install. -9173 errors are gone for me for real time bounce. However I am getting some weird Audio Suite behavior in 11.3.

[benwalker]

11.3 on Windows - playback is perfect (no spikes etc) but BTD reports -9173. Offline bounce is fine...

[gearhead2010]

I really, really wish AVID would fix these errors. It is beyond ridiculous at this point.

I laugh every time I get one of their emails touting their new S6 system, or other new hardware / software solutions.

Why would anyone buy it if they can't even get basic Pro Tools functionality to work?

It's clear what little resources they do have, is spent on misdirection.

[Wolfgang Eller]

Still random errors in BTD.

[Park Seward]

Originally Posted by nigelpry

Awaiting confirmation if 11.3 fixes 9173 errors during playback too …

Avid says 11/3 fixes 9173 errors...

"This issue is fixed in Pro Tools 11.3. Please see the following for more info:
Pro Tools 11.3 Info & Downloads
Real-time Bounce To Disk -9173 Bug Report"

[bashville]

Hi I just had to chase down a -9172(?) error I kept getting on one session only. The rest of the error message was similar to those described here (running out of CPU power), and also as described it was all happening in one core, kind of random like a sudden surge. That made me think it was happening in one particular track, because I've read that's the one limitation to the multi-core distribution, is that multiple heavy-load plugs all loaded to one track are still all processed in one core. Before the "surge" would begin, CPU was only at 15-25%.

Anyway I narrowed it down to a particular track--I was looking for a possible faulty plug, and the plug I was using in that track that wasn't being used on any others was SansAmp. However, if I disabled all the other plugs on the session except for SansAmp (running SansAmp only) it ran fine. Either way I farmed the task out to a different combination of distortion plug and amp sim and the problem went away (fingers crossed). This was after substituting a lot of other plugs that I thought might have been problematic.

I troubleshooted (troubleshot?) by loading the session with all the plugs disabled, then turning them on one-by-one and looping the session in playback until it got through a pass or two without failing.

So the weird part, in the end, was something about the combination of plugs on that track (high-pass filter, channel strip, SansAmp, delay, verb), and not one individual plug. Because it worked if I ran the SansAmp alone. It's just that I used the other plugs a lot in the rest of the tracks with no problem, and the SansAmp was the only difference. Then when I replaced it, the problem stopped. This is the only session out of maybe 15 I'm currently working on where I was having this problem.

[mesaone]

SansAmp core usage problems... Could this be related to denormalization, which people have successfully worked around by inserting a dither in the slot above SansAmp?

http://duc.avid.com/showthread.php?t=240318

[Park Seward]

It has been reported that you must remove the plugs completely from PT in order to troubleshoot. Just turning them off is not enough.

[bashville]

Originally Posted by Park Seward

It has been reported that you must remove the plugs completely from PT in order to troubleshoot. Just turning them off is not enough.

well honestly it seemed to work for me this time. I think I found the culprit. I wonder what the difference is between the plug being "inactive" and not being there at all?

[mesaone]

Pro tools pre-loads all the plugins at launch. Even if a plug isn't used, it's scanned. I don't know all the dirty details.