MAC Crap... FCP crashing all the time with HMC Transc. Footage

MadHMC150

DVXuser Sponsor
So here goes....

After much grief over the last couple days, we cant seem to get FCP to export a friggin decent final product!

Everything that takes over, say 10 minutes to render crashes - prores, mov, mp4, etc etc. The weird black screen that says there was an error and the mac must be restarted comes up the last 10 times we have tried.

The only thing that DOES work are quick mp4's... I set up a clip that should have been 13mbs and it came out looking like crap and isn't even web usable.

We need to get this thing exported for web asap and then Blu-ray/DVD later.

Any help appreciated - PC's have never done us this dirty :)
 
Last edited:
Give me some more specs! what system are you running? OS version? FCP version? Quicktime version?... have you ever had success on this computer before?...
one simple little app that fixes a lot of little bugs is called FCP Rescue, Google it, it's free!

That window that you describe is called a "Kernel Panic Attack" and could be cause by something small on your system or maybe a hardware failure!... if you purchased Apple Care, there's a CD in that box that helps to test you Computers hardware!

but lets start with the basic system info, and workflow proccess!
 
Sounds like bad RAM to me, but you have absolutely no details about your set up.

PCs also crash; it's better to details your system and hardware if you need help. I haven't had a crash on any of my Macs in nearly four years, but we run pretty clean systems.

Let us know.
 
Thanks super,

Its a new mac book pro, with most of the latest stuff (besides maybe a latest update.)

I don't have it in front of me now but I will find out shorty.

It has worked before, I guess when the project was a little more simple. We are working on a 1TD esata external HD that hasn't given us problems before...

going to try that rescue - thanks. More to come!
 
I take it then that you have the 17 inch model because the 15 inch models do not have an EC/34 slot.

And if that is correct, which EC/34 adapter are you using for the external HD?

Which version of the OS and what version of FCS?

How much RAM and is it Apple installed or 3rd party?
 
Two other questions?

Is it FCS2 or FCS3?

And can you hook that external via FW or USB2?

Also which EC/34 card are you using?
 
Let us know and we can solve this.

My guess is that the issue is the EC/34 adapter if the installs of OS and FCS are good.
 
So here goes....

After much grief over the last couple days, we cant seem to get FCP to export a friggin decent final product!

Everything that takes over, say 10 minutes to render crashes - prores, mov, mp4, etc etc. The weird black screen that says there was an error and the mac must be restarted comes up the last 10 times we have tried.

The only thing that DOES work are quick mp4's... I set up a clip that should have been 13mbs and it came out looking like crap and isn't even web usable.

We need to get this thing exported for web asap and then Blu-ray/DVD later.

Any help appreciated - PC's have never done us this dirty :)

One thing you could try, if it's a software problem, export using File-Export-Quicktime Movie... with "Current Settings", don't make it self contained.

This should be very quick. This will produce a relatively small file (as it refers to the original clips rather than containing all the footage).

You can then open this quicktime file in either QT Pro or Compressor and convert into your format of choice. You can even use it in iDVD if you want.

Good luck.
 
A userspace program like FCP is hardly causing a kernel panic. This is usually only caused by kernel bugs (unlikely), buggy drivers (possible) or hardware faults (very possible).
 
A userspace program like FCP is hardly causing a kernel panic. This is usually only caused by kernel bugs (unlikely), buggy drivers (possible) or hardware faults (very possible).

That's what I'm thinking as well.

My guess is the EC/34 card and drivers.

Some have flakey implementations.
 
I never got the versions from the computer, we ended up just not using the esata adapter and it worked fine :)

Thanks for the help guys, stupid little adapter.
 
Back
Top