[J K creative cow]

It has happened since the beginning.

I don’t think it’s Media100 software but rather the hardware connection with the G5, as I haven’t had any problems playing around with Media100/sw with the Magma chassis powered down.

When it crashes, it’s instant. Keyboard doesn’t work, force-quitting doesn’t work, …just a lonely mouse pointer with nothing left to click on. Wish there was a crash log of some kind in OS-X, then I could tell if it was indeed the p6000 or something else, such as memory.

[J K creative cow]

If it’s at all helpful in finding out what causes this:

I get a guaranteed lock-up when running a program for any significant amount of time, say 5 or 10 minutes, whether on the SW or the HW codec.

Normally when editing, we’re only dealing with seconds or frames, so the problem isn’t always there, until at last it’s time to sit back and watch something, then it rears its ugly head.

[J K creative cow]

I’ve had this problem too from the beginning. Sometimes my G5 crashes up to 5 times a day and, although not proven, I have strong suspicion that it’s the P6000 acting up in the Magma chassis or it’s related to M100 in some way.

I tried the Activity Monitor approach -but when it crashes, it’s completely gone, so I can’t always see what Activity Monitor was reporting. Does anyone know if OS X makes a crash report somewhere which can be viewed on re-boot to see what happened? Thanks.

M100i v8.2.2
G5 dual 1.8
1GB ram
OS X 10.3.3

[J K creative cow]

With very kind support from velocite (thanks John!) we were able to verify that OMF export does in fact work between Media100i 8.2.2 and current versions of ProTools LE on OS X. (Media 100 didn’t recommend this) Pan info does not translate but clip and audio level info does. No idea on crossfades. Best of luck. 🙂

[J K creative cow]

Thanks for the posts. 🙂

I’m sure every M100 owner could benefit from an OMF or XML option that solves this scenario.

Actually, I’ve mixed and EQ’d two hours of audio (with all 8 tracks packed to the hilt) on M100. The reasons for exporting to an audio program for finishing are many: more tracks available, better organization, ability to work with real waveforms, and (perhaps most important) ability to utilize multitudes of plugins of all kinds not available on M100.

I’ve had very limited success transferring audio information to ProTools (thru FCP) using XML. Transferring to ProTools via EDL is a piece of cake but audio-level info doesn’t remain in tact. I guess this means weeks worth of work down the drain without reconforming all those audio levels. Thanks again for the comments. An OMF to ProTools option could really put M100 back in the race.