"The share operation Master File has failed"

Trying to get an 54 minute movie ( about 3,5 GB) on DVD I get the message (after 33%): "The share operation Master File has failed". Deleted the render files, again: "The share operation Master File has failed".

Trying to make a Master file; FCPX shuts down suddenly. Restart the iMAc: same problems.

The iMac: 2.66 GHz Core 2 Duo early 2009. 8 GB 1067 MHz DDR. Events and Projects on external Thunderbolt LaCie. OS X 10.9. FCPX 10.0.9

Any idea?

Regards - Peter

If it always fails at the same point, that may imply some corruption issue there. Deleting render files was a good start, but do have a good look at the timeline around the 33% mark. I seem to recall something about missing frames occasionally causing problems - that is, single-frame gaps in the primary storyline, left behind after a trim operation gone awry.

Otherwise: try exporting ProRes rather than anything else - if you can get a complete ProRes render out, you can compress that separately, rather than trying to do the whole thing in one operation from within FCPX.

After upgrading to 10.9, I initially had no trouble exporting my (typically 30 minute) projects. But the first time I tried exporting an hour-long project , I got that Master File Failed error –repeatedly. I went through the standard trouble shooting list without success. Finally I tried disabling App Nap. which in my case at least seemed to cure the problem.

Russ

Agreed. The first thing anyone using Mavericks should do is disable App Napp for FCPX. Although it is a great memory saving feature for other apps it causes a lot of problems for people who export longer projects from FCPX. Putting inactive apps to sleep is good, but rendering processes should never be interrupted automatically.

- Ronny

I've been trying to work out why I haven't been seeing this problem, despite running some significant export jobs recently. At first I wondered if my system (2008 Mac Pro) was simply too old to support the feature, but reading Apple's vague notes doesn't suggest any such limitation.

My understanding is that App Nap comes into play if you hide FCPX, or normally run it full-screen and switch into another space while it's working. I do neither of those things, I just command-tab into whatever text editor or browser window I fancy, and FCPX carries on working behind those other windows: the FCPX window is still partly visible, so App Nap is never triggered.

My hunch: the next release of FCPX will handle this for us by making use of the App Nap API . Disabling App Nap manually would therefore be a short-term workaround.

Seems the problem is solved. Suddenly the external 500gb HD was 99% full. Couldn't find out were about 200gb was coming from......

Copied 'Final Cut Projects' and 'Final Cut Projects Hidden' to the internal HD and formatted the external 500gb HD. Afterwards I copied both back to the 500gb HD. FCPX is now rendering >60%, so I think everything is fine.

Peter