Oh dear, we will switch to fcpx!

[Erik Lindahl]

The lack of proper timecode readers in FCPX is one of the main issues I have with the app. It’s really hard or impossible to see timecode on clips in a project / sequence vs clips in the browser. Have I completely missed something or is this just the way FCPX is? I didn’t realize how important these things where before not having them.

[Scott Witthaus]

[Andrew Kimery] “It wasn’t pro before, but Apple has made a lot of good strides. ;)”

Hell, it was mid-beta when it was released!

Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter

[Simon Ubsdell]

[Erik Lindahl] “The lack of proper timecode readers in FCPX is one of the main issues I have with the app. It’s really hard or impossible to see timecode on clips in a project / sequence vs clips in the browser. Have I completely missed something or is this just the way FCPX is?”

You can use Clip Skimming to see the current timecode at the playhead position – but really a lot more feedback is needed for certain workflows where this feature isn’t enough to cut it.

Simon Ubsdell
tokyo-uk.com

[Craig Alan]

Thanks Charlie,

One follow up if you can bear with me. What kind of project needs frame matching frame overwrites enough that not having it is a deal killer? Music vid?

I’m sure others would have other ways of doing it, but I played around a bit and connected the browser clip to the timeline clip set markers in each at the frames I’m trying to match, lined them up, trimed the browser clip to match the duration of the primary clip and overwrote to the main story line. Another option: a replace edit and slip it into place.

Also why do folks feel there is something in FCP X code that makes adding this feature such a problem? If X can do three point edits and back timed edits what would prevent it from doing match frame edits?

I tried setting a marker in the browser’s clip and in the timeline clip as a guide for the slip but could not get X to leave the markers in place. Hopefully this is just my inexperience.

Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.

[Erik Lindahl]

That’s sadly an extremely inefficient way of dealing with things and requires using mouse over on a specific item.

[Charlie Austin]

[Craig Alan] ” What kind of project needs frame matching frame overwrites”

In my case, doing advertising for features, we always get at least 2, and sometimes many more versions of the cut. So we have to over cut all our existing work with pix from newer versions. In X, if there are just straight cuts, and you can match the first or last frame it’s easy. But if there’s a dissolve, or there isn’t a good frame to be able to eye match, not having match frame replace is a huge time-suck.

Also folks who do a lot of SFX work, again with multiple versions of the same shot, really need this feature.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Simon Ubsdell]

[Charlie Austin] “In my case, doing advertising for features, we always get at least 2, and sometimes many more versions of the cut. So we have to over cut all our existing work with pix from newer versions. In X, if there are just straight cuts, and you can match the first or last frame it’s easy. But if there’s a dissolve, or there isn’t a good frame to be able to eye match, not having match frame replace is a huge time-suck.

Also folks who do a lot of SFX work, again with multiple versions of the same shot, really need this feature.”

And in my experience (which is not far different from yours, I suspect) I’ve always only got about half an hour to turn around jobs like these, so every second is ridiculously precious – no time for even the most efficient of workarounds.

The other complicating factor for these workflows is the limitation X still has as regards relinking to new material that doesn’t match the original very precisely – one of the great strengths of FCP7 that can still save huge amounts of pain.

Simon Ubsdell
tokyo-uk.com

[Simon Ubsdell]

[Erik Lindahl] “That’s sadly an extremely inefficient way of dealing with things and requires using mouse over on a specific item.”

Yes, it’s not a particularly nicely implemented feature, that’s for sure – especially for those of us who dislike mousing.

Simon Ubsdell
tokyo-uk.com

[Charlie Austin]

[Simon Ubsdell] “I’ve always only got about half an hour to turn around jobs like these,”

Half an hour?! Luxury! (in heavy Yorkshire accent) lol I honestly find basic from i or o replace in X to be really fast, but not having match frame replace brings the process to a grinding halt. A 3 step workaround for what should be a keystroke like other replace functions is… less than ideal…

[Simon Ubsdell] “one of the great strengths of FCP7 that can still save huge amounts of pain.”

Yeah, I miss the “You can’t do that… Do it anyway?” options from FCP 7.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Simon Ubsdell]

[Charlie Austin] “Half an hour?! Luxury! (in heavy Yorkshire accent) lol”

“And you try and tell the young people of today that ….. they won’t believe you.” 😉

[Charlie Austin] “A 3 step workaround for what should be a keystroke like other replace functions is… less than ideal…”

It’s the dissolves and any other transitions that really make it a pain – that and the lack of gang sync when you’re looking for a really tricky eye match.

Simon Ubsdell
tokyo-uk.com