[Peter Ochs]

Figured it out … a mix of drop and non-drop frame soucres is the culprit!

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Figured it out … one of the sources is non-drop while the others are drop frame. Yikes, gonna have to rely on audio sync, which isn’t all it’s cracked up to be in my experience. I see a lot of manual tweaking of multiclips in my future!

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Attaching a screen grab to illustrate the problem I’m having here …

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Thanks for the tip, Tim. I’ll keep an eye on that within compounds to see if that is causing the error.

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

I agree, Nick. This shouldn’t be normal.

But truth be told this was just a small test. Handful of clips, straight cuts, a few basic texts, then compounded and layered with some color correction looks.

If files corrupt this easily, even following all best practices protocols, then am I not warranted in my concerns?

I’ll keep hammering on FCPX and put it through its paces. Maybe this was just a fluke. But I’m not ready to convince my AVID clients that this is the new way forward yet.

I’m a 20+ year professional myself. Been through it all. I’m rooting for Apple and FCPX … it’s just gotta be right.

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Yeah- just apply the “Straight Outta Compton” Filter and and it edits the music for you.

(I heard the “Eazy-E” Filter might be a little buggy, though…)

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

[Jason Porthouse] “* Range tool utterly inaccurate when entering in and out points on the fly – for instance, I usually turn music tracks into secondaries so I can edit them and add dissolves – but try and mark a bar of a track using I & O in the range tool. Seemingly completely random placement. Same goes for clips in the browser.”

Have to agree this is a MAJOR pet peeve. Marking I & O on the fly only marks ranges in the Primary Storyline. So if your music track is a Connected Clip (as they will be much of the time) then you’re outta luck. There needs to be a way to mark IO on selected clips.

In general music editing is cumbersome in X. It’s a shame with the advantage of subframe editing, but some of the current limitation of the magnetic timeline are problematic. Compounding the music edits is one work around. But then you have to “step in” to that every time you wanna edit the track. Seems clunky.

Let’s hope Apple is listening to their Pro Developer Consultants. They have made great strides with each subsequent release. But it seems like it will be 10.2 or .3 before this baby is ready truly for PrimeTime.

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Hey Loren,

Thanks for the reply. I’m up to date on all system and app software, so that’s not the issue.

My work around was to step back into my compound clip, copy all the clips, paste back to the master timeline, blowout the existing compound, re-compound the clips, reapply three layers of effects and … whammo … it is now exporting.

But boy, that is NOT a professional level workflow, IMHO. As an editor, I need to be able to count on things like compounds working solidly in this app. FCPX has a lot of promise and appeal. But I’m still wary of putting my professional reputation on the line with it.

Wondering how many working pros here on the Cow are fairing with FCPX as their main edit app???

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Peter Ochs]

Yup, that does the trick. Thanks, Andy!

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2