-9171 and -9172 errors Pro Tools 11 | HD

[brianjanthony]

I'm a dope. didn't re-install it on this studio machine I'm on. I just dragged the file in place and the problem stopped when sys noises occur.

I don't think Mavericks/ML will matter much. See if (before installing) you end up with something in Console that reads like the last line of my pic here. If yours DOES display that stack shots message, try the pref file. See if it helps day to day.

For me I didn't need to test much. Sys went from unuseable to useable and it was noticeable immediately. https://www.dropbox.com/s/h5ycc21tmx...%20PM.png?dl=0

[brianjanthony]

Sorry for ALL of this. Still not reponding on my machine. I will post updated stuff in an hour or so.

[brianjanthony]

https://www.dropbox.com/sh/vn2j0i292...LBFJkzYoa?dl=0

That is a link to the stuff (webpage, Terminal copy/paste, etc) that I used to disable the part of at least 10.8.5 that was throwing these errors at me.

For some reason going thru Terminal worked. Just dragging the file and rebooting did not. I dragged the file in, then used Terminal to update and I've watched the log like a hawk now. no error messages and PT has behaved just fine.

[Skwaidu]

Originally Posted by brianjanthony

https://www.dropbox.com/sh/vn2j0i292...LBFJkzYoa?dl=0

That is a link to the stuff (webpage, Terminal copy/paste, etc) that I used to disable the part of at least 10.8.5 that was throwing these errors at me.

For some reason going thru Terminal worked. Just dragging the file and rebooting did not. I dragged the file in, then used Terminal to update and I've watched the log like a hawk now. no error messages and PT has behaved just fine.

Ok, thanks, I'll check it out when I have time.

[ArKay99]

Originally Posted by brianjanthony

https://www.dropbox.com/sh/vn2j0i292...LBFJkzYoa?dl=0

That is a link to the stuff (webpage, Terminal copy/paste, etc) that I used to disable the part of at least 10.8.5 that was throwing these errors at me.

For some reason going thru Terminal worked. Just dragging the file and rebooting did not. I dragged the file in, then used Terminal to update and I've watched the log like a hawk now. no error messages and PT has behaved just fine.

It could have been a permissions issue just using terminal. I made the file you provided using nano with root user access and I've been running fine with the checkbox to flag all errors in the playback engine AND a 256 byte buffer for most of the day.

One point of note, my system seems to be running about 4-5% less busy now... must be some sort of voodoo magic! I will report back here if I see the errors or not.

[brianjanthony]

FWIW I abuse all sessions and I use 128 and its been ok.

[radkins]

I have noticed that this problem usually only happens when I am using both monitors in my session. For instance tonight I was doing elastic audio and had my edit window drug across both screens and could not even press play without getting the error. If I resized my window to just one window the errors went away all together. I was able to repeat this at any time. Anyone have this issue? I saw someone on Gearsluts who solved this problem on multiple machines by upgrading the video card from the stock GeForce to a much faster ATI 5770. Something about the slow video card causing PCI spikes. Mine just arrived today so I will give it a shot.

[brianjanthony]

Wohhhh. I have two monitor. But I have the 5770 ati (not in front of it hope that's right). Didn't know there was a better one for a Mac Pro cheese grater?

[gearhead2010]

Originally Posted by ArKay99

My personal opinion of the lack of acknowledgement of it is I believe AVID did not design the HDX card and to go back to the designers and have them find the issue and fix it would cost them a lot of money...which they don't have or wish to commit to at this time.

This problem is also rampant with HDN cards.

[radkins]

Obviously Avid is clueless.

Initial troubleshooting steps:
Upgrade to Pro Tools 10.3.7 or higher and Mac OS X 10.8.4.

Further troubleshooting steps:
Mac OS 10.8 Mountain Lion can increase the errors
Consider using an earlier Mac OS such as 10.7.4