Why Should Final Cut Pro 7 Editors Consider Final Cut Pro X?

Posted on by Larry

Passions run high when we talk about the software upon which we base our business. Last week, I wrote an article examining why Final Cut Pro 7 editors should consider Adobe Premiere Pro CC. (Read it here.) I was fascinated by all the comments.

This week, I want to take the same approach and look at Final Cut Pro X.


Final Cut Pro 7 was released July 23, 2009, along with the rest of the Final Cut Studio (3) suite. FCP 7 was last updated in late 2010 to version 7.0.3. Since that time, a lot of technology has changed. Final Cut Pro 7 has not.

Final Cut Pro 7 was never designed for today’s operating systems. While it still runs on OS X 10.9 (Mavericks), many of its plug-ins do not. And no one expects FCP 7 to run on all future OS updates. This means that current FCP 7 editors are forced to make a choice:

  1. Keep running the software on current hardware, stop upgrading the operating system and don’t buy any new hardware.
  2. Migrate their projects to a different editing system and learn something new.

If you are in the middle of a big FCP 7 project using hardware and software that is working fine, then don’t switch. Finish the project. Worry about what to do only after the project is complete.

But, if you are ready to move on, this article can help you decide what to do.


Before we compare FCP X to FCP 7, I need to clear the air on three points that keep reappearing in my email.

1. “If I wait a bit longer, will Apple bring back Final Cut Pro 7?” No. Final Cut Pro 7 has run its course. Development is stopped. It is not coming back. Put a fork in it, its done.

2. “Apple made me really angry when FCP X was launched.” True, the launch was not one of Apple’s best. In fact, the initial release of FCP X was widely criticized. But don’t let the launch blind you to what Final Cut Pro X has become:

3. “Apple took the easy way out by creating iMovie Pro.” If Apple wanted to take the easy way out, it would have added a couple of small features to FCP 7, incremented the version number and called it a day. There are dozens of Apple staffers working on Final Cut Pro X every day – an investment of millions of dollars a year. Nobody does that for a “throw-away” product.

If you enjoy being angry at Apple, fine. But, if you enjoy getting work done on-time and on-budget, then you have some very interesting options.

NOTE: I just discovered that there is a Final Cut Pro X Ecosystem page in the Mac App Store. Take a look.


Back in the 1980’s I wrote business-grade software. It wasn’t great, but it put one of my kids through college. I learned then that good software represents a way of thinking; a philosophy about how a task should be done.

Final Cut Pro 7 and Final Cut Pro X are good examples of this. FCP 7 is built on the philosophy of “how editing has always been done.” Starting with editing between two rolls of film, morphing into multiple tape decks and expanding into the digital world. This is a solid, traditional, totally understandable point of view.

Final Cut Pro X took a different approach. Apple started by asking: “What does editing look like in an all-digital world?” Then followed by asking: “What do editors who grew up in the world of computers and digital media expect?” Final Cut Pro X grew out of exploring the answers to those questions.

This resulted in major changes to media management, the interface, and the process of editing. Apple’s view is that modern, digital video editing software should take advantage of the huge amounts of metadata available from cameras and audio devices and the power of computers to help users tag, filter, and sort media in ways they never could before.

Media management has become more robust, more flexible and supports far more devices than FCP 7. Apple has continued to refine this as FCP X continues to evolve.

And thinking of the interface – another major change – it shifted from a light-gray background to a dark-gray background; similar to iMovie… and DaVinci Resolve, Autodesk Smoke and Photoshop. Dark gray makes colors easier to see.


Every week, I build a one-hour show using Final Cut Pro 7. It’s a template I created five years ago for my podcast: Digital Production Buzz. It takes me ten minutes to update the sequence template; then an hour and a half to render and export the master file. To make it go faster, I make sure nothing else is running on the computer during the export. In fact, I have dedicated an older Mac Pro running OS X 10.6.8 just for this one weekly project.

NOTE: Final Cut Pro 7 only effectively used 1 processor and, with just a few exceptions didn’t support the GPU at all. Also, because it was only 32-bit enabled, FCP 7 would only access 4 GB of RAM, regardless of how much RAM was installed on your system.

Because FCP 7 was so slow, Final Cut Pro X is all about speed – blinding speed – and moving as much work to the background as possible so you can be doing creative work without waiting for something to finish.

Final Cut Pro X has a modern architecture built to take advantage of multiple CPUs, multiple cores, multiple GPUs and its support for 64-bit memory addressing means that FCP X can use all the RAM you can give it.

While FCP X is highly optimized for the new Mac Pro, including dual-GPU support throughout the graphics pipeline for real-time effects playback, rendering, video monitoring, and Optical Flow analysis, it also runs extremely well on all current MacBook Pros and iMacs.

One thing that continues to surprise me about the app is how fluid it is. I can be playing a sequence, while opening and closing other windows, zooming into and around the Timeline, all without dropping a frame on playback. It is enormously responsive; even on a two-year-old iMac.

To give you an idea of how cool this is, you can be importing clips, exporting a project, rendering effects and editing – all at the same time; even on an iMac.


Feeding the need for speed is most evident in the Timeline. Probably the biggest feature is the “Magnetic Timeline.” This replaces the concept of tracks (like FCP 7) with layers (like Photoshop). It also means that clips edited to the Timeline are “attracted” to each other; preventing unwanted gaps or one clip accidentally overwriting another. While this takes a bit to get used to, it totally removes the worry about where the playhead is positioned when editing clips to the Timeline.

I find editing using the Magnetic Timeline is amazingly fast. And, when you need a clip to move to a specific spot, the Position tool overrides the “magnetic” part of the Timeline so you can precisely position a clip.

Apple redefined “state-of-the-art” when it released multicam editing in FCP 5. Final Cut Pro X takes multicam editing to an entirely higher level. FCP 7 doesn’t even come close.

A new feature, called the “Timeline Index,” provides a fast way to see, search, jump to, or filter all clips, markers, roles and tags in the active project. It offers faster and more flexible find and selection features than Find in FCP 7. I also use the Timeline Index to quickly review all chapter markers in a project for the correct spelling.

Nests in FCP 7 have become compound clips in FCP X. Roles, which are new, allow us to tag video and audio elements to control what gets displayed or exported. (Think of creating a single project containing both English and Spanish voice-overs and titles. We can change a Role setting and export two files from the same project the same time: one English and one Spanish.)

NOTE: While FCP 7 allows multiple sequences to be displayed in the Timeline at one time, FCP X only allows one sequence (called a “project”) open in the Timeline at a time. However, you can quickly jump from one sequence to another using the Browser.


The database FCP X uses for tracking media allows more and better clip metadata, and better file organization.

Skimming allows us to review the audio or video contents of a clip, without first opening it in the Viewer. Skimming makes browsing clips far faster and easier than FCP 7.

Scratch disks have morphed. Now, we have Libraries. These are master “containers” which are similar to FCP 7’s project files. Libraries hold everything we work on during a project: media, work files and edits (called “sequences” in FCP 7, “projects” in FCP X). Libraries can either store media (“Managed Media”) or point to media stored in external folders (“External Media.”) The ability to consolidate media all in one place makes copying, moving, sharing, managing and archiving a lot easier. Media can be stored anywhere and that storage location can vary by project. (Storing media by project was a major hassle in FCP 7.)

And, like FCP 7, we can open multiple Libraries at the same time and work with media or projects stored in any open Library. Libraries can be opened or closed whenever we want.

Imported media can be organized by folder (Event), rating or keyword. (FCP 7 only supported organization by folder.) While keyword management is awkward when more than 30 keywords are used in a project, search speeds using rating or keywords are virtually instant.

Creating high-quality optimized (edit master) and proxy files can be done automatically on import. Rendering and transcoding run in the background and is optimized for ProRes 422 and ProRes 422 Proxy.

NOTE: An interesting behind-the-scenes feature is that media that is shared between FCP X, Compressor and/or Motion is ColorSync-managed during rendering.

Switching between original and proxy files in FCP 7 took 17 separate steps. (I know because the article I wrote explaining how to do it was my most popular article for almost 18 months.) Now, switching between camera native and proxy media is a radio button and the media switches instantly.

Final Cut Pro X provides native, real-time support for professional video codecs like ProRes 4444 XQ and Sony XAVC along with more common codecs such as H.264 and AVCHD. In fact, FCP X fully supports the entire ProRes family throughout import, editing, rendering, and export.

NOTE: For a full-list of FCP X supported cameras and codecs click here.


Waveform display in the Timeline is bigger, more accurate and more adjustable. We can also display reference waveforms, which are a “ghosted” image of what the audio would look like if it were normalized.

Audio elements of synced clips are no longer separate clips. It is impossible to accidentally knock audio out of sync. Working with multichannel audio is just as flexible as FCP 7, without the risk of knocking clips out of sync. Double-system audio can be synced automatically based on matching waveforms.

Audio fade transitions have been replaced by adjustable fade “dots,” with the ability to change the shape of the fade.

And all the great Logic/Soundtrack Pro plug-ins migrated to the latest version of Final Cut, with the ability to adjust the plug-in directly in its own interface within FCP X.

NOTE: FCP X also provides a variety of audio repair tools, though, truthfully, if I have problem audio, I’m moving it to Adobe Audition for repair and mixing. On the other hand, for audio newbies, the audio repair features in FCP X are easy to use.


Like FCP 7, FCP X enjoys massive support from a wide variety of 3rd-party developers, including all the companies you used in FCP 7. Plus, there are new effects and utilities that exceed what we could do in Final Cut 7.

The chroma-keyer in FCP 7 was a dog. Beyond useless; and I’m trying to be kind. The chroma-keyer in FCP X is amazing. The default settings create stunning keys.

Final Cut Pro X uses Motion as its graphics engine. In fact, all effects in FCP X are actually Motion projects saved in such a fashion that Final Cut can access them. Like FCP 7, we can create animated titles in Motion which can be opened in FCP X, retaining all animation, but allowing customized text and text formatting. But the integration of Motion with FCP X is much more extensive than in FCP 7. You can customize any parameter in a Motion template, then export those controls directly into Final Cut to create modifiable effects from a Motion template inside Final Cut.

Aside from the confusing decision to redesign the color wheel as a rectangle, which I find totally unintuitive and awkward, the color correction in FCP X is better:

Apple has also improved the display of all the video scopes, though I miss the small line for measuring specific values and percentage indicators on the Vectorscope.

NOTE: For truly powerful color correction, DaVinci Resolve imports FCP X XML files easily with a single mouse-click, without having to prep files for color grading.


To move projects from Final Cut 7 to Final Cut Pro X requires a separate, and very inexpensive, utility – 7toX from Intelligent Assistance – and three steps:

When transferring files using XML, all media and edits transfer perfectly. Dissolves and audio levels generally transfer fine. However, effects, titles, and color correction will not transfer properly.

NOTE: Because XML is required to move projects from FCP 7 to FCP X, it is critical that you export to XML any FCP 7 projects that you might want to transfer in the future. Without an XML version, or a working copy of FCP 7, you won’t be able to move any old projects to FCP X. (Or Premiere Pro or Avid, for that matter. All these apps require XML to transfer FCP 7 projects.)


Change is scary. Change which has the potential to affect our business is terrifying. But we live in an industry based on technology. Change is inevitable. The key is to accept that change is as part of life, plan for change, and keep learning so that when changes come, we are ready.

We won’t be able to stay with the past much longer. FCP X is fast. It is fluid. And it handles the technology so we can concentrate on editing.

As always, let me know what you think.


18 Responses to Why Should Final Cut Pro 7 Editors Consider Final Cut Pro X?

Newer Comments →
  1. Guido says:

    I think for people set in their ways, with countless hours on FCP 7 (and earlier), Premiere might feel more like what you’re used to but with the power you need for modern projects.

    For newcomers not used to ye olde ways of editing, FCP X is faster and more intuitive.

    It’s great to have a choice. Personally, I started with Premiere, found it cumbersome, switched to FCP X and definitely preferred it for its fluidity and speed. Everyone will have to make up their own mind, of course, but my money is on FCP X

  2. Leo Hans says:

    IMHO when you think that you are going to spend thousands of days editing in an NLE, spending a couple of weeks transitioning is not a waste of time. In this regard, I prefer to spend the time learning a new app (FCPX) than goint to an app that mimics FCP7 way of working.

    In every project that I have edited with FCPX the producers and the directors were surprised (I mean, pleased) with the speed and the results.

  3. Jason L. says:

    Frankly the older NLEs just are not built for today’s world of editing. Some things, sure I find myself going back to using my legacy apps, but for the most part I just don’t look back.

    I was there at the Supermeet in Vegas when Apple was the star of the show with their announcement of FCPX, and personally I was inspired, impressed, and blown away with awe of what we had to look forward to be using next to finally fix the headaches with dealing with the memory card media – the digital file in our, then-current NLE, FCP7. I don’t know what the rest of the nay-sayers were on or smoking that night, but I saw nothing but pure editorial Jazz on that screen!! I know I heard plenty of cheers and “Hell Yeah!”s shouted-out from the audience. And I know that when I looked back at the back of the room, I saw AVID, Adobe, Autodesk, etc. Reps’ jaws dropping and fear just taking over at what Apple just accomplished! Faced with the ultimate competition, they took the best marketing tactic available to combat it, and slandered Apple on the accusation that they didn’t care about the serious editor, thus starting this sectarian war between self-declared classes of editors out in the world, mainly Hollywood Editors V.S. the Freelancer or Independent Editor.

    BS all the like! We are Freelancers/Independents are not Hobbyists like the Screen Editors community would prefer to believe. Now that we are living in such a connected world with video making the majority of online content, the Cinema Screen only makes a small fraction of the content created in this world! The rest of us are creating content most likely to be seen out there as it is readily available at little or no cost to the viewer.

    Anyone who looks away from a great tool that makes it easier to make a living at doing what you love, they should really have their head examined!

    Thank you Larry for sticking with FCPX despite the controversy around it! I really enjoy your tips, tricks, insight, and guidance in he Post process.

  4. Seigo says:

    If you insist on fcpx does not like pro, think about about your money raise rest of couple of years as a pro?
    That means game changes a lot.

  5. Bob Dey says:

    Thanks.Yoru view is pretty helpful. I’m going for X. No venture no adventure

  6. Pierre says:

    Thank you for this very helpful article. One question: if I try the free trial of FCX on my machine that had FCP7 on it but decide it’s not for me, will I be able to go back to FCP7?

    • Larry says:


      Yes. When FCP X is installed, it moves all your FCP 7 applications into a folder named “Final Cut Studio.” You can run both FCP X and FCP 7 on the same machine, just not at the same time.


  7. Mario says:

    In FCP 7 we had “Color” a plug in within the FCS package. For FXP X, the equivalent or simil might be the “Da Vinci Resolve”? The color correction tool of FCP X is not enough? Isn’t there another Color plug in to work with FCP X in a roundtrip, natively, WITHOUT the need of passing by the XML conversions?
    Thx a lot.

    • Larry says:


      Many of the Color functions moved into FCP X. However, for an excellent color plug-in that works inside FCP X without needing an XML round-trip, check into Color Finesse.


  8. Kristy says:

    Hi sir thanks a lot for such helpfull information..
    I want to edit my feature film shooted in 5d Mark 3 in FCPX..
    My import format is 1920*1080 24 frames..
    And export in h264..
    My doubt is this export and import formats are sufficient for giving 4k resolution in 70mm screen..
    And in fcp10 is there any quality supression after export..?
    Is FCP X is usefull for feature film editing..!

    • Larry says:


      FCP X is totally appropriate for feature film editing.

      But you are not doing yourself any favors using these codecs. 70mm is projected to GIANT screens, you need to shoot, edit and output much higher quality codecs. Your Canon is shooting an HD image using H.264. You need to shoot a 4K image, not HD. Also, you would be MUCH better off recording the output of your Canon to an external digital video recorder – such as AJA, Blackmagic Design or Atoms – as a RAW image, rather than the deeply compressed H.264 the Canon records internally.

      Then, edit either camera native (RAW) or optimize to ProRes 422 for editing. Export using ProRes or, for best quality, export an XML file and conform back to the original RAW format shot by your camera.

      In all cases, given your goal of projecting to large screen, H.264 should be avoided.


  9. S Marchant says:

    Is there a good way of getting audio to protools? (or Sequoia?)

  10. Oyikk | says:

    […] yang kamu tidak bisa hidup tanpanya … Final Cut […]

Newer Comments →

Leave a Reply

Your email address will not be published. Required fields are marked *

Larry Recommends:

FCPX 10.5 Complete

NEW & Updated!

Edit smarter with Larry’s latest training, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!


Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.