Final Cut Pro X on Mavericks - no export?

Confession - I rendered something yesterday. It was only 10 seconds though.

Disable Effects - well I was trying to not tell you completely and hopefully you would figure it out. Here is a quick video (I'm running into a meeting and didn't even get a chance to watch after I recorded. hopefully it's understandable)

Oops. Still uploading give it a few minutes.



- T.

Very nice technique.

"Complex Clip"? That is just the clip's own Timeline, right? Or is that something else?

Thanks for the tips guys. As soon as I get back in the office I'll try to repair my permissions; it's a fresh install so I doubt it had time to corrupt but who knows.

As for rendering I work with wildly different formats so I almost have to, but I'll try to use some different techniques.

I'll keep posted and thanks again!

BenB wrote: "Complex Clip"? That is just the clip's own Timeline, right?

I call it a "complex clip" for lack of a better term. It is in essence an old style (before 10.0.6) compound clip. It differs from a clip in it's own timeline because it appears that FCP treats it differently. If you recall in 10.0.6 and earlier, in the event browser the the icon or glyph of a clip changes to a "compound clip" once you added elements. I like "complex" clip because that is exactly what will happen to your timeline if you start chopping up a complex clip (many times), it will become complex and cause problems. (I actually have an entire tutorial that explains how to use complex clips but zero time to make it!) Hence Apple changed the behavior of Compound Clips to be references in 10.0.6. But that is a whole other topic....

You can see that glyph change in my Custom Resolution Timeline video here:

Look- 90% of the time people are going to tell you to delete your render files and turn off background rendering.

This simply isn't the case, I've found personally, for 10.0.9 and Mavericks.

Major "Share Operation" errors, whether Quicktime -50 or the Frame specific errors can be curtailed, pre-share, by doing two things.

1. Leave Background Rendering on. I know this goes against the internet grain, but in the case of Mavericks and 10.0.9 it works. (Control + Shift + R for Render All, can't be trusted without re-initializing every time FCPX hits a clip it, let's say for now, doesn't like for some reason) I am exporting full length half an hour television episodes with heavy 3rd party effects, known for causing render issues, like Core Melt Slice X and Film Convert by Rubber Monkey. I leave background rendering on during color correction.

2. PRE-TRANSCODE your R3Ds files (lock your RAW changes first via the FCPX plug-in) and also, all of your H.264 files. Apple calls it "Optimizing". Identify these clips in your edits during color correction using your timeline or better yet, your Timeline Index (Because you are on top of your organization, pre-edit ) and shift + F to reveal in the event and optimize them. The H.264 clips are a major contributor to failed share operations in Mavericks with FCPX.

I know Mavs is a pain right now, 10.0.9 isn't caught up to it, but 10.1 promises better stability and more.. but ITM give these two workarounds a chance and hopefully it will ease your pain until the update.

I am on our third episode (Tenth Season, and third full season delivered in FCPX), delivering to four different networks, plus digital copies, weekly on a Mac Book Pro 2.7 GHz with 16 GB RAM (6 and 8 core Mac Pro Towers on stand by)- trust me, I feel your pain, but rendering and pre-transoding non-native or larger than timeline resolution footage that uses spatial conformity settings will help you get a stable export, at the very least, for a master file export to Compressor for bigger/longer format timelines. I started off by setting in and out points and exporting my master files in sections, but after using the two combined processes above, I can do a single export with a lot of in-app and 3rd party effects now.

Also, to answer the thread's original question about "nothing happening" when hitting the Share button, I am seeing this behavior also. Basically, just CMD+Q to quit FCPX and re-open and normal access to the Share operations should be available. Hang in there.

Tight Edits,
Dusty

You know what, I think you might be on to something Dustin; I don't use heavy 3rd party anything for this project (I don't even color correct because it's straight to web...). But what I DO have is wacky resolutions, clips from the web and codec galore (AVCHD, H264 and Native ProRes all looped together like a big dysfunctional family).

I had turned of Optimizing a while ago to try and salvage some disk space because I was too lazy to buy more quality storage, but that would make some sense.

Still not back to the office yet, but I will definitely try all those tips this week.
Thanks!

It is strange and prob seems too basic a strategy- but for me, transcoding non-native timeline material has made long format master exports considerably more stable than if FCPX is doing it "on the fly" during any share operations. Our first show took me two days to finally get exported in sections.

It does seem to be more helpful when effects are involved (I can export master files of H.264 and R3Ds without transcoding, so far, as long as they are sans effects), but it definitely been helpful for us either way. Our second show, as I mentioned above, went out without a hitch using transcoding and BG rendering. *I don't leave BG rendering on, I just turn it on during down time, or during color correction.

I never optimized my clips before, much like you, the trade off in file size/disk space came at too high a price, particularly with long GoPro clips from mounted cams- and I am running two thunderbolt R4s (4 x 2 TBs each) and two OWC SAS enclosures off a tower (4 x 3TBs each). However, I am certainly glad the option is there when it comes to 10.0.9 running in Mavericks.. at least until the big update!

I know it might be redundant, but for anyone else running FCPX in Mavs, make sure and download the latest pro codecs pack from Apple, they can be found here:

support.apple.com/kb/DL1396?viewlocale=en_US&locale=en_US

Best of luck to you!

Cheers,
Dustin