Previous Posts by Topic

Archives

For the most part, this is not a review of FCP X. If you must know, I’ve used FCP X a little bit and I like its sleek interface and speed but, even more, I miss a lot of Final Cut Studio’s functionality, particularly Color. If FCP X matures into something more professional (i.e., more robust editor, plus a truly sophisticated color grading tool) I might embrace it. If it doesn’t, I will embrace something else.

The biggest problem for me, and for many others I suspect, is that I don’t know where it’s going and what it will become.

What’s been most puzzling in the aftermath of the FCP X is that so many people outside the professional production community — journalists, software developers, consumer video hobbyists, etc. — have tried to serve as apologists for Apple even though they have little experience editing professionally (i.e., for works that are publicly exhibited in broadcast, theatrical, or home video environments).

So, instead of reviewing the program in depth, I want to add my $0.02 to the ongoing FCP X debate by trying to articulate very clearly why I and others are frustrated with Apple and — yes — why we’re considering switching.

In the Q+A format below I try to address these (sometime maddening) comments.

Let me point out that the comments to which I’m replying are composites or, at times, actual quotes (marked with asterisks) of comments I’ve found in news articles, message boards and elsewhere. And if you don’t believe me, Google them.

“Editors are stupid if they upgraded on day one. I don’t know any pro I’d hire who jumps into something brand new and gets rid of their old stuff immediately.” *
I know of no one who threw out FCP 7 and assumed they’d jump straight to FCP X. Indeed, no pro worth her/his salt would ever migrate from one FCP version to a new one in the middle of a project. Final Cut 7 was an aging application that lacked many well-integrated features found in Premiere Pro and Avid. Editors have been begging for a new release of Final Cut for years. It’s logical for editors to be excited to try it. If anything, the number of pros that downloaded it on its release date shows a lot of passion for the Final Cut brand!

“How can you expect a brand new product to be fully functioning and have all its features included on Day One?”*
Actually, for two reasons: First, because no previous version of Final Cut Pro reduced functionality of its predecessor when it was released. And, secondly, because Final Cut Studio 3 was pulled on the same day, suggesting that the old Final Cut was indeed replaced by FCP X.

Apple can’t have it both ways — FCP X is either:

a) an update — and hence it can carry the name “Final Cut Pro”, and should be reasonably expected to carry over the same feature set, or

b) not an update — and so can be forgiven for not having the same features as Final Cut Pro, but it should not be named as such.

By using X instead of “10” Apple may be trying to have it both ways… but they can’t. It’s wrong to claim the “Final Cut” name for marketing purposes, but not own the legacy of expectations associated with the application — particularly when doing so casts the new version in a bad light.

“Your Final Cut Studio 3 suite of applications still work.”
“No one is forcing you to upgrade.”
“I was unaware that we lived in a world where software upgrades were mandatory.”*
Because FCS3 has been declared end-of-life, at some point — perhaps soon, maybe in years — it will no longer work, either because of an OS upgrade, changes in hardware, failure to support a new camera, etc. Transitioning to SOMETHING new is inevitable.

Since FCP X doesn’t allow one to open Final Cut Pro 7 projects, FCP7’s usefulness is today greatly reduced for the future, assuming one plans to adopt FCP X. As a point of comparison, Adobe Premiere Pro, for example, can open FCP 7 projects. (For an explanation of why opening legacy projects matters, see below.)

Finally, the issue for those of us in the educational community who teach editing is a pressing one. For us, Apple has forced a moment of decision. Beginning in August, when classes begin for most of us, we must decide whether to:

a) teach a “dead” application, which students cannot even purchase for themselves;
b) switch to an unfinished application that does not yet include features that are important in any professional’s skill set;
c) switch to another company’s application (e.g., Avid Media Composer, Adobe Premiere Pro, etc.).

In such a scenario, option “C” begins to look like the most logical solution.

“I haven’t seen a negative review of FCP yet from someone who took 10 minutes to learn about how it was new and then gave it a fair shot. All the bashing I’ve seen has been dishonest, by people who presume that, because something works differently in FCPX than FCP7, it is simply impossible to do.”*
Clearly, if anyone knows what’s possible and what’s not possible to do in the application, it is Larry Jordan, one of the leading teachers of Final Cut Pro. Jordan had access to a pre-release version and has been selling FCP X tutorials since Day One. Here is a quote from his blog:

In FCP X, Apple got some things amazingly right. But they also got key features amazingly wrong. And if they don’t change course, this software, which has significant potential, is going to spin further and further out of control. At which point, its feature set is irrelevant, its reputation will be set. We’ll be looking at another Mac Cube.

“The nay-sayers of this application fear change.”
First, this argument contradicts the earlier argument that “editors are stupid to try to adopt this on Day One.” (See above.)

The people that I know that are the most pissed off are, in fact, longtime FCP users who were looking forward to FCP X’s release. They were looking forward to the release because they had been waiting for an update to the application for several years. Several features announced in April by Apple about the new FCP X were exciting — 64 bit support, support for H264 footage, renders being a thing of the past… If these things had been delivered without “taking away” features that many editors use in their day-to-day work, most editors would have raced to adopt and embrace the other, less familiar aspects of the new application (say, the new user interface).

“The FUD from “pros” are not pros at all – they are competitors from Avid, Adobe, and every little editing software maker who are literally QUAKING in their boots at the incredible bargain that FCPX brings. Period.”*
To account for the backlash against FCP X with this kind of explanation is paranoid. I’m reminded of the quote, sometimes attributed to Twain, “Never argue with a fool; onlookers may not be able to tell the difference.”

“Why the hell should a 7 project open in FCPX? That makes no sense. The entire flippin program has been redesigned. Finish your project in 7 and shut up.”*
The ability to open old project files is essential to any pro or semi-pro editor. Whether working for clients or for oneself, motion picture project files are often re-opened and tinkered with for years after their initial completion. Reasons for this can include such things as revising a corporate video with a client’s new logo, updating a stereo project for surround sound, creating a Blu-ray project for a project that was once released on DVD or even VHS, creating a closed-captioned version to meet new accessibility guidelines, and so on. I could go on for pages about such changes, but I think I’ve made my point.

“Only a tiny segment of pros actually have a need for OMF, XML, EDL, tape output, etc.”You’re probably right — most of us don’t use these things on a daily basis. But that’s like saying “Most drivers, on a daily basis, don’t need airbags.”

OMF, XML, EDL and other features pros are lamenting are professional, which is to say that many of the programs you see on television, in theaters, at film festivals on on DVD run across the need for these specialized tools at critical junctures in their projects. Not all projects need these tools, and not all projects that need them use them daily. But they are critical.

Speaking personally, I often edit my own projects and my projects often stay on one computer, but even then I will use OMF or XML to share these projects with collaborators (e.g., a sound editor using ProTools or a color grader using a Da Vinci suite). These are essential steps to completing a project.

Ironically, the fact that FCP X has sound editing and color grading features far less robust than Final Cut Studio only heightens the need to be able to share your project with other applications!

“It’s released from the app store, so improvements will arrive faster.”First, improvements will not arrive faster because of the app store; the speed of the improvements — if and when they are offered — will be dictated by the software developers.

Regarding the App Store as a delivery method, I don’t understand why the App Store is different from, say, Software Update. But I’m not a programmer, and perhaps there is a good reason for this.

I do find exclusively using the App Store for such a massive piece of software cumbersome and the App Store creates problems for companies and universities that deal with issues like volume licensing and educational sales.

“Be patient. A lot of the features that are missing, like multicam, are on their way.”Are they? If they are on their way, when will they arrive? What will be included? What features will never be “restored” to the application? And finally, share with us the source of your information. Please only cite actual quotes from Apple.

In all of my reading on FCP X, I have yet to encounter official statements made directly by Apple regarding what features will or won’t be continued. A week after its release, the two closest things we have had to an official communication (as of this writing) are:

b) a response to a handful of criticisms in a hastily blogged response by David Pogue, a consumer tech journalist for the New York Times. Despite his attempts at helpfulness, Mr. Pogue is not an appropriate or even necessarily a capable messenger for any information that needs to be relayed by Apple to its current user base of Final Cut Studio users. His initial review and subsequent defense — which showed special access to Apple developers that pro users don’t have — sadly did damage to my respect for him. Though perhaps unintentional, his special access makes him look like Apple’s “embedded” reporter at the New York Times.

Final thoughts:

For many of its earliest years, Final Cut Pro was considered non-pro by many in the editing community. Avid reigned supreme, and many editors stuck out their necks by committing to Final Cut Pro. Though it’s largely an emotional, not a rational, connection, many editors feel a deep loyalty to Apple for the journey they’ve taken together as FCP ascended in reputation and market share. Now, to feel as if their needs have been ignored and, worse, replaced by the need to woo a consumer market… well, for many it is a very bitter pill to swallow.

Like any misunderstanding, the way to mend things is via openness and communication. But Apple’s lack of communication — and the othersignals it has sent regarding professional applications and tools — accounts for much of the anger and anxiety many editors are feeling. Unless Apple lets us know otherwise, can we be blamed for interpreting that the “Pro” in Final Cut Pro X may actually mean “pro Consumer”, and that the “X” may stand for ex-Pro?

If, as Ubillos suggests, FCP 7 projects will never open in FCP X, then I — and thousands of others — will be switching to something new. Here are our options:

love me and i will be in your heart. hate me and i will be in your mind. polarise people. dramatise the differentiating idea. that’s how steve works. that’s also how very very successful marketing campaigns work – ie ones that sell product to prospects.

@Regista: Yeah, the people using Apple’s ProApps are just a drop in the bucket, no question. My statement at the end was just pointing out a tiny irony — that the way for Apple to gain (consumer) customers was to shed (professional) customers. But I’ve developed some thoughts on how Apple’s actually trying to have it both ways in my new post today.