-9171 and -9172 errors with Pro Tools HD 10.3 on HDX

[MixerGuy]

Originally Posted by glasswing

Read my reply in the other thread about 9172 errors. I think I've figured it out! It's the Mac accumulating tweaker/consumer garbage. And it can be plugins too. I had it resolved till today and discovered Vienna Ensemble Pro can trigger it if Pro Tools is confused about which instance, or project, to talk to.
Read my thread about it. It's pretty much gone for me now!
Mountain Lion/HDX 12.2.1/2012 Mac Pro main machine
2008 Mac Pro Vienna Ensemble Pro satellite machine
I wish someone would create a cleaner for Mac OS to get rid of all the junk they put in for gamers, messaging, Internet, hair curling etc.
Get Onyx and clean your machine! I do it every week now and all is working like it's supposed to… unless a plugin gets gummy.
errr…. KNOCK ON WOOD!

bump to an old thread

suddenly getting - ProTools 9171 errors

after upgrading from 10.8.5 to 10.9.5 (HDX)

PT HD

sept 2016

yes i read this old info:

http://avid.force.com/pkb/articles/e...ve-errors-9071


and i'm sure that my work Mac Pro is clean. no junk on it

PT HD 10.3.10

mac os 10.9.5 (yes i know not officially approved, but i am told by a very smart person it should be fine)

was 10.8.5

just upgraded to 10.9.5

thoughts?

thanks

[DetroitT]

Trash all the usual, check drive and permission, try again.

Do you also use PT's 12.5.2 or other versions?

[MixerGuy]

Originally Posted by DetroitT

Trash all the usual, check drive and permission, try again.

Do you also use PT's 12.5.2 or other versions?

Trashed all the usual, no dice.

didnt check permissions tho.... where? how?

and i only use PT HD 10.3.10

thanks.

[Southsidemusic]

Computer specs and what model hard drives do you have? Ram etc

[krsongs]

I just experienced this problem today: Bouncing a single track (wav file) to MP3.

NO PLUG-INS running.

(PT 11.3/OSX 10.8.5 Mountain Lion/iMac/2.9 GHz Core i5)

Never had this problem until today.



Kiki

[centerstage]

Same boat. New system 12.6.1 9171 errors. A few avid plugs. $5000 card that doesn't work. 3 weeks of this crap. If a don't find a solution by the weeks ends, I'm returning the card and leaving this platform. Anyone else on board?
Tim

[YYR123]

Originally Posted by centerstage

$5000 card that doesn't work.

$2999 priced card

[SaschaP]

I'm bringing this thread back to share my recent experience with this issue and to hopefully to shed some light on a (sort of) fix that works for me ...

My current system:
Mac Pro 5,1 12 core
64GB ram
OSX 10.12.1
Pro Tools 12.7.0
HD Native PCIe w/ Avid Omni

I've been using this same HD Native PCIe / Avid Omni combination for several years across 3 different Mac Pro's and from PT version 9 up through my current 12.7 set up.

I have always had -9171 and -9172 "Audio processing could not complete due to conflicts with other CPU tasks or a potential clocking issue..." errors to some degree or another on all my HD Native systems. The CPU usage would never be more than 50%, sometimes as low as 20% with a low track and plug-in count and no matter what the errors would pop up from time to time.

Over the last two weeks I've switched my playback engine to the Mac Pro's built in Digital output and voilà! no more errors. Not one. I've been running 60+ track sessions with HEAVY plugin usage and a playback buffer of 64 with zero errors. The CPU usage generally sits around 25% unless I go nuts with plugins. The min I switch back to HD Native the same session will double in CPU usage and the errors start up unless I raise the playback buffer significantly.

I suppose my particular card my just be bad, but given the amount of posts on this issue I'm pretty convinced the errors are due to poor communication or a bad driver between PT and the HD Native card in general.

I highly recommend you give your computers internal audio output a try and see if the errors stop. It's not a real solution but might it be a workaround for some.

[DetroitT]

Bad Driver.
Needs multi-client layers to play with all (or compliance).
Firmware + Software.
(My Best guess today)

[Rectifried]

had the same native card + omni...the 16x16
same crap
errors with barely anything going... audio stopping
so
I finally sold that stuff
really UNgood
plus you need HD only to access that HW?
400 a year to have MORE errors than vanilla native
wow
what
are they
thinking