Mbox 2 Pro + MacBook Pro 10.4.11 help - cpu spikes?

[Tubetone99]

After accidentally upgrading my OSX to 10.4.11 I can't any of my PT sessions to run it keeps giving me a -6068 error and also this message. I'm running a MacBook Pro Duo Core Intel with 10.4.11

Upon monitoring my system usage my cpu seems to be spiking and jittering.

I have re-installed PT 7.3
I have ran cs updates
I have repaired permissions on drives
I have opened new sessions with 1 track and still get the same errors.


Is there a known capability issue with 10.4.11?

Thanks

[DigiTechSupt]

Have you tried all the steps in the OS X Setup and General Troubleshooting thread yet?

[jturner]

Odd. I have been having a similar error as of this morning. Except I haven't updated anything (Automatic Software Update is turned off, and I have been on 10.4.11 for months). Also, my problem has been -6085 errors.

My system:
MacBook Pro 2.33 Intel Core 2 Duo
3 Gb RAM
Mbox 2 Pro
PT LE 7.3.1 cs6

Mbox connected via SIIG Fireire Express Card
LaCie ext FW 250GB 7200rpm drive connected to onboard FW800

This system has worked flawlessly since building it. In fact, it has been more stable than my HD rig! As of this morning I am having -6085 errors (H/W buffer underflow) on every session I open, as soon as I initiate playback. Most sessions are 10 to 15 tracks, 24bit/96k. All are sessions I have worked on before with this rig with great success.

I have:
Lowered H/W Buffer settings (as recommended by error message)
Trashed prefs
Repaired permissions
Zapped PRAM
Booted into Safe Boot
Changed FW ports for the drive
Reconnected SIIG card/Mbox
Verified disk on ext drive (via Disk Utility)

None of that helped.

I have not yet:
Re-installed PT
Created a new user account and worked from there
etc..

But I saw this post, and thought I would see if anyone had any suggestions before I start dismantling my rig.

Ideas?

Thanks,
Josh

[yellowjacket]

http://discussions.apple.com/thread....63824&tstart=0

3rd post down.

10.4.11 had an Airport update that was causing CPU spikes that affected many other apps, not just Pro Tools.