11.2.1 My Findings, -9173 error with BTD

[Southsidemusic]

As far as I interpret "clean unistall" is chosen in PT unistaller where you can chose between different unistall options, i would guess Clean unistall is the option talked about here

Best of Luck
Christopher

[treason]

Originally Posted by Southsidemusic

As far as I interpret "clean unistall" is chosen in PT unistaller where you can chose between different unistall options, i would guess Clean unistall is the option talked about here

Best of Luck
Christopher

Performed the PT 11 clean install as described here, and then added plugs in groups to determine the culprit(s).

I ended up leaving BlueCat's MB-7/Patchwork and all the Native Instruments plugs out (I run them in VEP anyways) resulting in about 15% more CPU headroom. These plugs now reside in the Plug-Ins (Unused) folder.

Since I was not using BlueCat in sessions anymore (switched over to AAX plugs or FabFilter Pro MB for any multi band work), this was an easy choice. Surprised that removal of the BlueCat plugs alone saved that much CPU usage on a session that does not even instantiate any of them.

As always ... YMMV.

[CinematicPrime]

Originally Posted by lucienpalmer

When you say 'clean install', did you reinstall the OS, or just Pro Tools? Plugins too?

I did a clean install of Everything!!!
1) Mac OSX 10.9.4. and then 2) Pro Tools 11.1.2 then 3) All Plugins

Now every plugins work just fine. (I also tried only reinstalling pro tools 11.1.2 or even 10.0.3 and deleted everything out the library folder but nothing worked.)
It took a whole day but a fresh install of OSX and PT fixed the issues (even if i don't know exactly why...)

I'm working now around a week with the reinstalled system and everything works with no issues after all !
So i figured out it's none of my plugins - it's pro tools!
So if you use NativeInstruments, Waves, McDSP, Antares Autotune etc. , RevoicePro/Vocalign, Bluecat.... It IS ProTools! Everything works here without any issues

[climber]

Was running 11.1.3 and generally all was fine. Updated to 11.2.1 and couldn't successfully BTD. Down-dated back to 11.1.3 and things are OK again. Thank goodness...

[ja_allen]

On the mac, OSX 10.9.3 - 4, that if you have VNC enabled, this will cause very serious spike problems. Seems Apple may have done something with screen sharing all the way up to 10.9.5 (Which is worse on screen sharing, frozen screens, etc...). This makes ProTools system info on CPU red. Was not an issue it seems in 11.1.3. I cant check as I am at 11.2.1.

I use VNC (Screen Sharing) when moving files and updates and what have you. Once I went into preferences and turned screen sharing and file sharing off, instant stability and was able to real-time bounce no issues.

[Ken Skoglund]

I got the -9173 error also, MacPro 5.1, HDX system, OS 10.8.5, PT 11.2.1. Always on BTD, and aslo sometimes on playback, (not very oftenon PB). Doing a mastering session now, only 2 stereotracks, 3 plugs and 1 insert for a tube compressor. Using 3% CPU. It goes away for a while after restart, so I managed to get my project done. Moving on to a MP Trashcan and 10.9.4 next week and new installs on everything so I will try to bounce in between plug installs to see whats going on.

[gives]

Originally Posted by JFreak

I haven't seen any issue with bounce (11.2.1).

The fix for me has been for now to close Protools completely and then re-launch Protools. then it seems to work. I have had intermittent issues here with it, but not always. Offline works no problem. Good news with the ADC!! G

[jryser]

This is a known and logged error with Avid. They are working on a fix.