Export problem

[John Davidson]

I’ve submitted tickets on it so I’m sure they’re quite aware. There are also many Apple Discussion forum posts out there about it.

What you’re doing when you delete the renders is forcing the program to rerender at the same time as you are exporting. I think the problem is that render files are getting corrupted and by blowing them away the program is starting fresh, so to speak.

John Davidson | President / Creative Director | Magic Feather Inc.

[Chris Hunziker]

Thanks again, John
It was quite a long project, so it took some time to create a master file, but your workaround works well.
Of course I still hope, a 10.0.9 version will soon be available and solve the problem.

On another note: Is it advisable never to turn “render in background” on and only render the final product or even let FCPX render automatically while exporting?

[John Davidson]

[Chris Hunziker] “On another note: Is it advisable never to turn “render in background” on and only render the final product or even let FCPX render automatically while exporting?
“
I normally keep background render on, this is just a little bug that I don’t doubt will be patched up sooner rather than later. Even now, I can’t seem to recreate the experience in a predictable way. It’s just some weird bug.

John Davidson | President / Creative Director | Magic Feather Inc.

[William Ridenour]

Did you mean “quit” final cut in no. 2? Also, it is now July 2013 and I don’t see a patch forthcoming. But thanks for the work around–it worked great first time. I’m keeping my fingers crossed it will continue to do so.

[John Davidson]

I did! I should fire my copy editor. It’ll keep working, but it’s totally annoying.

John Davidson | President / Creative Director | Magic Feather Inc.

[Deryk Clary]

Worked for me! Thanks!