FCPX is Ready for prime time

[Shane Ross]

It’s that comment that prompted my response. If that wasn’t said, I’d have left well enough alone. We all know FCX is good and used in many pro environments. But “learn it?” I have no reason to

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Charlie Austin]

[Oliver Peters] “In my experience, compounds should be completely avoided at all costs, except for effects nests and the like. These have ramifications later, like when you try to dupe+used clips to create a “consolidated” event.”

Agreed. CC”s work fine, except when they don’t. I know a lot of people have requested easier versioning.
————————————————————-

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

[Jeremy Garchow]

[Douglas K. Dempsey] “I ask because when I versioned using duplicate projects, my folders grew geometrically. “

You can make folders in the Project Library. For my versioning, I typically have a few working sequences, and then a folder marked “zOld” and put older cuts in there.

You can even quit FCPX, Make a new folder in the Final Cut Projects folder, drag a few Project folders in to it, launch FCPX, and FCPX will have the exact same organization with folder names in the Project Library.

This way, I can drag multiple Projects to the zOld folder. Something you can’t do in the FCPX project library.

This makes me think that one day, FCPX folders are going to get “packaged” one day.

Jeremy

[Charlie Austin]

[Jeremy Garchow] “You can make folders in the Project Library. For my versioning, I typically have a few working sequences, and then a folder marked “zOld” and put older cuts in there.

You can even quit FCPX, Make a new folder in the Final Cut Projects folder, drag a few Project folders in to it, launch FCPX, and FCPX will have the exact same organization with folder names in the Project Library.

This way, I can drag multiple Projects to the zOld folder. Something you can’t do in the FCPX project library.
“

I do the same thing. Works quite well. Remembering to not include and/or delete render files is kind of a PITA though.

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

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

[Jeremy Garchow]

[Charlie Austin] “I do the same thing. Works quite well. Remembering to not include and/or delete render files is kind of a PITA though.”

Yes.

I go back and forth.

As someone that needs to maintain archiving I really appreciate how tidy the FCPX file system is. You can move things to different machines very easily, including render files, and everything just relinks so easily. Or you don’t even need to relink, it just works, even if it’s a new drive with a new name, etc. It’s very handy for archiving, very handy for restoring, very handy for moving things around en masse.

Then there are days where I’m like, “F*ck!! If FCPX would just allow to put the render and Proxy Files where I want them!!!!”

‘Scuse my language. It’s Friday afternoon.

[Jordan Mena]

i can’t say at the moment. But we create or own content as well as promos for said content. from 5 min BTS to hour long doc dramas. all on FCPX.

Jordan Mena | Editor | Colorist | Producer
Los Angeles, CA
jordanmena.com

[Douglas K. dempsey]

Yikes! Thanks Oliver & Charlie, I am forewarned.

Oliver, are you going to write a book, Phil Hodgetts-style, on your NLE comparisons and/or FCPX experiences?

Too time consuming, no doubt. We’ll just have to keep reading the blog!

Doug D

[Charlie Austin]

[Douglas K. Dempsey] “Yikes! Thanks Oliver & Charlie, I am forewarned.”

You’ll be fine, though as Oliver points out, CC’s can cause trouble when consolidating Events etc. So… don’t do that. lol

It’s probably worth your time to turn final versions of your cuts, if they’re CC’s, into projects just to be safe though. Particularly before updating to whatever new versions of X appear… CC’s were not really designed to do what a lot of people are using them for… They work, but there can be… issues…

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

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

[Bill Davis]

[Shane Ross] “It’s that comment that prompted my response. If that wasn’t said, I’d have left well enough alone. We all know FCX is good and used in many pro environments. But “learn it?” I have no reason to”

Everyone has a right to their workflows and opinions and they’re all good.

But it’s also become clear from the past two years of debate here, that since X truly did re-invent some of how NLE operations can be expected to happen – it is to an extent HARDER to switch to it if you’re still simply re-enforcing your traditional NLE habits every day.

You may never need to do what X does really well. But if you ever decide that you CAN benefit from it’s strengths – I truly expect you will find it harder to adapt to the longer you wait to open your thinking up to the new processes.

It’s a judgement call. Just like everything else.

Nobody HAS to use X.

But it’s interesting how those who do – “mostly” seem to return after the learning curve praising how much it’s transformed their speed and efficiency – and how well its working for them.

Not all – but most.

Something to consider is all.

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Chris Harlan]

[TImothy Auld] “Happy to hear anyone’s story of their tools and how they work in their situation. But “FCPX, Learn it”?
Please.”

A bit militant, yes. I’m also interested in some clarification over a show or production company at a network vs. the entire network. Situation one, I can easily understand; situation two would be quite a surprise.

Oh, what the heck:

Avid. Learn it.

I mean, Premiere Pro. Learn it.