Making FCP X Work For You

df_fcpx4u_1_sm

Final Cut Pro X is steadily gaining numbers among professional editors as Apple integrates more features in response to users’ needs. Unlike the previous iterations of Final Cut Studio – where everything was integrated into a bundle of Apple applications – FCP X relies more on an ecosystem of outside developers who have brought a number of useful tools to the table. This means that you only buy what you need and fill your toolkit according to your own specific workflow. Here are some tips on getting the most out of the FCP X. (Click on images for an expanded view.)

Motion and Compressor

df_fcpx4u_18_smApple sells Motion 5 and Compressor 4 as standalone applications through the Mac App Store. Although not essential for running FCP X, each adds useful functions. Motion 5 is an advanced compositor that’s optimized for the design and animation of motion graphics. It also has become an effects creation tool for Final Cut Pro X. Many of the filters, transitions and generators found in FCP X are actually Motion templates. It’s easy to open a copy of an effect from FCP X into Motion and customize it. Likewise, you can create you own effects plug-ins from scratch and “publish” them back to Final Cut. Many of the free or low-cost filters available for FCP X were created exactly this way.

Compressor 4 is an updated version of Apple’s encoding software. This new version is faster and better optimized for current hardware and includes new presets for Apple devices. Since DVD and Blu-ray creation has been integrated into the FCP X Share menu, as well as Compressor, this will be the tool you need for separate production of “one-off” review discs.

Moving between the Final Cuts

df_fcpx4u_6_smFinal Cut Pro X introduced a new version of XML, which differs greatly from the XML used by Final Cut Pro 7 or Adobe Premiere Pro. Yet, this the core method Apple provides for interchange with other applications. If you need AAFs, OMFs, FCP 7 XMLs, EDLs and so on, you first have to go through the new FCPXML format. To date, only a handful of applications, like DaVinci Resolve, can natively read/write FCPXML; therefore, general interoperability will require one of several third-party translation utilities.df_fcpx4u_3_sm

Intelligent Assistance/Assisted Editing jumped into the game early with applications designed to make FCP X a better citizen of the post world. Xto7 for Final Cut Pro and 7toX for Final Cut Pro are XML translation utilities that let editors bring legacy FCP projects into FCP X, as well as to go from FCP X back to FCP 7 (or Premiere Pro). Although the need for 7toX seems obvious, going in the other direction (Xto7) is also quite useful. For instance, it’s the only efficient way to create an audio OMF from an FCP X project. Use the translation to get the timeline into FCP 7, where you can generate the OMF export. This is also a good way to get from FCP X to Apple Color, if that’s still your preferred grading application.

Other applications for FCP X from Intelligent Assistance include Sync-N-Link X. It is designed to batch-process double-system audio synchronizing based on timecode. Lastly Event Manager X is a tool for editors to control which Events and Projects show up inside Final Cut Pro X at launch.

df_fcpx4u_2_sm

Interoperability with other applications

df_fcpx4u_7_smApple left EDL generation to third-party developers. XMiL Workflow Tools’ EDL-X is the application to use if you need to generate CMX 3600-compliant edit decision lists (EDLs). This is still an important need in many industry workflows, such as sending files and a sequence to an outside color correction or visual effects facility. EDL-X gives you control over customizing lists based on the needs at the other end. This includes length of reel names, which data is used for the reel names and the inclusion of source lists.

df_fcpx4u_5_smFinal Cut Pro X uses a trackless timeline design, which doesn’t translate to a layout required by audio mixers working on a DAW, like Avid Pro Tools. The software designed to translate an FCP X Project (edited sequence) for Pro Tools use is Marquis Broadcast’s X2Pro Audio Convert. It reads the FCPXML file and generates an AAF file with linked or embedded media. This is compatible with newer versions of Pro Tools. In addition, the FCP X Roles and Sub-roles feature is used to organize the track layout when the file is opened in a Pro Tools session.

df_fcpx4u_17_smWhat if you want to mix the audio yourself, but don’t own Pro Tools? There’s another option. Assuming that Soundtrack Pro is installed on your computer (part of the “legacy” Final Cut Studio) or you’ve purchased Adobe Production Premium CS6, which includes Audition, then you can also use Xto7 to translate your timeline’s audio into XML. Import the translated XML list into one of these DAW applications, which will automatically link to the audio files on your hard drives. Now you can mix the audio in a familiar track-based environment.

df_fcpx4u_8_smIf you’ve left Apple Color behind, then Blackmagic Design DaVinci Resolve is tailor-made for Final Cut Pro X. The roundtrip between the two applications is solid and even their user interfaces sport similar aesthetics. Resolve is a world class grading tool used on blockbuster features, but even the free version will cover nearly all of your needs. Another interesting free (donation requested) application is ClipExporter from Mind Transplant. df_fcpx4u_15_smThis translation utility can generate composition files for SynthEyes, Nuke and After Effects from FCP X timelines, as well as self-contained or reference QuickTime movies from individual Event clips.

df_fcpx4u_16_smTwo more applications that will add powerful capabilities to your system are Red Giant Software’s PluralEyes 3 and Soundbite from Boris FX. PluralEyes 3 is a standalone application for clip synchronization using audio. It can sync double-system productions, as well as multiple camera angles based on matching audio waveforms, without the use of timecode. This new version supports the FCPXML format, as well as roundtrips to and from FCP X.

df_fcpx4u_9_smSoundbite is a dialogue search engine powered by Nexidia and used to be known as Get before Boris FX picked up the product. It’s the cousin of Avid’s PhraseFind, but operates outside of any specific NLE. To use it with FCP X, first analyze a folder of media to search for specific words, phrases or terms. Markers are placed at the word matches within the “found” clips. Then generate an FCPXML file for these search results, which will be imported into Final Cut as a new Event, complete with markers placed at the locations of the word matches.

Finally, let’s not for get the useful workflow and maintenance/system management tools from Digital Rebellion, like Preference Manager and Pro Versioner.

Filters, transitions, titles, generators and templates

df_fcpx4u_11_smVideo effects in Final Cut Pro X are based on Motion templates built on an updated version of the FxPlug architecture. Many of the effects created for FCP X by third-party developers are simply a combination of native Motion effects, which have been “published” as a single FCP X effect. In this process, the developer can choose to limit or reveal as many adjustment sliders as is appropriate. Therefore, a very complex effect can be controlled with a single slider within the FCP X inspector pane. Some plug-in developers go beyond that, of course, but the combination of the traditional developers and the new crop of editor-designer-entrepreneurs has led to a rich ecosystem of effects just for FCP X.

df_fcpx4u_10_smAll of the major developers have introduced FCP X products. These include Boris FX, Coremelt, GenArts, Red Giant, Tiffen, Digital Film Tools, RE:Vision, DigiEffects, CHV and many more. I find those from Noise Industries and Digital Heaven to be the best match for most users. Digital Heaven’s Transitions Pack, BoxX, ReincarnationX and SubtitleX effects form a nice combination of tools that you’ll use every day. Not overly flashy, but very useful.

df_fcpx4u_14_smNoise Industries’ FxFactory is the only comprehensive package that you can grow as your need increases. The free version acts as a license manager for the partner plug-ins, while the paid Pro version adds a set of Noise Industries’ own filters. Most of these plug-ins run in FCP 7/X, After Effects and Premiere Pro, although a few are specific to only FCP X.df_fcpx4u_13_sm Since these plug-ins are developed by individual partner companies, like Nattress, LucaVFX, idustrial revolution, PHYX and others, you can buy the filters as you need them and grow the repertoire over time.

Final Cut Pro X naturally includes a nice complement of built-in filters, so before you started draining the bank account, you should definitely check out what’s already included. If you want freebees based on Motion templates, simply scour the web for a plethora of effects. FCP.co’s free plug-ins forum and the Alex4D filters are a good starting point. FCP X also includes a wide range of audio filters brought over from Logic. It also recognizes most third-party AU (Mac audio units) filters, like Focusrite or Waves plug-ins.

df_fcpx4u_12_smApple Final Cut Pro X is proving to be a viable platform for the professional user. You’ll find a range of tools that augment FCP X, which will enable you to complete productions at nearly any level of complexity. The supporting ecosystem of applications, utilities and plug-ins is growing every day and quickly expanding this next generation Final Cut Pro beyond it seemingly simple beginning.

Originally written for DV magazine / Creative Planet Network

©2013 Oliver Peters

NAB 2013 Distilled

df_nab2013_1Another year – another NAB exhibition. A lot of fun stuff to see. Plenty of innovation and advances, but no single “shocker” like last year’s introduction of the Blackmagic Cinema Camera. Here are some observations based on this past week in Las Vegas.

4K

Yes, 4K was all over. I was a bit surprised that many of the pieces for a complete end-to-end solution are in place. The term 4K refers to the horizontal pixel width of the image, but two common specs are used – the DCI (film) standard of 4096 and the UltraHD (aka QuadHD) standard of 3840. Both are “4K”. Forgotten in the discussion is frame rate. Many displays were showing higher frame rates, such as 4K at 60fps. 120fps is also being discussed.

4K (and higher) cameras were there from Canon, Sony, RED, JVC, GoPro and now Blackmagic Design. Stereo3D was there, too, in pockets; but, it’s all but dead (again). 4K, though, will have legs. The TV sets and distribution methods are coming into position and this is a nonintrusive experience for the viewer. SD to HD was an obvious “in your face” difference. 4K is noticeably better, but not as much as SD to HD. More like 720p versus 1080p. This means that consumer prices will have to continue to drop (as they will) for 4K to really catch hold, except for special venue applications. Right now, it’s pretty obvious how gorgeous 4K is when standing a few feet away from an 84” screen, but few folks can afford that yet.

Interestingly enough, you can even do live 4K broadcasts, using 4K cameras and production products from Astro Designs. This will have value in live venues like sporting events and large corporate meetings. A new factor – “region of interest” – comes into play. This means you can shoot 4K and then scale/crop the portion of the image that interests you. Naturally there was also 8K by NHK and also Quantel. Both have been on the forefront of HD and then 4K. Quantel was demonstrating 8K (downsampled to a 4K monitor) just to show their systems have the headroom for the future.

ARRI did not have a 4K camera, but the 4 x 3 sensor of the ALEXA XT model features 2880 x 2160 photosites. When you use an anamorphic 2:1 lens and record ARRIRAW, you effectively end up with an unsqueezed image of 5760 x 2160 pixels. Downsample that to a widescreen 2.4:1 image inside a 4096 DCI frame and you have visually similar results as with a Sony or RED camera delivering in 4K. This was demonstrated in the booth and the results were quite pleasing. The ALEXA looked a bit softer than comparable displays at the Sony and RED booths, but most cinematographers would probably opt for the ARRI image, since it appears a lot closer to the look of scanned film at 4K. Part of this is inherent with ARRI’s sensor array, which includes optical filtering in-camera. Sony was showing clips from the upcoming Oblivion feature film, which was shot with an F65. To many attendees these clips looked almost too crisp.

In practical terms, most commercial, corporate, television or indie film users of 4K cameras want an easy workflow. If that’s your goal, then the best “true” 4K paths are to shoot with the Canon C500 or the Sony F55. The C500 can be paired with the (now shipping) AJA KiPro Quad to record 4K ProRes files. The Sony records in the XAVC codec (a variant of AVC-Intra). Both are ready to edit (importer plug-ins may be required) without conversions.

You can also record ARRI 2K ProRes in an ALEXA or use one of the various raw workflows (RED, Canon, Blackmagic, Sony, ARRI). Raw is nice, but adds extra steps to the process – often with little benefit over log-profile recording to an encoded file format.

Edit systems

With the shake-up that Apple’s introduction of Final Cut Pro X has brought to the market, brand dominance has been up for grabs. Apple wasn’t officially at the show, but did have some off-site presence, as well as a few staffers at demo pods. For example, they were showing the XAVC integration in an area of the Sony booth. FCP X was well-represented as part of other displays all over the floor. An interesting metric I noticed, was that all press covering the show on video, were cutting their reports on laptops using FCP X. That is a sweet spot for use of the application. No new FCP X news (beyond the features released with 10.0.8) was announced.

Adobe is currently the most aggressive in trying to earn the hearts of editors. The “next” versions of Premiere Pro, SpeedGrade, Audition and After Effects have a ton of features that respond to customer requests and will speed workflows. Adobe’s main stage demos were packed and the general consensus of most editors discussing a move away from FCP 7 (and even Avid) was a move to Adobe. In early press, Adobe mentioned working with the Coen brothers, who have committed to cutting their next film with Premiere.

The big push was for Adobe Anywhere – their answer for cloud-based editing. Although a very interesting product, it will compete in the same space as Quantel Qtube and Avid Interplay Sphere. These are enterprise solutions that require servers, storage, software and support. While it’s an interesting technology, it will tend to be of more interest to larger news operations and educational facilities than smaller post shops.

Avid came on with Media Composer 7 at a new price, with Symphony as an add-on option to Media Composer. The biggest features were the ability to edit with larger-than-HD video sources (output is still limited to HD), LUT support, improved media management of AMA files and background transcoding using managed folders (watch folders). In addition, Pro Tools goes to 11, with a new video engine – it can natively run Avid sequences from AAF imports – and faster-than-real-time bounce. The MC background transcode and the PT11 bounce will be time savers for Avid users and that translates into money saved.

Avid Interplay Sphere (announced last year) now works on Macs, but its main benefit is remote editing for stations that have invested in Interplay solutions. Avid is also bundling packages of ISIS storage, Interplay asset management and seats of Media Composer at even lower price points. Although still premium solutions, they are finally in a range that may be attractive to some small edit facilities and broadcasters, given that it includes installation and support.

The other NLE players include Avid DS (not shown), Quantel Pablo Rio, Autodesk Smoke 2013, Grass Valley EDIUS, Sony Vegas, Media 100 (not shown) and Lightworks. Most of these have no bearing in my market. Smoke 2013 is getting traction. Autodesk is working to get user feedback to improve the application, as it moves deeper into a market segment that is new to them. EditShare is forging ahead with Lightworks on the Mac. It looked pretty solid at the show, but expect something that’s ready for users towards the end of the year. It’s got the film credits to back it up, so a free (or near free) Mac version should shake things up even further.

One interesting addition to the market is DaVinci Resolve 10 gaining editing features. Right now the editing bells-and-whistles are still rudimentary, though all of the standard functions are there. Plus there are titles, speed changes with optical flow and a plug-in API (OpenFX). You can already apply GenArts Sapphire filters to your clips. These are applied in the color correction timeline as nodes, rather than effects added to an editing timeline. This means the Sapphire filters can be baked into any clip renders. The positioning of Resolve 10 is as an online editing tool. That means conforming, titling and trims/tweaks after grading. You now have even greater editing capabilities at the grading stage without having to return to an NLE. Ultimately the best synergy will be between FCP X and Resolve. Together the two apps make for a very interesting package and Apple seems to be working closely with Blackmagic Design to make this happen. Ironically the editing mode page looks a lot like FCP X would have looked with tracks and dual viewers.

Final thoughts

I was reading John Buck’s Timeline on the plane. Even though we think of the linear days as having been dominated by CMX, the reality was that there were many systems, including Mach One, Epic, ISC, Strassner, Convergence, Datatron, Sony, RCA and Ampex. In Hollywood, the TV industry was split among them, which is why a common interchange standard of the EDL was developed. For awhile, Avid became the dominant tool in the nonlinear era, but the truth is that hasn’t always been the norm – nor should it be. The design dilemma of engineering versus creative was a factor from the beginning of video editing. Should a system be simple enough that producers, directors and non-technical editors can run it? Sound familiar?

When I look at the show I am struck at how one makes their buying choices. To use the dreaded car analogy, FCP X is the sports car and Avid is the truck. But the sports car is a temperamental Ferrari that does some things very well , but isn’t appropriate for others. The truck is a Tundra with all the built-in, office-on-the-road niceties.

If I were a facility manager, making a purchase for a large scale facility, it would probably still be Avid. It’s the safe bet – the “you don’t get fired for buying IBM” bet. Their innovations at the show were conservative, but meet the practical needs of their current customers. There simply is no other system with a proven track record across all types of productions that scales from one user to massive installations. But offering conservative innovation isn’t a growth strategy. You don’t get new users that way. Media Composer has become truly complex in ways that only veteran users can accept and that has to change fast.

Apple FCP X is the wild card, of course. Apple is playing the long game looking for the next generation of users. If FCP X weren’t an Apple product, it would receive the same level of attention as Vegas Pro, at best. Also a great tool with a passionate user base, but nothing that has the potential of dominating market share. The trouble is Apple gets in its own way due to corporate secrecy. I’ve been using FCP X for awhile and it certainly is a professional product. But to use it effectively, you have to change your workflow. In a multi-editor, multi-production facility, this means changing a lot of practices and retraining staff. It also means augmenting the software with a host of other applications to fix the short-comings.

Broadening the appeal of FCP X beyond the one-man-band operations may be tough for that reason. It’s too non-standard and no one has any idea of where it’s headed. On the other hand, as an editor who’s willing to deal with new challenges, I like the fast, creative cutting performance of FCP X. This makes it a great offline editing tool in my book. I find a “start in X, finish in Resolve” approach quite intriguing.

Right now, Adobe feels like the horse to beat. They have the ear of the users and an outreach reminiscent of when Apple was in the early FCP “legacy” era. Adobe is working hard to build a community and the interoperability between applications is the best in the industry. They are only hampered by the past indifference towards Premiere that many pro users have. But that seems to be changing, with many new converts. Although Premiere Pro “next” feels like FCP 7.5, that appears to be what users really want. The direction, at least, feels right. Apple may have been “skating to where the puck will be”, but it could be that no one is following or the puck simply wasn’t going there in the first place.

©2013 Oliver Peters

Noise Industries FxFactory 4

df_fxf4_1

Noise Industries was one of the first plug-in developers to leverage the power of the GPU by tapping into the core image component of Mac OS X. This approach took off when Apple added the FxPlug architecture to Final Cut Pro. From this start, Noise Industries has been able to develop its FxFactory product into both a powerful filter package and a platform to add filters from other partner companies. FxFactory 4.0.2 now supports Final Cut Pro 7 and X, Motion 4 and 5, After Effects and Premiere Pro (CS6). Although After Effects has been supported for a few versions, the upgrade to 4.0 extended support to Premiere Pro CS6. (FxFactory Pro 4.0.2 is a free upgrade for owners of FxFactory Pro 3.x versions.)

df_fxf4_7_smWhen editors install the free FxFactory application, it functions as a central control point to purchase, install, license and manage all of the filters. Most of the plug-in installers are included with the package and are available as trial versions, plus there are links to tutorials for each effect. FxFactory enables users to activate or deactivate products based on preference.

df_fxf4_5_smIf you purchase Noise Industries’ FxFactory Pro filter set, then this adds 176 filters, generators and transitions for Final Cut Pro 7, Motion, Premiere Pro and After Effects, and 160 effects for Final Cut Pro X. If you only purchased FxFactory Pro, you would have a well-rounded set of filters to tackle many creative challenges; however, the beauty of the FxFactory platform is in its extension through partner companies, whose plug-ins tie into this application.

Current partners include Yanobox, Ripple Training, Stupid Raisins, Squid FX, Tokyo Productions, Luca Visual FX, idustrial revolution, Nattress, Boinx Software, SUGARfx, PHYX, Cineflare, Dashwood, Sheffield Softworks, DV Shade, Crumplepop, Futurismo, Aquafades and nVeil. df_fxf4_4_smDepending on the company, some or all of their products are available though FxFactory and supported hosts vary with each product. Some of the newest additions that are built as Motion templates are only available within Final Cut Pro X. Purchasing FxFactory Pro and augmenting it with a number of these add-ins gives you a very powerful set of filters. On the other hand, if you only wanted to use Ripple Tools, Yanobox Moods or Luca VFX Lo-Fi Look, then simply purchase the individual filters you need and run them under the free version of FxFactory. This way you can grow your inventory of effects as budgets permit.

df_fxf4_2_smFxFactory developers have been rapidly adding to the options, due in part to the ability to create FCP X effects as Motion templates, along with an increased user demand for Premiere Pro plug-ins. Noise Industries has brought on board some of the popular plug-ins from the old FxScript days of Final Cut. These include Nattress and Sheffield with updated versions of their looks and grading tools. New developers, not previously known as plug-in creators, have joined the fold to offer FCP X-specific effects. These include Ripple, Tokyo, Squid FX, Stupid Raisins and others. Some of the long-time FxFactory partner developers, like Luca, Yanobox and idustrial revolution are bringing out new products, as well.

df_fxf4_3_smAs a whole, this group represents one of the most eclectic set of filters and transitions available anywhere. Because these products are not developed by a single team of programmers, you get different styles that don’t all look like they came from one company. It would be very difficult, within a reasonable amount of time, for a talented editor to re-create from scratch the sort of transitions you get from packages like XEffects, Slide Pop, FxTiles or Punchline -  even using a powerful NLE like Smoke or a compositor like After Effects.

df_fxf4_6_smAs a working editor who uses these products, I appreciate that Noise Industries spends a lot of time making sure their tools work with the changes Apple brings about. They are fast with fixes and I’ve found that their filters tend to be more stable than some other packages as NLE or OS updates come down the line. This is especially true with Final Cut Pro X, which is still a moving target, as Apple tweaks AV Foundations with each update. FxFactory Pro and partner filters run well within the application and provide reasonable real-time performance when left unrendered. If you are running variations of Final Cut, Motion, Premiere Pro and After Effects, then one price covers the plug-in installation for all of these hosts.

Originally written for Digital Video magazine.

©2013 Oliver Peters

Final Cut Pro X versus Premiere Pro CS6

df_fcpxvsppro_1_sm

The struggle within most shops that invested in Apple’s Final Cut Pro is whether to stay put a while longer, adopt Final Cut Pro X or cut the cord and move on. For many this means shifting to the Adobe Production Premium bundle – part of Creative Suite. Most of the editors and facilities in my sphere are doing just that. I’m one of only two local editors that I know of, who is actually using FCP X professionally. The rest are in the process of shifting to Premiere Pro, while maintaining some continued use of FCP “legacy”. This post is not intended as a “shoot out” or to say one is better than the other. Both are good tools and much of the choice gets down to personal preference. Instead, my goal is to lay out some random considerations in making the move.

Cross-platform / performance

Premiere Pro runs on Mac OS X and Windows workstations and laptops, while Final Cut Pro X is a Mac-only product. The biggest consideration is that by having the tool available to Windows, you open your access to the fastest machines and GPU cards. Premiere on a PC can tap into the faster NVIDIA CUDA-enabled cards, which is not an option for either Premiere or FCP X on the Mac. Although Premiere runs with both CUDA and non-CUDA cards on Macs, the selection is limited.

Adobe’s standalone software must be purchased with either a Mac or Windows license and switching platforms requires cross-grading the license. Unlike Avid, you cannot simply go from a PC workstation at a facility to a MacBook Pro at home with a simple de-activation/re-activation process. The exception is the Creative Cloud subscription, with permits access to both Mac and Windows licenses on up to two machines, as long as they aren’t used at the same time.

Naturally, if you opt for Final Cut Pro X, you have software that has been tweaked for the most current Apple hardware. We can argue the merits of CUDA, OpenGL and OpenCL acceleration, but it’s pretty clear that FCP X running on a decked-out iMac outperforms the application on a Mac Pro tower.

Suite versus “suite

Premiere Pro is generally purchased as part of the Production Premium or Master Collection software bundles – or as part of a Creative Cloud subscription. Final Cut Pro X is only available as standalone software through the Mac App Store. The beauty of the Adobe software is its integration, with direct links between Premiere Pro and After Effects, Prelude, Audition or SpeedGrade. These aren’t all fully developed yet, but it’s a key reason some editors prefer Premiere Pro.

On the other hand, there’s a large ecosystem growing up around Final Cut Pro X that constitutes much of the same. It’s not an official “suite” of software and interoperability is limited to translations of FCPXML. For similar dollars, you get similar capabilities – only with the added ability to pick and choose what’s right for your workflow.

Plug-ins

The plug-in architecture for Premiere Pro has historically been weak. Many of the third-party After Effects plug-ins show up and work within Premiere Pro, but some don’t. If you edit in Premiere, you are best off doing your effects in After Effects. Lately, developers have been tweaking their filters to make them work – or work better – inside Premiere.

To compare, Final Cut has no plug-in architecture. Instead third-party plug-ins use FxPlug through Motion and then show up inside FCP X as a Motion template, rather than a traditional plug-in. This allows developers to not only create updated plug-ins for Motion and FCP X, but also add new and unique effects and transitions built strictly as Motion projects. These in turn are published to FCP X as effects. Since this latter approach requires less programming skill, the market for low-cost (and even free) FCP X plug-ins has exploded. Not to mention, there are effects and transitions for FCP X that simply don’t exist – or can’t easily be re-created - for any other NLE.

Organizational tools

All NLEs are giant databases tracking information. Final Cut Pro X takes this to a new level and uses ratings, keywords and smart collections as a means for fast and automatic organization of your media. Plus a considerable amount of camera and textual metadata is tracked in the background. This doesn’t mean that Premiere Pro doesn’t track a lot of data, as well. Open the metadata display window and you find plenty of fields that are assignable to each clip. Bins can be filtered by a search field, which will reduce the amount of clips displayed according to the search criteria being typed in.

User interface configurations

Final Cut Pro X’s interface design is based on panels and windows that can be opened and closed as needed. It is arranged well for single and dual-screen layouts, though you have very few options to move any of these windows around and create custom screen layouts. Premiere Pro uses a system of dockable tabs common across several of Adobe’s applications, including After Effects and Photoshop. Re-arrange these as you see fit and save custom workspace layouts.

Tracks versus trackless

Premiere Pro uses the “traditional” track-based timeline structure, where audio and video is separated into tracks and clips are positioned on the timeline based on a reference to absolute time. Final Cut Pro X’s timeline does not use tracks, but instead lays out clips according to storylines and connected clips. These are linked to each other in a parent-child relationship. This allows groups of clips to be moved, by simply moving the clip on the storyline to which the others are attached. There is no vertical hierarchy to audio and video content as tracks. Although video is displayed to the viewer from the top down, audio and video connected clips can be linked above or below the central primary storyline.

Project and clip management

Premiere Pro creates a single, self-contained data file for every edit project. This file contains the links to all media on your hard drives and the edited sequences created from these. Final Cut Pro X divides its structure into Events (source media) and Projects (edited sequences). These correspond to separate folders on your hard drive as well as divisions within the FCP X interface. Event folders can contain either actual source media content – or alias files pointing to other locations on your hard drives for that source media.

Media management

At the end of a production, many editors like to organize the final edited sequence and the clips used within it into a single “consolidated” project. This means the source clips have been trimmed to only the portions used, plus a few seconds of “handles” on the ends of the trimmed clips. Premiere Pro allows you to do this via its Project Manager tool. FCP X currently does not allow any clip trimming. You can copy a Project (edited sequence) with its used clips to a new Event, but then it requires a second step to organize the media. That step copies the media itself for all used clips into the new Event that was created.

Multiple editor interaction

Right now, neither tool is very good for collaborative editing. Final Cut Pro X works best to have all Event and Project folders at the root level of drives and only one editor can access those at a time. There is an “add SAN location” feature for shared storage environments, but it doesn’t appear to work with all SANs. The best method is to have media on a SAN, but keep the Event and Project files local to each system, with the media linked to these. If one or more editors is working on the same production, then each can have local, “mirrored” versions of the Event folders. To exchange edited sequences, simply copy and transfer the Project files that you’d like to share.

In the case of Premiere Pro, the current workflow is similar to that of FCP 7. It will likely change after NAB, where Adobe is expected to show Adobe Anywhere as a real product and its entry into collaborative editing. Currently, if multiple editors work on the same Premiere-based production, media can be on a SAN, but the project files should be on local drives. Unfortunately, you cannot open multiple project files at once. When you import another editor’s sequence into your project, it annoyingly imports all the associated master clips, even through they may already exist within your project. These cannot be removed, otherwise clips in your imported sequence will go offline.

[EDIT - My Premiere Pro import issues were challenged by a reader, so I went back and did some testing. It appears that if two editors create two unique projects, but using the same media (like in a shared storage facility), then duplicate master clips are created upon import. However, if the second project is created using a "save as" command, then sequences imported from it back into the original project do not create duplicate master clips.]

List interchange

Final Cut Pro X only interchanges data with external applications using the FCPXML data format. This is different than other versions of XML, which means you have to use translation to get from FCP X to FCP 7, for example. Premiere Pro supports XML, EDL, OMF and AAF (limited).

Tape handling (or not)

Neither application is great for videotape-based workflows. Premiere Pro has capture-from-tape and output modules, but it’s not as solid as FCP 7 and definitely not as good as Avid Media Composer. On the other hand, FCP X’s is non-existent. There is limited support for Firewire-enabled videotape decks, like HDV, but you really end up using the capture/output utilities of the third-party hardware cards (AJA, Blackmagic Design, Matrox, MOTU).

The Cold Mountain moment

Feature film editors’ use of specific NLEs does not amount to a large market segment for either of these manufacturers (nor Avid, for that matter, either). But the association with a Hollywood blockbuster fuels aspirational marketing in other sectors. It wasn’t until Walter Murch cut Cold Mountain – along with the Coen Brothers’ use of FCP – that Final Cut started to get noticed by a large portion of the professional editing community as a viable tool. Neither Apple nor Adobe have had that yet with Premiere Pro or FCP X. There has not been a major feature film cut with either.

Adobe is a bit closer in that many films have touched on Premiere Pro as a conduit to get into After Effects or handling some conforming tasks. Naturally, Adobe is more than happy to let the lines be blurred through omission between these roles and doing an actual creative edit of a film. That is likely to change this year. This is purely a guess, but I wouldn’t be surprised to see a studio film being cut on FCP X or Premiere Pro at some point during 2013.

Pricing and openness

For now, when you compare cost, FCP X is the better deal. Even when you add more applications and utilities to fill in the gaps, the cost is lower than Premiere Pro. Add to that the fact that Mac App Store purchases can run on multiple machines under a single Apple ID, thus bringing the cost per machine even lower. Adobe is in the process of changing its sales and licensing structure through the Creative Cloud mechanism, but the limit is typically two machines. The beauty here is that you have access to the whole host of Adobe creative applications for video, photography, web and design as part of a monthly subscription model.

Over the course of the first year on one machine, cost is probably going to be similar for most users. If you use multiple machines, own the software for several years or use more than the average number of applications, then the scale will tip in favor of one company or the other. Both the Mac App Store and Creative Cloud models allow for more rapid updating of software than in previous years.

Openness and company response may also be a factor in your purchasing decisions. Apple is secretive about new product development. They do listen to customer feedback, but they don’t show it publicly. Adobe has tried to be very proactive in their outreach to the professional creative community. In the end, the net result may be the same in how it translates into new features that you can use.

Interesting tools

Both NLEs offer tools beyond just media organization and editing. For instance, both include stabilization, but Premiere Pro includes extra touches to fix rolling shutter artifacts. FCP X includes optical flow processing for high-quality variable speed effects. Final Cut features a number of non-destructive “automatics” for image and sound analysis on ingest and shape/shot recognition. Premiere Pro offers speech-to-text analysis. A lot of these tools fall into the “nice to have, but I never use it” category for me. Still, if these are worthwhile for you, then take a closer look.

Batch exports

Neither tool offers good batch export tools like I’m used to with FCP 7, however, each offers queued exporting functions of edited sequences. In Premiere Pro, if I want to export multiple sequences, or the same sequence as multiple deliverables, then all I need to do is set up a queue in Adobe Media Encoder. With Final Cut Pro X, I can use the Share menu to export straight from the timeline or send Projects to Compressor. Unfortunately neither one lets me export a QuickTime reference file that can be used in other encoders. You first have to export a self-contained master file if you intend to use it with other software.

Responsiveness

This is a big one for me and a good place to end this list. In its current form, FCP X feels a tad buggy to me. Response is generally better on an iMac. I’m mainly on Mac Pros, so playback often just doesn’t look smooth. It’s definitely not dropping frames, but looks like the graphics card (usually an ATI 5870) simply isn’t refreshing as well as it should. The interface also tends to feel “sticky” as I’m going between windows. It “forgets” where it is during skimming when switching between a clip in the Event browser and the timeline. Then it takes a bit of clicking around in the interface to get it to “wake up”.

There seems to be some type of RAM leak issue,too. The longer I work on it in a day with large Events (bins), the more sluggish it becomes. This requires me to close and relaunch the application to get peppier performance.

I don’t see any of this with Premiere Pro. I do miss the skimming features of FCP X (no, hover scrub is NOT the same), but otherwise, the Premiere Pro user interface interaction seems to be better for now. I’d say for me, this is an annoyance and not a deal-breaker, but it definitely needs to be addressed by Apple.

©2013 Oliver Peters

Organizational Tips for FCP X

df_fcpxorg_12

The beauty of Apple Final Cut Pro X is in its power to organize media. When editors take advantage of these tools, FCP X can prove to be a very fast way to cut. I’ve covered some of these concepts in previous posts on “Rethinking NLE Design”. Here are some tips that will help you get more out of FCP X. Click on the thumbnails to see an enlarged image for an expanded view of each of these tips.

df_fcpxorg_1_smProjects and Events. FCP X organizes media and sequences into Events (source media) and Projects (edited sequences). These divisions correspond with matching data files and folders at the Finder level. Unfortunately a colossal oversight was the lack of any way to organize these within the application. All active Events and Projects are open and accessible when you launch FCP X. The solution is Event Manager X from Intelligent Assistance – an essential tool for working with FCP X. This handy utility controls the location (and visibility) of Events and Projects by automatically moving unneeded files between the active and “hidden” folders.

df_fcpxorg_2_smFinder organization. Many editors like to “pre-organize” media files on their hard drives at the Finder level. FCP X lets you use that structure when importing files. Enable this preference on import and hard drive folders will be used for Keyword Collections. The latter function is the equivalent of creating bins with subclips in other NLEs. If you organized camera media by day and camera on the hard drive, the same breakdown will be automatically created in FCP X as part of the import.

df_fcpxorg_4_smEntering multiple user data fields. Custom user data, like reel names, scenes, takes, camera angles, etc. can be entered in the Event column or in the Inspector pane. When multiple clips are highlighted, the editor can use the Inspector to enter common values for all of these clips with a single entry.

df_fcpxorg_5_smKeywords and folders. Events are the location to store master clips (sources) within the FCP X interface. The corresponding Event folder on the hard drive can contain links/aliases to external media or actual media, depending on your import preference settings. Media within an Event can be organized by assigning keywords, which places the equivalent of a full-length subclip into a corresponding Keyword Collection. Multiple keywords can be assigned. The example image is from a series of grocery store commercials. On-camera employee clips can be placed into different sets of Keyword Collections that are organized by day/camera, department/category and person’s name. Keyword Collections can be placed into folders for a further level of organization. This enables the editor to locate clips using any of these subdivisions.

df_fcpxorg_7_smExpand or collapse Event Library. The Event Library pane shows all hard drives and Events visible to FCP X, as well as the Keyword and Smart Collections created by the editor. The leftmost panel can be expanded or collapsed to show/hide the drives, events, folders and collections. When the view is collapsed, only the clips within the highlighted event or collection are displayed.

df_fcpxorg_8_smEvent grouping. The Event Library can be displayed as an open list or can be grouped by various criteria. For example, if you need to quickly identify the most recent media imported, then group clips by date imported and the list becomes divided and sorted accordingly.

df_fcpxorg_6_smLists and filmstrips. When the Event Library is set to a list view, the selected clip is displayed as a filmstrip at the top of the window. This strip includes an audio waveform, which makes it easy to identify audio spikes, such as the start of each take in a series of takes within a longer clip. It shows markers added by the editor and highlighted regions for in-out ranges and Favorites (saved subclip ranges).

df_fcpxorg_3_smProject Library. Projects are edited sequences and shouldn’t be confused with a “project” file in the same sense as in FCP 7 or Premiere Pro. These sequences are typically saved within the Final Cut Projects folder, which is a separate folder from the Final Cut Events folder. Sequences can be previewed and/or skimmed from the Project Library pane. The more visible Projects you have, however, the longer this pane will take to display when opened. To organize a lot of Projects, place them into folders, which can be left closed until you need to access the files within. This lets you place older versions of a cut out of the way, but still accessible if needed.

df_fcpxorg_9_smEdits saved in the Event. The Project Library is the place to save edited sequences, however, edits can also be saved in an Event. Edited sequences or sections of sequences can be saved as Compound Clips. These go into an Event. By opening the Compound Clip in a timeline, you can continue to edit within that Compound. Depending on your strategy, Compound Clips can be organized into Keyword or Smart Collections for quick retrieval.

df_fcpxorg_10_smAudio expansion. By virtue of using a trackless design, FCP X combines the audio and video channels for each source into a single clip on the timeline. All channels for multi-channel audio sources are represented by a single waveform. To access individual channels, the timeline clips can be expanded to expose the audio “tracks”. Audio components can be further expanded in the Inspector or timeline to display individual audio channels for that source. The audio configuration (such as dual mono versus stereo) can be changed and/or channels muted or enabled. It is also necessary to expand audio in order to enable split-audio trimming (L-cuts and J-cuts).

df_fcpxorg_11_smControlling clips on the timeline. The Clip Appearance menu lets you adjust clip height and how clips are displayed. For maximum real estate, use the smallest “chicklet” view. To access audio and expand clips, use one of the views with a visible waveform. The Timeline Index is another way to focus in on elements of the timeline. Roles can be enabled or disabled, which effectively solos certain timeline clip categories.

Click here for another blogger’s article on this subject (Part 1). (Part 2). (Part 3).

©2013 Oliver Peters