I'm running into alot of "bus error- main thread" (about 10 yesterday) where Media Composer bails completely. I can repeat it by playing a group clip and playing "in to out" multiple times and cycling through the takes. I've repaired the permissions, tried new user settings etc... I can also recreate the crash on another editors machine. 

MacPro - 2.8 Ghz"Harpertown" 8 core. 4 Gig ram, OS 10.5.6, Quicktime 7.6

the other editors machine is  MacPro 3.0 Ghz.... 1 4 Gig ram, OS 10.5.5, Quicktime 7.5

we are connecting to a unity.

Any ideas, or can other people repeat this bug?

Is the other editing machine crashing as well, or just yours?

Based on the 3.1.2 Readme, you're out of a supported configuration if you're up to 10.5.6 and QT 7.6.

Taken from ReadMe:

Macintosh® OS Support Leopard® v10.5.5 The Leopard OS has been qualified with the Mojo, Mojo SDI, Adrenaline, Mojo DX and Nitris DX hardware.
QuickTime Support 7.5.5

I guess that's where I'd start.

~Hammer

yes, the other machine crashed also (it has the approved specs) and is fully maintained by the post facility and acsr's.  

I agree with Hammer, get another Drive, install 10.5.4 and QT 7.5.5 and see if you can repeat the "errors".

BTW. You can't call it a "Bug" since your running an Unsupported Machine.

--
Ted

oh yeah, both machines are standard def. Adrenalines. Our footage is 14:1 @ 23.976

Thanks, Scott

Hi Scott,

Being out of spec as far as you are can certainly cause these problems. However, the two version of MC you list, 2.8 and 3.0, were prone to these bus errors. Updating your Avid software to 3.1.2 could solve some of these crashes for you and will also bring you closer into bundle with your OS and QT.

k...I'm an idiot, those were your Processors, not your software!

If you remove your drives from the desktop, do you still get the bus errors?

I'm aware that my machine is slightly out of "spec" but..I can also recreate these errors on the other machine (Avid MC 3.12, OS 10.5.5, QT 7.5) So.... 

Blkdog, If I remove my drives from the destop... I'll have no media to play... Are you suggesting, try to recreate the problem with oflline media?

Yup. If yoiu don't get errors, then you know the problem is somewhere in the drive chain. At that point we can start by troubleshooting the MediaFiles folders.

Blkdog. I've take the drives offline (as you suggested) and yes, I was able to recreate the crash.

hmmm....... I recreated it by:

marking about a 2 second portion of a Group clip-which has 3 cameras in it. 

playing that group multiple times in a row

and intermitantly cycling through to the other group clips.

I can recreate it on 2 different machines, I was wondering if anyone else could also?

Thanks,

Is that a brand-new group, or one that you just made? 

Can you create a brand new group and recreate the crash?

~Hammer

Hammer, yes I made a new group and recreated it.  The work around that I'm using now is just to move slower...stopping the playback of in to out before I toggle the group to the next take etc...

It sounds similar to a situation I've been seeing much more regularly with the release of version 3. 

Perhaps try turning your playlength on and running that way (playlength= 1 or 2 minutes).  The play button should turn white while playlength is enabled. See if this makes any difference for you.

The situation that I've been seeing is grouped clips in version 3 seem to have issues playing when there's a lot of data being pushed.  I have seen this on Leopard Mac's connected to 4.1.6, 8400's/8600's connected to 5.1, and 8400's/8600's connected to 4.1.6.  The only similarity so far has been version 3.  The PC's have stayed at 3.0 and the mac's have been up multiple versions up to 3.1.2.

The "error" is not a kernal panic or bus error, it's just that audio drops out after playing the group for about 5 seconds.  If you stop playback and restart it, the audio is back again for about 5 seconds.  If you mark in-out for a small section of the group and play in to out, everything plays fine.   If you set playlength to a few minutes or less, it plays fine.  If you subclip the group down so it's smaller, everything plays fine.  If you match back to the original master clip, everything's fine.  It just seems to have trouble when it's prereading many cameras for long periods of time.  I've seen it happen with groups that are 3+ hours in size, and then subclipping them down to 45 mninutes or so has fixed it.

I realize that it's not the same result, but perhaps the cause of "a problem" is related. 

Has anyone else seen this situation with version 3?

~Hammer

Tried "playlength" option... it doesn't fix it... hmmm. 

I tried turning playlength on, to no avail.. still crashes ....hmmm

I've tried adjusting  playlengths and still have not fixed the issue.  

I've also gotten a couple of "exception: ASpringBuffer TIMEOUT" errors. Could these be related? maybe pointing toward something else?