I remember a long time ago when we cursed Apple for abandoning FCP 7 and foisting FCP X upon us. I can't remember exactly why since I never used FCP X but it seemed the right thing to do once Apple decided not to support FCP 7 anymore and a bunch of editors and writers called FCP X a glorified iMovie... (And I really hate iMovie) so I joined the mob and cursed Apple as we ran FCP X out of town. I continued to cut on regular ol' FCP, and forget all about FCP X. Lo and behold, a year and 3+ updates later, I stumble across David Leitner at Filmmaker magazine this month who really, really likes FCP X and thinks that one day we will learn to love it.
His argument:
A big advantage of conjoined operating systems is that user-interface breakthroughs on mobile devices such as the iPad can readily migrate to Mac apps like FCP X — for instance, use of animation, multitouch, auto-saving, full screen display, Retina display, integration with flash architecture — all of which in turn optimize FCP X for use on portable MacBook Pros with trackpads. On the latest MacBook Pro with Retina display, for example, you can view full 1080p in FCP X’s small Viewer window.
Of particular significance: the 64-bit AV Foundation found in OSX supplants the now legacy 32-bit QuickTime framework (video files will continue to sport QuickTime extensions). AV Foundation brings, at last, multi-core and GPU-assisted speed to Final Cut Pro rendering tasks (using OS X’s Grand Central Dispatch and OpenCL), as well as full color management from input to output and finer time accuracy for subframe events.
In addition to incorporating OS innovations and building out extensive control of metadata and media management, the FCP X team sought to directly address several prominent trends in production: Digital cameras generate endlessly more footage than film cameras ever did, which must be readily reviewable and searchable. Multiple cameras are now common and often wild (no sync). Democratization encourages many to edit regardless of experience; at the same time, audiences expect perfect finished quality regardless of budget.
FCP X’s solutions, in order: fast Skimming with pitch-corrected audio, Keywords & Smart Collections, Multicam (introduced in January in FCP X’s third upgrade in a year), and a friendlier, less cluttered interface for those with less experience, with deep controls located just below the surface for experienced editors.
A big plus for Leitner is that it allows him a new conceptual approach to editing:
FCP X has no tracks. It adopts a different metaphor, one that Aeschylus would recognize. Instead of a timeline with tracks above and below, FCP X provides a single “primary storyline” that serves as a narrative spine, with a beginning, middle and end. Individual clips are “connected” at points along the storyline, floating on, just above (video) or below (audio) the storyline. A complex stack or sequence of clips can be collapsed and nested into a simple “compound clip” that can be edited like a single clip or momentarily reopened into its own storyline for internal editing.
The editor, free from worry about accidentally knocking clips or complex sequences out of sync, can playfully shuffle clips and sequences, focusing entirely on story structure.
Dispensing with the clutter of conventional tracks also favors use of FCP X on mobile devices and compact laptops with smaller screens — a clear nod to the future.
I like my timeline and I hate the iMovie timeline but I won't lie... I'm not hating on FCP X that much now. Maybe Apple was on to something from the get-go but messed up the rollout when they released an incomplete FCP X and abruptly shut down FCP 7.
Also, check out 7 pro editors on their experiences using FCP X.