Pro Tools 10.3 9171 and 9172 Errors

[MGohil]

According to the doc on the Avid site, it's qualified through 10.8.x which is why I upgraded.

Restoring the system to the old state is not an acceptable option as I lose a lot of other updates that went along with that.

Is there anything else that can be done.

BTW I tried changing # of processors to 14 and that did not help.

I also tried changing the # of processors to 7 and that did not help either.

I'm noticing that while the System Usage shows CPU Native averaging around 10-14%, there are frequent peaks up to 50% - this is on a stereo track.

[RamblerSound]

I couldn't find a magic setting. I felt like I tried so many combinations and had turned most of the OS off. Nothing made a difference for me except rolling the OS back.

I'm in an interesting position because I work at a post studio that has built three new systems as well. The only real difference between the machines at my work and the one I own are the OS. If I could go back to a 10.7 OS I would but I think it's not possible for me.

I did about three hours of mixing yesterday on my rig. Its running good but not perfect. At one point I ended up getting a slew of DAE errors (4 in a row). I think it was a 9041 error but the wording is the same. I had to reboot PT and it cleared up. This is bothersome but at least it's not a session ending situation.

I forgot to add this in my first post because I was in a hurry. My rig is a 2012 Mac Pro 4 core 3.2 Westmire machine with 16 gigs of ram. I have installed the Waves Gold Bundle but no other plugs. I'm back to OS 10.8.1 and PT 10.2. I have the Avid 16 analog HD IO.

Thanks and good luck,

Scott

[Tops3b]

Ok I have some good news people. After trying a myriad of combinations I have stumbled upon a solution that was posted in another thread : http://duc.avid.com/showthread.php?t=328644

Basically after booting my mac into safe mode and restarting I have only had one error the whole day and thats when I had lots of tracks and way too many plug ins going on. I certainly hope this works for all you guys out there with a similar problem. Here is a link to Apples help page about booting into safe mode.

http://support.apple.com/kb/PH11212?viewlocale=en_US

Good luck everyone!

Cheers

Richard

[acstctws]

Originally Posted by MGohil

According to the doc on the Avid site, it's qualified through 10.8.x which is why I upgraded.

Restoring the system to the old state is not an acceptable option as I lose a lot of other updates that went along with that.

Is there anything else that can be done.

BTW I tried changing # of processors to 14 and that did not help.

I also tried changing the # of processors to 7 and that did not help either.

I'm noticing that while the System Usage shows CPU Native averaging around 10-14%, there are frequent peaks up to 50% - this is on a stereo track.

I updated to 10.8.2 and had tons of problems. Luckily, however, it's easy to revert to 10.8 without losing any of your files or settings. Just restart and hold Command+R while the system is booting. It will take you to a dialogue that (among a few other options) will allow you to reinstall ML without have to wipe your drive.

Worked like a charm for me, and while I'm still having some issues here and there, my system is usable. I think at this point it's 3rd party plugins that are giving me trouble, something I'm in the process of hashing out.

[MGohil]

Originally Posted by Tops3b

Ok I have some good news people. After trying a myriad of combinations I have stumbled upon a solution that was posted in another thread : http://duc.avid.com/showthread.php?t=328644

Basically after booting my mac into safe mode and restarting I have only had one error the whole day and thats when I had lots of tracks and way too many plug ins going on. I certainly hope this works for all you guys out there with a similar problem. Here is a link to Apples help page about booting into safe mode.

http://support.apple.com/kb/PH11212?viewlocale=en_US

Good luck everyone!

Cheers

Richard

Richard - thanks so much. I tried this (restart in safe mode, followed by restart in normal mode), and everything worked much better. My CPU usage has gone down drastically, and I don't get any errors anymore as long as I'm not using Ableton Live*.

I did some further research and found out that restarting in safe mode deletes the font cache, and also deletes a system cache having to do with display.




*The asterisk is that this applies to the sessions that were giving me trouble in the past. Now I'm now only getting that error when I'm running Ableton Live with ProTools in Rewire mode. I'm not sure if this is new or related to the other one. But other than this error, it's worked really well for me, and I did a ton of sessions this week so far on this without Ableton Live, and those without Ableton did not have a single crash.

[jgehring]

I too was experiencing these errors as they got worse & worse to the point of un-usability. This is on a system that when first set up (and then even recently with OSX10.7.3 & PTHD 10.2) could do fairly heavy tracking & mix sessions at 256 buffer size all day. It had excellent, "snappy" system response. Eventually even completely empty sessions would only play back at 1024 & yesterday it couldn't even play anything back at 2048 without popping these errors up. I also noticed that enabling Low Latency Monitoring would completely freeze the computer - it had to be powered off & restarted. So, with clients waiting I did the following:

1. Verified all settings from the system optimization guide, at which time I noticed:
-my system & recording drives had never been exempted from spotlight
-Firewire networking was never shut off. I shut that off as well as both ethernet ports (my controller is USB), but left the wireless on since I use that
-my Pace drivers were not the newest
-I don't think I had ever trashed Digi databases/trashed prefs since setting the machine up, so I did that

2. Restarted the machine into Safe Mode

3. Restarted it again back into "Normal" mode

The first time I started up Pro Tools & loaded a session it was still flaky & couldn't see my second 192. I closed Pro Tools, cycle powered the unrecognized 192, and then started Pro Tools again. THIS TIME everything was (and has remained) perfect - no more errors, snappy performance, & 256 buffer setting is no problem at all. I haven't tried the lower settings but they might be fine too. Basically all of the trouble-free original performance has been restored & the system performed without error for the rest of the day.

I can't be sure what did it, but something in that list fixed my problem. Hopefully this will help some of you that are still having these problems.

Additionally, I had also tried these other steps prior to yesterday with no avail:
-removed Soundtoys plugs
-repaired permissions
-reset system SMC
-updated OSX to 10.7.4 (from 10.7.3)

Good luck
John

[hotsizzlemusic]

knock on wood, but the newest update seems to have fixed these errors for me. Not one in the last 2 days.

PT10HD native 10.3.2
OSX 10.8.0
mac pro 8 core 2.4ghz
32gig ram
running video/blackmagic intensity and ve pro 5 with massive amounts of VIs

running really smoothly and barely breaking a sweat at low buffer settings.

[wdjudd]

If I have somehow missed a thread that covers this issue on OS 10.6.8, please me know.

OS 10.6.8
MacPro1,1ual-Core Intel Xeon: 2.66 GHz; 10 GB RAM
ProTools 10.3.6

Some sessions that worked fine in older PT versions (9.x-10.2.x) seem to be too taxing on the CPU, and I get several different -9xxx errors. Even if I create a new session with two stereo tracks and a stereo master track, I still get these errors if I try to record at 256 buffer size. Most new sessions will run at 1024 but you can't record at that size.

Is it just me or does this whole problem seemed to have appeared with PT10? Not trying to blame PT 10 but wondering if this problem will even go away with a new computer at current OS versions?

What I've tried:
clean driver installs
clean PT 10.3.6 install
Reinstall OS 10.6.8
Repair disk
Repair permissions
OnyX to remove all cache, etc.

[Trak]

Below is part of an earlier post. I wasn't sure if it was the OS or the PT version. Its looking to me like you don't want 10.3.6 to be your workhorse.

"On a new drive I installed ML and the combo ML 10.8.3 updater. I did the proper procedures and turned off all the ML extras. I installed PTHD 10.3.6, PSP Springbox, and three fabfilter plugs. I booted up and got rolling on a project with eight tracks of B3 @ 96kHz with the Avid 1 band EQ on each track and Springbox (which sounds awesome!) on an Aux. After a few setup changes I got rolling with a 128 buffer, which I usually track with.

Much to my surprise the -9172 error soon popped up. It happened a few times so I upped to 256 and still got the error. It was my first checkout of Springbox, so I replaced it with Avid's spring emu and still had issues with the lower buffer settings.

I rebooted to my 10.6.8/10.3.5 SSD and opened the same session and it ran flawlessly at 128 with and w/o Springbox.

For now, 10.3.6 and ML 10.8.3 will only be a transfer station to 11 and
I'll stick with 10.6.8/10.3.5 for work. I'll also do some more testing with 10.3.6 and ML 10.8.3."

Update: I rechecked this again adding one of the Avid compressors to the eight tracks with the Avid EQ. 10.3.6/ML10.8.3 stopped with a -9172 almost immediately at 128. 10.3.5/SL10.6.8 played it flawlessly, I couldn't get it to screw up.

I recommend that you try PT 10.3.5/OS10.6.8 and see if you still have issues.

[MGohil]

I'm still getting errors on ProTools 11, but not nearly as often.