By Amy Leland
There exists within the post world a deep schism. On one side are those who use Final Cut Pro X, appreciate it for what it is, and want to know more about it. On the other side are those who see it as “iMovie Pro” and disdain all discussion on the topic. Full disclosure: I have always fallen firmly in the first camp.
When FCPX was first released in June of 2011, besides being a professional editor, I was also an Apple Certified Trainer (in FCP, Motion and Color), and out of necessity figured out this new product as quickly as possible to meet the demand of those wanting to know more. Along the way, I positioned it in my own work as my go-to tool for any of my independent freelance projects, and most recently for the feature documentary that I am directing and editing. I recognize that it isn’t the right tool for all editing jobs. But sometimes it is the best tool for an editing job.
Last week I had the opportunity to attend a demo of the new FCPX 10.3. For those who are using it and others who have an open mind, there are some exciting new features and updates. I don’t think anything I say will sway the minds of those who decided long ago this product isn’t for professional editors and isn’t worth their time. And for those whose hesitation was, it’s too different, well it’s still different. It’s just a new different.
The thing that really stuck out to me was the streamlining of how audio works. There are both interface and under-the-covers changes to audio mixing and organization. The big news is the use of Roles, and how that applies to audio. FCPX introduced the idea of Roles in the very first update to the app just a few months after the initial release. Roles allowed for identifying types of audio in a way that would aid in multichannel exports and stems. But this version is the first to fully take advantage of them for streamlining the editing process.
There is now more comprehensive support for doing things like color-coding clips based on Roles for visual cues in the timeline. There is also a new concept called “audio lanes.” This is still the world of the magnetic timeline. I am a fan of the magnetic timeline, and that functionality is the biggest reason why my workflow in FCPX is typically far faster than it is in any other app. But it has always been a bit frustrating to get the audio beneath the magnetic timeline to make sense visually. Now, with audio lanes, audio in different roles can be displayed in distinct visual troughs (NOT tracks) that make it far easier to look at the timeline and see exactly what is there. With a single click, lanes can be turned off and on. The flexibility for display in different stages of the work process is fantastic.
The interface as a whole has also undergone the biggest overhaul it has had since the initial release. It looks, quite simply, cleaner. The color scheme has been flattened and darkened to allow the video content to take focus. Some onscreen controls have been moved to places that, upon reflection, do make more sense. Though having used the product for five years, I expect to have some moments of feeling a little disoriented while I get used to the changes. I look forward to seeing how the adjustments further streamline the process.
One change I am particularly excited about might seem like a small thing, but it will save me one of the biggest headaches I tend to experience in my FCPX work. I’m a big fan of custom Motion content. I create my own custom titles, transitions and effects for almost every project I do. I also use Motion publishing to bring effects specific to Motion into the FCPX interface. The only problem is that, up until now, all of that custom content lived in the Movies folder of the user library in the OS. There was no option to customize that location or store things elsewhere. More times than I can count, I would move a project from one hard drive to another, or consolidate a project to a portable drive to work on while traveling, and discover I’d left my custom Motion content behind. Those offline media icons made me nuts.
In 10.3, there is now a user preference for storing those custom Motion projects inside of an FCPX library. If the Motion project is specific to a particular FCPX project, I can store it in that project’s library. For things I have created to be more universal, I can now create a central library that can travel with any of the other work I’m doing. It’s a small change, but a really important one.
Many of the other changes, while relatively small details, are important ones. After years of user requests, we finally have selective “Remove Attributes.” (FINALLY!) FCPX will now also natively accept MXF-wrapped ProRes files. For those of us who go back and forth between editing systems, and do a lot of work in Avid, this will be a real time saver.
There is also a new effect in the FCPX effect library called “Flow,” a transition similar to the Fluid Morph in Avid or the Morph Cut in Premiere. I have to say, as I often experience with effects in FCPX and Motion, it just works…better. Unlike Avid where I often have to finesse the frame count to get it to work right, and then render before playback, this just drops in and works. I love it.
And finally, for those whose biggest hang-up about FCPX is shared media/project use, there is now support for shared libraries on SMB 3-compatible storage systems. There is also a new white paper out from Apple about managing the media and libraries that includes workflows for a shared storage environment. This is an aspect of the update I haven’t had the time to test fully myself. But the workflow outline in the white paper makes sense. It isn’t a fully shared work environment like opening bins from other projects in Avid. It seems more analogous to the Media Browser in Premiere, but this seems to have the potential to open up the idea of collaboration much better than before, and is something that I find pretty exciting. The “In Action” section of the FCPX website profiles a commercial post house in London called Trim Editing that is using this workflow. I imagine this won’t be enough to convince all of the skeptics. But it definitely feels like a big step in the right direction, and I look forward to working this way myself.
This is definitely a major update to an editing tool that was already more robust than it often gets credit for being. Those who are already on board should see a lot of good things here to reward their continued usage. Best of all, by releasing this major update as 10.3, and not as a new version 11, this update is a free one for anyone who already owns the app. That may be the best news of all.
Amy Leland is a filmmaker and editor in Brooklyn, New York, whose editing credits include Bravo, NFL Network and CBS Sports Network. She can be found on Twitter @amy_leland and on Instagram @la_directora.