Export from FCPX: Failed

Hi

Just finished another project in FCPX, and went for the export with compressor settings as usual. However, all I get after a while is a "Failed" message. No further explanations, no hints to where the error might be.

Have any of you wiz's experienced something similar?

If I export the whole thing to Compressor, drag and drop a preset, the same thing happens.

I would be very glad to receive some help, as this project has to air today.

Thanks!
Gunnar Kristiansen

Wow … searching forever, then writing here, and THEN I find this:

support.apple.com/kb/TS3844

…I will check it out right away!

However, having 200GBs free HD space should be sufficient, right? The final file will only be like 100MBs…

Should be more than enough. Have you a corrupt clip in there somewhere?

peteramwiggins wrote: Should be more than enough. Have you a corrupt clip in there somewhere?

Not that I know of.

I made the export to my external drive - it all worked like a charm now! Seems that these QT movie exports needs A LOT of space while exporting!

Remember you must leave 10-15% of all drives free. So if you have a 2TB drive, you've actually filled up that drive.

Did you actually get a message that said says "Failed: Quicktime could not access a file. Offset too big." ?

Reason I am asking is that out of the blue a couple of days I started getting a "Failed" message when exporting. I nearly had a heart attack. Anyway, no matter what I tried I could not get it to work. Even when I tired to export small test scenes that had worked previously (all settings the same) I kept getting the failed message.

I had recently installed mLooks, but this did not seem to be the cause.

Previously I had been rendering to my internal drive, but had switched to an external drive for the render with the Failed message. Rendering back to the Internal drive also got the failed message.

Eventually I saw a thread somewhere in the Apple Support Forums that mentioned you might have to go to Utilities and run Repair Disk Permissions. I did this, but the Utility said there was nothing wrong with the Disk.

However, when I tried to Render again it worked.

Not sure what happened, or really why it started to work again, but it was pretty worrying (the reason I moved to FCPX / Apple was because I became fed up with multiple problems Premiere on the PC due to conflicting hardware / software issues when rendering).

BenB wrote: Remember you must leave 10-15% of all drives free. So if you have a 2TB drive, you've actually filled up that drive.

My internal drive is 1TB, with 223GB free. So no problem there as far as I can see.

simonpwood wrote: Did you actually get a message that said says "Failed: Quicktime could not access a file. Offset too big." ?

No, only "Failed".

My reasoning about the free harddisk space came solely from reading the Apple document, that I linked to in my initial post.

Here under PDF TUTORIALS get the FCP X Maintenance doc.
fcproxuniversity.com/FCPro_X_University/Curriculum.html

Also, since these are new releases with a few bugs, go to Digital Rebellion (dot com) and get the free Preference Manager app. Use Otto safely and properly delete both FCP X and Compresso 4 preference files.

Not sure if it'll help, but it may.

When you run Disk Utility, always run the REPAIR options, never the Verify (waste of time), on ALL attached derived. It will always find something to fix, no matter how minor. And on Lion, run it at both levels of the drive; physical and partition.

BenB wrote: Here under PDF TUTORIALS get the FCP X Maintenance doc.
fcproxuniversity.com/FCPro_X_University/Curriculum.html

Also, since these are new releases with a few bugs, go to Digital Rebellion (dot com) and get the free Preference Manager app. Use Otto safely and properly delete both FCP X and Compresso 4 preference files.

Not sure if it'll help, but it may.

When you run Disk Utility, always run the REPAIR options, never the Verify (waste of time), on ALL attached derived. It will always find something to fix, no matter how minor. And on Lion, run it at both levels of the drive; physical and partition.

Thanks for sharing!!