FCP X alternatives

Final Cut Pro X has been out in the wild for over a month. Some of the hysteria has died down, but professional editors – those working in film, broadcast and at post facilities – have started to make some decisions regarding their next move. As a 1.0 application, FCP X doesn’t fulfill the needs required in many established workflows.

FCP X is a love-hate relationship. The people who are drawn to it feel that it’s the next revolution in editing technology. The folks ready to switch to something else point to the lack of advanced features, a radical redesign of the editing metaphor and the loss of compatibility with legacy projects. So, what do YOU do?

Click image for an enlarged view of the GUI.

Option 1: Adopt FCP X

I certainly don’t feel that Final Cut Pro X is either “junk” or “useless”. Clearly, if you like it and feel that it works for you, then the answer is to dive in, learn it and develop workflows that utilize it to your advantage. If you don’t like it, that doesn’t mean that it can’t be helpful for some jobs. Even if you don’t want to use it as your primary NLE – or if you just want to hang on and wait to see what improvements Apple has in store – it can be an asset in your current toolkit.

I see several areas where FCP X can augment other NLEs. For example, HDSLR-based projects shot on a Canon 1D/5D/7D. FCP X handles H.264 files extremely well, so use it as a “pre-edit” tool. Ingest the native H.264 camera files, align double-system sound (such as from a Zoom H4n) using built-in synchronization and color-correct/stabilize shots. Once you’ve done that, assemble a loose string of selects (with handles) and export a self-contained ProRes QuickTime file for further editing in the NLE of your choice.

Another type of project where FCP X would shine is one made up entirely of moves on high-res still photos. The built-in Ken Burns effect – coupled with the ability to access iPhoto or Aperture library files – makes FCP X the easiest tool for these projects. Unlike previous versions of Final Cut, start and end key frames are automatically adjusted when transitions are added. Do you shoot with RED and want to edit in 4K? FCP X is well-suited for 4K projects. Simply export 4K ProRes HQ or ProRes 4444 files from Redcine-X and do your cutting and grading on a 4K timeline in FCP X.

Option 2: Staying with FCP 7

Many ask, “Why the rush to abandon FCP 7?” After all, it’s working as well today as it did before the release of “X”, so simply continue editing in FCP 7, until FCP X issues are addressed by Apple. That’s true, but, of course, all development has now stopped on previous versions of Final Cut and related developer product sales have tanked. Apple abruptly pulled FCP 7 off the market, although they did subsequently allow resellers a limited extension to purchase additional licenses for their customers. The unknown is what happens to FCP 7 compatibility with future OS versions (beyond this release of Lion) and Mac hardware.

Many users have been waiting over four years for significant development in the Final Cut Studio suite (discounting the incremental advances in the 2009 version). Receiving an unwanted answer in the form of Final Cut Pro X, they’ve decided to switch solutions. I think that’s quite a reasonable attitude for most facility users, but the truth is that you can certainly “freeze” your current installation in its present state (hardware, software, OS) and be just fine. After all, there are plenty of users working with FCP 6 running on G5 PowerMacs.

The Shake experience is the closest analog we have. It, too, was EOL’ed by Apple, but has continued to work with newer OS versions and Mac hardware and is still a reliable compositor and effects tool for many. My guess is that the current Final Cut Studio suite has at least 1-3 more years of viability. In fact, some elements of the suite, like DVD Studio Pro, Color or Soundtrack Pro will continue to be user favorites, long after those same users have finally moved to FCP X or another choice as their main NLE.

Option 3: Adobe Creative Suite / Production Premium / Premiere Pro

Adobe’s Premiere Pro CS 5.5 is the NLE closest to what many FCP users would have wanted. A hypothetical 64-bit FCP 8 may have been a lot like Premiere Pro, so it’s natural that many disgruntled FCP users have found a new home with Adobe. The commands, workflows and working styles are familiar to Final Cut Pro editors.

If you own a third party capture card (AJA, Blackmagic Design, MOTO, Matrox), then having the right set of drivers means that the same hardware will work with Premiere Pro. Not to mention that basic FCP 7 projects can be imported into Premiere Pro CS 5.5 via XML.

Many FCP editors have realized they already own Premiere Pro if they bought one of Adobe’s bundles to acquire Photoshop or After Effects. Moving to Premiere Pro for many is as simple as clicking that square, purple “Pr” icon that’s been sitting in the Dock all along.

The move to Premiere Pro isn’t going to be flawless. Like any software, there will be quirks and differences. Yet, I can attest to the fact that there has been tangible improvement in Premiere Pro from CS4 to CS5 and to CS5.5. In this present version, Premiere Pro is a 64-bit, cross-platform application that handles more native codecs than FCP X and offers plenty of real-time performance via the Mercury Playback Engine technology. If you are RED user, Premiere Pro is the only NLE is this price range to allow native cutting with the REDCODE codec and frame sizes at up to RED Epic’s 5K format. Of course, integration with After Effects is a huge selling point, but buyers may also be attracted by Adobe’s aggressive cross-grade promotion for users coming from either Apple Final Cut Pro or Avid Media Composer.

Option 4: Avid Media Composer

Many older Final Cut editors started their nonlinear editing careers with Avid Media Composer. Some gravitated to FCP by version 3.0 and, therefore, perceptions of Media Composer are based on the application in 2002 or 2003. Some had less than flattering impressions of the company based on sales interaction during that time, as well.

Time marches on and those who have maintained a knowledge of the software and a relationship with Avid know that both the company and the Media Composer software are vastly different than those of eight or more years ago. Although not quite as cheap as Final Cut Studio or Final Cut Pro X, Media Composer is still extremely affordable in a software-only form. There’s a 30-day trial for tire-kickers, one of the most aggressive pricing policies for students and it’s now doubly attractive to FCP owners with a summertime cross-grade promotion.

Avid Media Composer offers many advanced tools simply not found within other NLEs. These include stereo 3D, AMA for native camera support, optional script/speech-based tools (ScriptScync and PhraseFind) and more. Ironically Avid added many features that are said to be more “FCP-like”, such as in-context timeline editing (Smart Tool) and AMA, which allows users to edit with existing files in place without first transcoding media files. Conversely, Apple adopted many Media Composer traits in its development of FCP X. Of course, earlier FCP projects can be imported into Media Composer using tools from Automatic Duck or Boris FX.

The Media Composer image I posted is of the prototype user interface presented at recent Avid user events, which showcased a technology preview of the next version. Although no specific feature nor even the design is locked in yet (and there is no announced release date), some of the bullet points include 64-bit operation and the ability to integrate an expanded range of third-party hardware.

Interestingly enough, this suggested UI drew some online comments that it copied FCP X. I would offer that those comments are generally uninformed. Enlarge the image and you’ll see most of the familiar Media Composer tools designed into a modern, darker, dockable and tabbed layout. If anything, this UI design resembles Premiere Pro more than FCP X and includes come interesting clues, like tabbed sequences and a mixer panel akin to Pro Tools.

Option 5: Other

I’ve concentrated on these four options, because they are in a similar price range, keep the user on the Mac and are all viable industry leaders. But there are other options, as well. The two Mac solutions I didn’t mention are Autodesk’s Smoke for Mac OS X and Media 100. I doubt most FCP switchers would move to Smoke, because that’s a completely different business model and price structure. However, those needing more advanced finishing tools designed to be integrated with FCP 7 and Media Composer workflows would be happy with Smoke. Media 100 is a step in a different direction. Still one of the easiest NLEs to use, Media 100 has continued to advance with moderate development under Boris FX. It’s a viable editor with good integration for After Effects, Boris Red and even native RED raw files.

Apple’s handling of the FCP X product launch has turned off some users so completely that they are also contemplating a move to Windows. Adobe’s and Avid’s tools are all cross-platform and Windows 7 Professional 64-bit is a very good OS. Other NLE choices are opened with such a move. These include Sony Vegas, EditShare Lightworks, Grass Valley EDIUS and Avid DS.

Whether or not you decide to switch or wait it out, it’s clear that Apple’s launch of Final Cut Pro X has shaken up the landscape. More options – more tools – and no clear market dominance – that’s what the next year seems to hold.

©2011 Oliver Peters

More FCP X thoughts

Thanks for the positive comments on my previous post. As a review of Final Cut Pro X, I wanted it to be even-handed. It was intended to let you know about the program without injecting too many of my own opinions. After all, FCP X does work for many potential users and my goal as a reviewer is to try to determine whether or not a product achieves the objectives its designers set for it. I wanted you to be able to have the basic facts and decide for yourself. This post is different, written from the niche I work in, advanced post-production.

From creative platform to iDevices

FCP X is hard to judge. It is viewed through the lens of twelve years of ever-increasing professional development that culminated with FCP 7 and the 2009 version of Final Cut Studio. In that time Apple, capitalized on the positive marketing vibe generated by the success of prominent users, like A-list editors working on high-visibility projects. In that time Apple also evolved from a niche computer company to the dominant mobile devices company. It seems pretty obvious that the new Apple view of the world is different from that of Final Cut’s biggest champions.

Apple has always been about the user experience. Hiding the technology under the hood and making things easier, more intuitive and more fun. The original acquisition of Final Cut Pro by Apple was intended to keep a QuickTime-based video editing tool on the Mac and to offer a powerful multimedia editor that served a variety of needs. With that purpose in mind, it was OK if certain advanced features and functions were missing. All it needed to be was an 80/20 application that could work with FireWire (then limited to DV) tape and camera sources and other QuickTime files.

Had the story ended there, Final Cut would have never been widely adopted into advanced film, video and broadcast environments. Final Cut up through version 7 evolved into a viable competitor to established NLE companies like Avid, thanks to the ecosystem of third-party hardware and software that had grown up around FCP. If it weren’t for original vendors like Pinnacle, Aurora, Digital Voodoo and others, FCP would have never been used for advanced post.

The attraction at first was price – one that was effectively subsidized by Apple’s hardware sales. FCP X presents a much truer reflective of cost. To equal the features of Final Cut Studio, you have to bundle FCP X, Motion 5, Compressor 4, Automatic Duck Pro Export and DaVinci Resolve for a total of about $1,900. Then you still don’t have advanced DVD/BD authoring or mixing. It’s likely that many of the missing features in FCP X will be augmented by free or paid updates or third-party solutions. If so, the bundle could run more in the range of $3,000 to replace what you now have in Studio for $1,000. Of course, most FCP X users will never need more than what can be done with FCP X at $300. This says to me, that Apple is focusing on the broader potential customer, so those that need the advanced features should be willing to pay for them. Therefore, the third-party developers also profit from the transition. A win-win from Apple’s point-of view.

Many point to the benefits of Apple’s push towards democratization in driving down the price of the NLE. They would argue that without FCP, there would be no improvements nor price reductions in Avid products specifically. To some extent I agree; however, I also feel that’s revisionist history. When FCP came on the scene, there were already other competitors pushing Avid to produce lower cost models. Media Composers of the day were full turnkey units (hardware, software, storage, monitoring) and if you configured a comparable FCP system with an I/O unit like Pinnacle CineWave, the cost really wasn’t that far apart. Yes, FCP was cheaper and pushed software-based models earlier, but Avid was in that game, too, albeit a bit late. One oft-ignored impact of FCP’s rise to dominance in many segments is that it killed off many of the other innovators, like Edit, ImMix, Lightworks (almost), Media 100 (almost) and others.

Time to reboot

Which brings us to the present. Final Cut Pro X is a reboot of sorts. Final Cut before “X” has grown into a very versatile platform that can be used in many enterprise environments. But, that’s really not what FCP was ever intended to be.  Apple doesn’t play well in the enterprise world. When you look at the on-again, off-again interaction with the enterprise user, through tools like Xserve and Final Cut Server, it’s clear that Apple is more interested in the broader base of end users. Apple is more than willing to eliminate under-performing software or replace one product with an updated, but often incompatible rewrite (AppleWorks, Shake, LiveType, Final Cut Express, Final Cut Server, all FCS apps, Dot Mac, MobileMe).

The sort of predictability and access to road maps that an enterprise client can get from Avid, Quantel, Microsoft or HP simply isn’t in Apple’s DNA. This makes it very risky for any customer or partner to put all of their eggs in Apple’s basket, except for a short-term advantage. You’re either on-board for the roller coaster ride or not.

In that context, Final Cut Pro X takes the application back to the essence of what was originally intended for Final Cut. A product that made it easier for both skilled and unskilled editors to achieve professional results with less complexity. It isn’t necessarily intended for the same advanced workflows where FCP has succeeded to date. There’s no need for Apple to do that any longer, since advanced post, albeit a niche, is quite nicely accommodated on the Mac platform by Avid, Adobe, Autodesk and even Media 100. There’s little concern anymore of not having any video editing tool available for the Mac.

It’s very tempting to true to boil this down to a “consumer vs. professional” argument, but I think that’s inaccurate. I’m coming around to the view that for Apple, the moniker of “Pro” isn’t defined by the target user, but rather by the performance capabilities of the software. Compare iPhoto with Aperture or GarageBand with Logic. In both categories, Apple offers two solutions: basic and advanced. The demarcation is in the tools offered and resources required by the application and not who uses it or how it’s used. Podcast producers often rely on GarageBand for recording, editing and mixing. Professional and amateur photographers alike use Aperture. It seems clear than Apple has set up the same pairing with iMovie and Final Cut Pro X. Even in the broadcast space, there’s the possibility of letting a reporter assemble a basic story with iMovie and then send the project to an editor using FCP X for polishing – or at least that’s the vision.

The missing features

Some argue that Apple will quickly add back in the missing features of FCP 7. I’m not so sure. Final Cut development went that route of its own accord over twelve years, but I believe the goals have changed. Apple has been coy about returning specific missing features, but they have promised to release “hooks” that will allow other developers to provide them. In fact, we are already seeing that in some of the free effects presets posted by users. FCP X effects are really Motion projects, so Apple has enabled users to leverage Motion 5 in the same way as was previously done with FxScript. There are already some early FCP X utilities on the market from developers like Assisted Editing and Automatic Duck.

Unfortunately by releasing FCP X in the way it was done, Apple has destroyed the existing ecosystem built around FCP and all developers start at square one again. Some are happy for the new opportunities and others express concern. By ignoring legacy support and releasing a product with many gaps, Apple has alienated many high-end professionals. You can argue all you want that these users constitute an insignificant niche, but for developers, it’s these users who will pay thousands of dollars for capture cards, accessories and plug-in packages.

The danger of re-inventing the wheel

I have nearly four decades of experience in broadcast operations, production and post, with most of it in editing. I’ve gone through numerous transitions and along the way operated, reviewed or been associated with well over two dozen different edit platforms. One of the things I’ve seen in that time is that non-standard workflows and interfaces eventually return to accepted concepts. After all, editing tools are built on over 100 years of post production practices.

For me, FCP X simply is NOT faster nor easier, just DIFFERENT – precisely because Apple has radically changed the way an editor organizes the information and works in the timeline. I will freely admit that my nonlinear days started with Avid and I first disliked moving to FCP. Now, after eight years of mostly non-stop experience with Final Cut Pro/Final Cut Studio, FCP 7 has grown to be my preferred editing tool – warts and all. It’s incredibly versatile, but that level of user control was dropped from FCP X.

I use the timeline as much as a scratch pad as the location for a final assembly. Place multiple clips onto top tracks and preview them as one option versus another. Or build little sub-sequences at the back of the timeline and then copy & paste these into the place I want. Work rough and then clean things up. FCP 7  and Media Composer give me that freedom and precision. FCP X does not. Of course, some of this is handled through Audition clips in FCP X, but that requires that you know and select the possible options first and then combine them into an Audition clip, which can be cut onto the timeline for previewing. To me, this requires more work than I go through in all other NLEs.

My ideal NLE would likely be a mash-up between Final Cut Pro 7 and Avid Media Composer, augmented by the performance features of FCP X and Premiere Pro. It’s difficult to predict the future where Apple is concerned, so I don’t want to discount the possibility of FCP X picking up steam with my customers. If that’s true, then I’ll be there ahead of them; however, today, FCP X is the wrong tool for my projects and those of my clients.

Take the Precision Editor, as an example. This highly-promoted feature is little more than a toy in my view. Trimming in FCP X is much weaker than in FCP 7 and that version wasn’t anywhere close to having the trimming control of Media Composer. Asymmetrical trimming in FCP X is virtually non-existent. The basics, like trimming L-cuts, haven’t been properly implemented. For instance, split edits (L-cuts, J-cuts) are only based on trimming audio track in-points in FCP X, instead of either audio or video as in most other NLEs.

It’s these and many other little things throughout FCP X that will hinder its adoption by the upper tier of users. That has a cascading effect. In a film school, why adopt FCP X for your students, when they’ll encounter Avid Media Composer as the tool of choice out in the “real world”? If you teach a digital media curriculum, whose graduates are destined to work in the corporate and web arena, then isn’t Adobe Create Suite better suited? What Apple has in effect done – by rebooting Final Cut as FCP X – is to pull the rug out from under its own advances earned over twelve years of FCP development. They’ve handed an extraordinary gift to competitors who can better service these smaller, but still important, market segments.

The post production niche

I’m currently cutting a feature film, shot on RED, using FCP 7 for the edit. I’m working with two assistants on a couple of systems plus a second editor. I’ll have multiple FCP 7 projects, scores of bins and probably over 100 sequences when I’m done. Plus it goes through a Pro Tools mix and grading in Color. No way would I ever consider using FCP X for this project. It simply does not work for me or most other film editors.

“Well,” you say, “that’s the exception.” I agree. But now contrast this with a simple story assembly for a corporate marketing video. That would seem ideal for FCP X. You get the cut done and it worked perfectly. The next day the client calls with changes and you realize that you have to reuse some of the elements and sequences from last year’s version, which was cut in FCP 6 or FCP 7. Oops!

In the work I do – ranging from spots to corporate to TV to films – I simply don’t see FCP X version 1.0 as functional for any of my real world workflows. I find that a shame, because there really is a lot there to like. Admittedly, my brain has learned to organize media in a certain way and to think of audio and video as tracks or channels. It’s not just training, but also the most logical way to work.

The analogy has been made to musical instruments. Experienced editors play their system like an instrument. You don’t have to think about how to do things, because your brain and muscle memory instinctively take care of running the system that you know so well.  The proponents of FCP X frequently have difficulty explaining why the new way is better. I understand the how and why, but I just don’t see it as better. I also don’t see it as inevitable that it will succeed, just because it is Apple. I realize “pro” has many different meanings to people, but in my world, “pro” means interacting with other apps, other facilities and other users. FCP X fails on those levels and I don’t see Apple changing that.

©2011 Oliver Peters

Apple Final Cut Pro X

Apple Final Cut Pro had been rocking along for twelve years, gaining professional market share and becoming a versatile platform for many editors, facilities and developers. But it was time for a change, especially after the 2009 update, which many editors felt was too incremental. Behind the scenes, Apple had been working on an entirely new version designed to take advantage of Apple’s modern operating system and hardware. After all, Final Cut Pro had evolved from the original Windows-based Key Grip application to a Mac OS 9-based Final Cut Pro, which then flourished under the transition to Mac OS X. With such a storied past, it was clear that a complete, from-the-ground-up rewrite was needed to modernize the code and feature set. In typical Apple fashion, this also offered the opportunity to re-imagine the inherent concepts of nonlinear editing.

In June, Apple rolled out Final Cut Pro X (10.0) as the successor to Final Cut Pro. Unlike the most recent versions of Final Cut Studio, Final Cut Pro X is no longer a suite of applications, but rather a single application, available only via download from the Apple App Store for $299.99. In addition, the updated Motion 5 and Compressor 4 applications are also available from the App Store for an additional $49.99 each.

In a move that has dismayed many loyal users, Apple removed the previous version, thus eliminating Final Cut Studio (Final Cut Pro, Color, DVD Studio Pro, Soundtrack Pro, Compressor, Cinema Tools and Motion), Final Cut Express and Final Cut Server. For now, Soundtrack Pro still exists as part of the Logic Studio bundle. Of course, previous video applications, like Shake and LiveType were eliminated several years ago. The bottom line is that the current Apple video family is focused on a smaller, but more cohesive video group that includes iMovie, Final Cut Pro X, Motion 5 and Compressor 4.

Built for speed

Final Cut Pro X has zero similarity with the previous Final Cut versions. It is a 64-bit application, which runs on the latest version of Mac OS X Snow Leopard (minimum 10.6.7 with ProKit 7.0) or Lion (10.7) and the whole range of recent Apple hardware. I did my testing on a 1 ½ year old 2.26GHz eight-core Mac Pro (Mac OS X 10.6.8) with 12GB of RAM and the ATI 5870 graphics card.

All of this optimization pays off in better support for larger formats, such as 4K-sized projects and native editing with H.264 files, like those from a Canon 5D. In my testing, FCP X was very responsive with all types of media with both rendered and unrendered effects. Real-time performance is generally maintained at all times with minimal instances of frames being dropped, compared to the “classic” versions of FCP. Since some of this performance boost is a due to how FCP X pre-loads media into RAM, the more memory you can install, the better performance you’ll enjoy.

I compared this against media performance in other NLEs, like Avid Media Composer or Adobe Premiere Pro. The playback and media scrubbing responsiveness with optimized media formats and accelerated effects was fairly similar in all three. FCP X performed well, but didn’t necessarily outshine the others at SD and HD frame sizes. Performance of 2K and 4K-sized ProRes files had a definite advantage with Final Cut and H.264 media handling seemed the best out of the three. The “wow” performance feature is Skimming, which is a technique of scrubbing media clips anywhere in the interface, simply by hovering over the clip and moving the mouse. No clicking required. In spite of these media improvements, some formats, like REDCODE raw, are not natively supported yet and AVC-Intra still requires a copy and rewrap into QuickTime MOV container.

Three big marquee features are Synchronization, Audition and the Precision Editor. Synchronization is designed to allow you to auto-sync clips by timecode, markers, in-points or audio content. This latter capability should allow you to match double-system sound from two sources to each other. For instance, a camera clip with camera audio to an externally recorded sound file. I tried this with some Canon 5D clips and Zoom H4N WAV files, which had previously synced well using FCP 7 and Singular Software’s PluralEyes. My initial test didn’t seem to work, but when I tried it again a day later it was fine. It’s quite possible that there was some background analysis required and that I hadn’t allowed enough time. In any case, on the second day it worked quite well for all of the clips I had tested. The result is a new Compound Clip marked as a Synchronized Clip, which contains the camera and audio clips. The camera audio can then be turned off in the Viewer’s inspector tab.

An Audition clip is a single, nested clip containing several different selected shots, such as alternate performance takes. Audition clips can be edited to the timeline and then you may select and preview any one of the shots from the Audition clip, without re-editing the other shots into the timeline. This feature is handy when working in client-supervised sessions, where you might quickly preview alternate clips in context without ever leaving the timeline.

The Precision Editor is a tool lifted from iMovie. Instead of the usual trim tools for rolling edits, the Precision Editor displays two adjacent clips on the timeline in an over-under filmstrip format. You can see the available media past the cut for the outgoing and incoming clip. For me, the standard ways of trimming are better – and they’ve been improved in FCP X over FCP 7 – but the Precision Editor does offer a method that mimics a film-style way of working.

The whole intent of this revamp is to keep the creative juices flowing without interruption. Performance is largely real-time and there are many background processes, like automatic analysis and rendering. There’s no Save or Auto-save function, because the application is continually updating its current status.

The user interface

The most obvious change is the user interface design. FCP X is built with single-display configurations in mind using a fixed layout; however, you can spread it across two screens. In a dual-display layout, either the Event Library/Browser or the Viewer can be moved to a second display, but you can no longer move floating, dockable windows and reconfigure the entire layout. FCP X sports a more pleasing, darker interface design, with updated icons like those in iMovie. It is intended as a full-screen application designed to hide other applications underneath – much like most Windows programs.

The previous version of Final Cut was built on the popular paradigm that stemmed from both film and linear editing, utilizing a source and record window (Viewer and Canvas), a timeline for edits and a set of folders or bins for source clips. This has been replaced by a single unified Viewer, which can display the timeline, as well as source clips. In addition, all source clips can be viewed as filmstrips that can be directly scrubbed or skimmed for edit selection.

New concept – the Events database

Changing the viewer would have been a minor change, but Apple also completely revamped how Final Cut Pro X deals with media. The past organization of Capture Scratch folders, FCP Project files and a Browser with master clips and sequences has been tossed out the window. Media is now organized as Events and stored on your designated hard drive in a Final Cut Events folder. An Event is a set of files that could represent a tape, a camera card, a day of shooting or some other definition.

When media is imported as a file or from tape into an Event, you have the option to create/transcode optimized (ProRes) or proxy (ProRes Proxy) media during this step. You can’t choose other ProRes codecs; however, existing files using ProRes HQ or ProRes 4444 will be copied as optimized media, but not transcoded. Or you can simply link to media in another folder on your hard drives. In the first process, the new media copies are stored in the corresponding Events folder. In the latter step, only an alias of that file is stored. During either of these steps metadata is created that’s associated with the files in the Events database. A number of items can be analyzed, including stabilization/rolling shutter issues, color balance, audio problems and shot identification. This analysis can be applied during import or after the fact, but it’s always a background process.

Although these background processes are cool, I did find them getting in the way at times. For instance, skimming was affected by background rendering. Often background processes are paused when you engage in work, since they are designed to utilize the machine’s idle time. I found it was better to turn off all automatic import analysis and then use individual functions, like color balance or stabilization on selected clips only when actually needed.

The entire method of clip organization is designed around a relational database. Events can be organized through the use of Keyword Collections and Smart Collections, which replace traditional bins. Rather than go through clips and manually move them into different bins, FCP X intends the editor to assign keywords and let the system handle the organization. This will permit one clip to appear in more than one collection based on context. For example, you could have one keyword collection for a specific scene and a second for all clips featuring a certain actor. All clips that matched these two criteria (scene and actor) would appear in both collections. Keywords can also be assigned to a range within a clip. Think of these tools as a replacement for subclipping.

One analysis feature is to have FCP X determine the shot type, based on People. The software will analyze a set of clips and create Smart Collections for One Person, Two People, Wide Shot, Medium Shot, etc. It’s a neat concept, but unfortunately, like most automatic analysis, I found it was frequently wrong. For instance, grouping a two-shot in the One Person collection and other such mistakes.

It’s important to realize that when you are working in the Event Browser in FCP X, you are actively working with the actual media and not merely clips that reference media. Therefore, changes you make can be destructive, like moving a clip to the trash. If one of these media files is altered by another application, it will become off-line within FCP X. This happened to me when I opened some of the files in Premiere Pro, which altered the embedded metadata. As a result, FCP X no longer saw these as the same files. There is no simple Reconnect Media process. Often an off-line media file can be removed from the browser and re-imported, but re-linking has become harder than in the past, as part of Apple’s effort to make FCP X media management rock-solid.

More new concepts – Projects and Storylines

Terminology gets a bit confusing with Final Cut Pro X if you try to equate it to other NLEs. Timelines in FCP 7 were referred to as Sequences and a Project file contained all the data, including master clips (not media) and edited sequences. In Final Cut Pro X there is no single file containing all the data associated with an editing job or session. Clip metadata has been broken out as part of the Events database. Projects contain the edit information and location of render files, but there is only one timeline per project. This becomes clear if you look at the library files on your hard drive, which are also broken out according to Events and Projects. If you typically create a lot of sequence copies as various versions of a cut, then that same task is achieved by duplicating a Project.

The biggest change for editors is that Apple has decided to redefine how we think of editing itself. They’ve dropped the video/audio track metaphor in favor of the concept of Storylines. It’s based on the way most narrative pieces are structured, where sound bites are edited together to tell the story. Then cutaway shots are built around these to enhance the visuals or hide edits made in the interviews.

In FCP 7, the sound bites would have been assembled as synced audio/video clips edited to V1 and A1/A2. Cutaway shots would be edited to V2 as video-only clips. In FCP X, the sound bites are assembled as combined audio/video clips to the Primary Storyline. Cutaway shots are edited as Connected Clips, which are attached to points on the Storyline and appear above it; however, vertical hierarchy isn’t really track-based. For example, an audio clip can be above a video clip in the timeline window, but in general, the visibility of a video clip works top-down, as before. If you need to build a series of cutaway clips as a group, complete with transitions, then these can be connected to each other as a secondary Storyline, which in turn is connected to the primary Storyline. Although this sounds confusing, Apple has essentially replaced the track metaphor with Storyline “lanes”.

A key aspect of this new approach is the Magnetic Timeline. This is a way of keeping clips together as you rearrange them on the timeline. By using combined A/V clips, together with connected clips, it’s possible to quickly change the order of a group of associated clips (audio, video and cutaways), simply by moving one of them. The rest will follow and the timeline opens or closes accordingly. Or if you trim a clip in the primary Storyline, the connected clips will ripple their position, as well. Auto-selection, locking tracks and clip collisions are gone, because conflicting audio or video elements will move up or down out the way to allow the change to be made. A group of clips can be “collapsed” or “nested” into a single timeline element called a Compound Clip, which can then be manipulated as a single unit.

Effects and color

There has been a huge change in effects with Final Cut Pro X. Current FCP 7 plug-ins won’t work until updated. FCP X effects are really Motion projects based on the new 64-bit FxPlug2 architecture. There are quite a few presets and the control parameters have been restricted to make it easier for new users.

If you really want more effects horsepower, then you will need to also purchase Motion 5. You can open a clip or an FCP X effect in Motion 5, but you can no longer “round trip” a timeline clip from FCP X to Motion 5 and back. There is no Send To Motion function. Although Motion 5 still works as an advanced, standalone compositor, it didn’t really get a huge performance boost. The user interface was rearranged, darkened and streamlined, but it seems to be intended as a developer’s tool to build effects and templates that can be used within FCP X.

In this scenario, a graphic designer might use Motion 5 to support a number of FCP X editors, who themselves might never touch Motion 5. The designer would use Motion 5 to create and/or modify effects and templates that would then appear within each user’s FCP X effects palette. This is enabled by the new Rig tool in Motion 5. A Rig is a mechanism to combine a set of adjustable parameters into a single control, like a slider or drop-down menu. Parameters are published – meaning that specific sliders are made visible and adjustable within FCP X.

Noise Industries had early access to the effects API and was able to release a free update of FxFactory compatible with FCP X and Motion 5, as well as the other supported hosts. Only the FxFactory Pro filters appear as effects, transitions and generators inside Final Cut Pro X. If you open Motion 5, you’ll see some of the other partners’ effects, like those from Idustrial Revolution, Luca Visual FX or DV Shade. These employ custom interfaces in their filter panels, which isn’t permitted in the new FCP X design. I presume this will also affect other popular effects filters, like Magic Bullet Colorista II. Nevertheless, having FxFactory inside FCP X gives the editor a much better palette than sticking with the built-in effects.

A lot has been made about ending Apple Color and whether or not those tools are in Final Cut Pro X. I’d have to say no they aren’t, although color correction is way more advanced than in FCP 7. Color correction and grading happens in three places – the automatic color balance and Color Match controls, as well as the Color Board. Automatic balance and Color Match work by changing information in the color profile of the image. Analysis is based on the section of the clip you use. Changes made are not visible in any of the color correction controls, though, which means you won’t really know what values have been changed. You can use the Color Board to correct a shot and then automatically match a different shot to that correction, however, the changes in the second shot will be made in the profile and not the controls.

The Color Board is where you perform subjective color grading and it’s the replacement for the older 3-way color corrector. There are three tabs for color (hue), saturation and exposure (lift/gamma/gain). Each tab features shadow, midrange, highlight and global controls. I personally find color wheels and curves to be faster and more intuitive, but Apple used this new design to conserve screen real estate. You can stack a series of corrections to create secondary adjustments, like adding vignettes or isolating a specific color through HSL keying.

The color adjustments for hue work in a similar way to the additive/subtractive toning used by DV Shade EasyLooks and also Adobe Lightroom. If you want more blue overall, simply move the global button in the color tab to the blue swatch and above the line (positive range). For less blue, then move it below the line (negative range) in the same region of the blue swatch. This subtracts blue from the overall image. Think of it more as painting with color, rather than shifting color balance.

I was generally happy with the quality of the correction I could achieve, although I found the color (hue) controls to be a bit coarse, as compared with traditional hue offset controls (color wheels). Unfortunately, there’s no true color grading workflow for easy scene-to-scene grading, as you have in Color. There is no word whether the FCP X Color Board interface will eventually be compatible with the various third-party control surfaces, like Avid Artist Color or Tangent Devices Wave.

How to get in and out of FCP X

Apple is clear that it has designed an NLE from the ground up for the file-based world, so tape support is gone, with the exception of legacy support for FireWire-based cameras and decks. Even there, the control is limited to a “capture now” approach without extensive logging. The slack will be taken up by utilities offered by the i/o hardware makers, like AJA, Blackmagic Design, Matrox, MOTU and Telestream. And yes, they have utilities to capture to QuickTime and lay off to tape independent of FCP X or FCP 7. These will be enhanced to work in tandem with FCP X.

Currently FCP X can only be displayed to a broadcast video monitor as a full screen desktop image. Using the ability of a card like AJA’s Kona 3G to mirror a Mac desktop display, FCP X can be monitored as preview quality only. That’s generally fine for editing, but you can’t output to tape that way. You’ll need to export a self-contained QuickTime file and then use a utility to edit it to tape.

With the loss of DVD Studio Pro, Final Cut Pro X and Compressor 4 retain only basic DVD and Blu-ray capabilities. You can encode and burn a disc from the FCP X Share Menu or Compressor, but in either case, these are only intended for simple discs without advanced authoring features. I presume Apple feels that’s a dead-end business and if you needed those functions, you would already own the previous version of Final Cut Studio. (You can continue to use your existing installation of DVD Studio Pro, of course.) Naturally, presets for mobile devices and various online destinations have been expanded. Compressor itself didn’t get much of an overhaul, but did gain support for TIFF and Open EXR image sequences. Apple Qmaster controls are now built into the top menu.

The biggest i/o issue that has troubled users is the lack of project compatibility – especially the fact that you cannot import an existing FCP 7 project. There was a nice ecosystem of developers than grew up around XML, EDL, OMF and other open format support offered by previous versions of Final Cut. In this initial version, FCP X cannot import or export any type of sequence or project format, except bringing in an iMovie project. Apple says that the data formats of FCP 7 and FCP X are so different that a lot of the information would be lost in the translation. That’s of little consolation to FCP editors who routinely have to revisit past projects. Although a third-party translation solution might arise in the coming months, Apple has given no clear indication whether they would supply a built-in solution nor whether they’d offer it as a free update.

Many professional editors have to interchange projects with other studios and facilities. For example, even with local market TV spots, I often send files to one of the audio studios in town, because that’s who the agencies want to work with for their mix. OMF has been the standard interchange file for both Pro Tools and Logic, as well as many other DAWs. OMF export was there in FCP 7 and gone in FCP X. There is also no Send to Soundtrack Pro or Send To Logic feature in FCP X. In short, there is simply no way to send audio clips with track assignments and edit points from Final Cut Pro X to any audio editing application.

Fortunately, Apple allowed Automatic Duck into the process early enough to support FCP X with the simultaneous release of Pro Export FCP 5.0. This is a standalone application rather than a plug-in. Simply launch Pro Export and drag the FCP X project from the project browser window to the Automatic Duck window and it will generate either an AAF or OMF file. I tested an OMF export and timeline and associated audio files opened just fine in Adobe’s Audition, but ironically not in Apple’s own Soundtrack Pro.

Wrapping it up

Final Cut Pro X is very different and it takes a while to get used to it. I’ve been beating on the evaluation software provided by Apple for about two weeks as I write this review, along with a few hours worth of press briefings from Apple staff. I’ve also conferred with probably a dozen colleagues who are also trying to shake it out, including a number of experienced feature film editors. Without a doubt, it’s definitely worth tapping into some of the various training materials if you want to use Final Cut Pro X to its fullest. The manual (available as online Help or a downloadable 395-page PDF) covers a lot, but I’ve already hit a number of undocumented features and I’m sure there are many more.

At the end of the day, this is still a developing product that isn’t ideal for every high-end situation where FCP 7 has succeeded. FCP X is a tool intended to be easier to use by people who aren’t necessarily full-time editors – meaning event videographers, video journalists, producer/directors who occasionally edit and corporate presentation professionals. These are users who may not exclusively edit for a living, but expect professional results that can’t be achieved with iMovie. Apple has focused on an architectural design for the coming decade with an eye towards people who are just starting out as video professionals and will grow with the product.

The sweet spot today for Final Cut Pro X is a production that is file-based and can be completely started and finished within FCP X without the need for interchange with other applications. According to Apple, the App Store online distribution method now allows them to offer updates more quickly than before. They have promised to address a number of the most-requested features within weeks and months, rather than years.

The current version is quite stable for a 1.0 product. If you can deal with the limitations and are dying to see whether Apple’s re-imagining of nonlinear editing is a better way for you to tell the story, then Final Cut Pro X might be right for you. But if you are a professional user with established, advanced workflows, it will likely be a frustrating experience in that scenario. FCP X is ready for prime time now, although Prime Time might not be ready for it!

Written for DV and Videography magazines (NewBay Media LLC)

©2011 Oliver Peters