application interdependence bug

[c-post]

OS 10.3.9 and PT 6.4.1

I can't boot Final Cut or Itunes unless protools has launched.

And protools is crashing a lot unless I boot Final Cut and leave it idle when protools is running. Then protools seems stable and runs happy.

Has anyone else experienced this kind of "application interdependence?"

I tried dumping all preferences and database folders for PT, but it didn't help. The application PT 6.4.1 just shut down (not loss of contact with hardware -- it just disappears from the screen and it says "send a bug report to Apple".)

These kinds of problems come and go and it's usually not anything I can put my finger on. My protools session which I am printmastering (not doing anything fancy!) just shut down about every 5-20 minutes or so. What startled me is I booted FCP and then it ran fine without crashing. This is bizarre. Any insights? And has anyone noticed there is a firebrand anti-war candidate in the Republican camp? The media sure isn't aware of it. Yeah, THAT guy, right over there. Shhhh! Don't tell anyone!

best regards

c-post

[Craig F]

have you tried a permissions repair and the other things from trouble shooting sticky?

[c-post]

Yes, I did repair permissions, thanks!

c-post

[Craig F]

have you tried anything like OnyX or Mac Janitor?

[c-post]

No I sure haven't. Can you tell me anything about them, Craig?

sincere regards

c-post

[Craig F]

http://versiontracker.com/dyn/moreinfo/macosx/20070

Both runs other repair scripts, both are freeware, I linked OnyX because it seems to be keep to better to me, it will also show you the hidden .ds files if you so wish

[Druphus]

This could be a conflict between your other apps and the digi core audio manager. With Pro Tools closed try looking in your system prefs under sound/output and if thee system is set to use Digi Core Audio try switching it to internal speaker and then see if your other apps open up ok. If this works but you need to use the Digi hardware then try downloading and installing the latest version of the core audio manager plug-in to see if this cures the problem.