Mbox 2 with PT10 = major problems.

[YouMeOh]

Can someone please help me? I'm starting to freak out. Here's the problem (partially described in this thread):

Recently bought a used iMac i7 27" from late 2009. Installed Pro Tools 10 to use with my Mbox 2. I am getting the error
"Problem detected with audio clock. Check that your clock source and sample rate are correct".

Some projects work for a while, then I get the error. On some projects, I can't start playback what so ever. All projects are 44.1Khz and I'm using the internal clock. Recently, the problem starting happening more and more. I am also getting messages saying

"Pro Tools is unable to reacquire the hardware because it is in use by another application. Please quite other applications and hit "OK" to retry. If the hardware cannot be acquired, please quit and relaunch Pro Tools. ".

This happens after I reboot the computer, no other softwares is running and I am not using my Mbox as the soundcard for the iMac (using the internal one).

I am also getting "Pro Tools hardware is either not installed or used by another program". This leads me to believe that there's something wrong with the drivers, but I have installed the latest ones. I am not iusing the Mbox with any other applications.

I have gotten similar problems at work (I work in the music software industry) but not nearly as much. At work I use the Mbox 2 Mini with a MacBook Pro.
I have tried all different USB ports but it doesn't make any difference. Is it time to get rid of the old Mbox 2 and get the 3rd generation or can it (and my money) be saved?

[YouMeOh]

Nobody? Or am I given the silent treatment because the answer is elsewhere? If so, please let me know.

[PD-John]

Only thing I can think of is trashing Pro Tools Preferences - that may fix it.

[YouMeOh]

Where do I find them?

[Dism]

http://duc.avid.com/showthread.php?t=300050

[paulrgmusic]

Hi

I have exactly the same problem except I'm on a mid 2011 iMac 27" 3.4 i7 12GB RAM and 10.7.3 Lion and an Mbox 2 Pro. I've trashed prefs and repaired permissions to no avail.

I have (I think) narrowed it down to the Mbox or its drivers. I ran PT10.0.1 today on the internal sound device (thus taking the Mbox 2 Pro out of the equation) and I ran session after session with no problem. I switched back to the Mbox and within a few minutes had the error.

If a session starts, it seems to be fine for as long as you are on the session. When you load a different session it often goes belly up.

Any other ideas?

Paul