Final Cut Pro X: My first impressions
June 23, 2011
There’s been a lot of excitement in the air about Final Cut Pro X since the SuperMeet at NAB in Las Vegas many weeks ago. It’s been like a friend telling you about someone they want to set you up with on a date, and they tell you all sorts of things about them that get you excited about meeting them and builds expectations, so there’s a lot riding on the first date. And then comes the day of the date, and after this crucial first date you realize that this is a wonderful person, but they still have some growing up to do. They are going to get there, but they are not at the same place where you are at yet in their stages of life…
After two days of pouring over the entire online manual and editing with Final Cut Pro X I have to say there are things I love about it that I’ve always wished Final Cut Pro had (performance, integrated metadata support, background processing), and things that are deep disappointments (lack of XML import/export, lack of multitrack audio editing, splitting tracks, exporting stems). Final Cut Pro X is like a precocious teenager that still has some growing up to do before they are ready for the adult world, but they have prospects, and we simply have to take a wait and see attitude. I can’t depend on it for mission critical work, however, I will use it for editing and see what it can do, and over time, and as it evolves, it might become part of my professional workflow.
I like the product and I think Apple did more things right than wrong. We have to take a moment to pause and reflect this is a version 1.0 product, not 10.0 like the splash screen states. But the things that are missing are not consistent with the hype, and there lies the rub. It’s possible that the way this product was released at the same time support for the current version was dropped may have done huge damage to the brand among professionals, but on the other hand Final Cut Pro X bring excitement and sizzle to the majority of people editing everything besides professional productions that require complex workflows and resource sharing. This much larger group is the future. Sophisticated editing has become democratized. Apple is betting on the new generation. When it comes to shareholder value and market share, there is no room for nostalgia or catering to the old ways. Leave the pros in the dust, their days are numbered, at least that’s the message I hear through Apple’s actions. Apple can say they support professionals, but their actions say otherwise, and as Aristotle reminds us in The Poetics, character is revealed through action. It’s clear that the future lies in tens of millions of individual editors, not in tens of thousands of professional editors. I’m sure many of the missing pro features will be added.
Here are three interesting threads I’ve been following this week:
Larry Jordan: Ain’t Nothing Like It In the World
My response to Larry’s blog post:
Larry, this post has been very useful and thought provoking. While Final Cut Pro X has a slick interface and provides sizzling performance, I can’t imagine using it in a professional environment. Without the ability to place audio in individual tracks for exporting to a sound editing and mixing application, without multi-cam, without the ability to import legacy Final Cut Pro projects, without EDL or XML export for transferring work I can’t take it seriously in a professional environment. This resets the clock back to version 1.0 and it’s a travesty. [PAUSE] sip on Apple Kool-Aid [PAUSE] Final Cut Pro X is revolutionary, it’s awesome, it’s what we’ve all been waiting for! 64 bit performance, background rendering, new interface, none of this could have been done in an evolutionary way the way Adobe does with their applications, Apple is about revolution and what Apple tells us we’re going to like, we’re going to like, and two or three versions later, we’re all going to say, why did we not do it like this all along?
My response to Philips’s blog post:
At the end of the day, I think much of the anger and frustration is ultimately about the gap between what works today (Final Cut Pro 7) and what is promised (some future version of Final Cut Pro that supports a professional workflow). In this interim many of us will have to continue using Final Cut Pro 7 with no idea how long this gap is going to be with our work, our livelihood now depends on an unsupported product. Imagine the outcry if Avid did the same thing to their users? But Avid would never do this, their editing applications are their livelihood, on the other hand, Final Cut Pro is a tiny sliver of Apple’s business, and so given this fact we have plenty of justification in being concerned, it’s hard not to feel as a professional and educator that the rug has been pulled from under me and there is no soft landing in sight.
One of my contributions to the discussion thread:
Goes to show that in the wake of all the hype, reality is now setting in. This is becoming a fascinating case study in expectations, and the meaning of the “Final Cut Pro” brand. It’s a risky strategy to kill off an old product, replace it with a completely different one, and call the new version “awesome” as if it was the second coming. As “iMovie Pro 1.0″ FCP X is brilliant. As the next version in the Final Cut Pro line? It’s ludicrous. It’s going to take the hyperspace edition of the reality distortion field to fix this situation…
In some ways this break between the old ways of Final Cut Pro and what would have better been called iMovie Pro 1.0 gives us all a chance to re-evaluate our choices of editing tools. I started on Avid, perhaps it’s time to take a look at where they are at, I stopped using Avid with the introduction of Final Cut Pro 4.5 in what now seems like ancient times. This might also a good time to see if Premiere Pro is worthy of this role, since Adobe has a good track record of evolving applications and not leaving their professional users out in the cold as they evolve their products (I’ve been using Adobe Photoshop since version 1.0).
The time has come to look around and play the field, for no matter what happens in the future, one thing is for certain, Final Cut Pro as we know it has come to the end of the line, it is a dead product with no support. We have to consider the tradeoffs of jumping over the chasm between where we are with Final Cut Pro 7 and the promises that Final Cut Pro X will grow up fast enough to meet out needs and fulfill our desires. For now I will continue editing my mission critical work with Final Cut Pro 7 and experiment on short projects with other tools and see what happens. The day Final Cut Pro 7 stops working due to an OS X update or new hardware incompatibility will force a change, but for now, it’s still smooth sailing with a lot of underlying anxiety that comes with editing on a dead platform.
Video from Abattoir Rising, a work-in-progress documentary by Audrey Kali and David Tames.