Automatic Duck Redux

df3915_ad_1_sm

Automatic Duck invented timeline translations between applications. Necessity is the mother of invention, leading Wes Plate, an Avid Media Composer editor who tackled compositing in Adobe After Effects, to team with his programmer father, Harry. The goal was to design a tool to get Avid timelines into After Effects compositions. Automatic Duck grew from this beginning to create a series of translation products that let editors seamlessly move timelines between a number of different hosts, including Media Composer, Pro Tools, After Effects, and Apple Final Cut Pro “classic”.

Four years ago Adobe licensed the IP for the original Automatic Duck Pro Import products, as well as brought the father/son team on board to develop tools for Adobe. Now they are back on their own and have decided to reboot Automatic Duck, which has been mothballed for the past four years. Seeing an opportunity in Apple’s Final Cut Pro X, the company has developed Ximport AE, a timeline translation tool to bring Final Cut Pro X projects (edited sequences) into After Effects. The team is no stranger to Final Cut Pro X’s new FCPXML format, since it was the first developer to create a companion utility that translated Final Cut Pro X 10.0 projects into Pro Tools sessions.

Knowing the market

df3915_ad_2First, let’s define the market. Who is Automatic Duck Ximport AE for? Editors who do most of their heavy lifting in Media Composer, Final Cut, or Premiere Pro might not see the attraction. On the flip side, though, there are quite a few editors for whom After Effects is the tool of choice for all effects and even finishing. For this group, the NLE is where they spend the least amount of time. They use an editing application for shot selection and assembly and then go straight to After Effects for everything else.

If you are a motion graphics designer who relies on After Effects, then your occasional need for an NLE might be best served by FCP X. The interface is fast and easy to master, compared with more traditional track-based edit software. Finally, if you are a dedicated FCP X editor, you no longer have a “send to Motion” function as in the old Final Cut Studio. This means you can’t send more than a single shot to Motion for treatment. Besides, After Effects may still be your preferred motion graphics application. Take all of these points into consideration and you’ll see that there’s a clear need to get a project from FCP X into After Effects – the industry’s dominant motion graphics application.

How it works

df3915_ad_4Automatic Duck Ximport AE is designed as a plug-in that’s installed into After Effects, including CS6 up through the current CC2015 version (and beyond). There are several other competing translation tools on the market, which convert between flavors of XML or from FCPXML into AE Scripts. Automatic Duck is the only one that integrates directly into the After Effects import menu. Ximport AE cuts out one middle step in the process and should provide for a more complete translation from FCP X into After Effects.

I’ve been beta testing the product for a few months and it certainly hits the mark for serious users. The steps are simple. Just cut your sequence in Final Cut Pro X and then export an FCPXML for that project (sequence). When you open After Effects, select File > Import > Automatic Duck Ximport AE. This opens a dialogue box with a few settings and it’s where you navigate to the correct FCPXML file. Settings include whether to let your clips cascade up or down in the After Effects timeline, as well as an option to create pre-comps from Final Cut’s secondary storylines. The question mark icon also launches the user guide.

In the timelines I’ve tested, the translation is quite good. Compound clips are packaged as pre-comps. The active angle of Multicam clips and the selected pick of Audition clips are translated. Alternate angles aren’t.  Generally transform, crop, opacity, and blend functions are supported, as are audio and video keyframes. A number of third party filters are accurately translated between applications, assuming that the same filter is installed into each host. At launch, these include selected plug-ins from Boris FX, Digital Anarchy, Noise Industries/FxFactory, PHYX, Red Giant, and Yanobox. Check the user guide for a detailed list with specific filters.

Some caveats

df3915_ad_3It’s worth noting, however, that just about all of the built-in FCP X filters are not translated into an equivalent filter in After Effects. For example, the color board metadata is included in the FCPXML, but there’s no way to read that info on the After Effects side. This is true even when there are filters that appear to be the same. For example, both hosts include a native Gaussian blur filter, yet that doesn’t get translated. On the other hand, if you apply a Flipped filter in FCP X, it will be correctly translated into the -100 transform scale value in After Effects. So again, read the user guide and do a little experimentation to see what works and what doesn’t in your projects. Whenever an effect is not supported, a note is made in the companion HTML file created at import. A marker is also placed on that clip in the After Effects timeline, naming the missing plug-in.

df3915_ad_6I tested a number of supported third-party products, staying mainly within the Red Giant family. Translation was good between the Magic Bullet tools, but not without issue. For example, Universe ToonIt Expressionist Noise was available in both hosts, yet the effect was not applied in the After Effect composition. That’s because at the time I tested this using a beta build, that specific Universe filter had not been included. This has since been corrected. Other effects, like Looks, Colorista III, Mojo, Universe Glow, and others worked flawlessly. According to Wes Plate, the plug-in has been architected in a way to easily add support for new effects plug-ins. The bottom line is that if you stay within the supported features, you will get the richest translation experience from FCP X into After Effects that’s currently available in the market.

Automatic Duck Media Copy 4.0

df3915_ad_5Along with Ximport AE, the company will also introduce Automatic Duck Media Copy 4.0. The original Media Copy grew out the need to collect, copy, and move sequences and their associated media. The original version worked for Avid Media Composer and Apple Final Cut Pro “classic” sequences. It would read either the AAF or XML file and copy all associated media, plus the timeline edit info. This new folder could then be moved to another system for more editing or used as a back-up archive. Media Copy 4.0 has been updated to add FCPXML support. As before, it collects media and timeline files for use elsewhere. It does not trim or transcode the media, but you have the choice to copy media all into a single folder or to maintain a folder hierarchy matching the original paths within the newly created location. Media Copy works well as a standalone application or as a companion to Ximport AE. It supports Avid Media Composer, Final Cut Pro X, and Final Cut Pro 6/7.

With the reboot of Automatic Duck, they’ve decided to partner with Red Giant Software to provide marketing, sales, and customer support. Red Giant will offer Automatic Duck Ximport AE for $199 and Media Copy 4.0 for $99. If you still have need for Automatic Duck’s legacy products, the company is posting them again on their own website for free, with an optional “donate” button. These include Pro Import FCP, Pro Export FCP (for FCP 7 users), and Pro Import AE (for importing AAF and XML into AE CS 5.5 or earlier).

Regardless of which NLE you use, I’ve found Media Copy to be an essential tool, whether or not you work with effects or motion graphics. It’s great to see Automatic Duck update it, as well as launch their next great product, Ximport AE. Adobe After Effects will continue to be the ubiquitous compositing and motion graphics choice for most editors, so this marriage between Final Cut Pro X and After Effects make great sense.

For more, here’s a good interview with Wes Plate at Red Shark News.

©2015 Oliver Peters

Blackmagic Design DaVinci Resolve 12

df3115_R12_1_sm
The industry has been eager to check out Blackmagic Design’s DaVinci Resolve 12. This “first look” is based on the initial build of the Resolve 12 public beta. A number of functions have not yet been enabled, so expect to see some changes in the product by the time you read this.

As with any public beta, the point is to get feedback and reap the benefit of crowdsourced quality testing, so be careful about using it on real jobs. That being said, so far I’ve found the public beta builds to be reasonably stable. I’ve had a chance to test the application on several different machines, including two 2009-2010 Mac Pro towers and a new 15” Retina MacBook Pro. Testing included a Sapphire 7950 and an Nvidia Quadro 4000 GPU, as well as the built-in Nvidia card on the laptop.

Blackmagic is no longer using the “Lite” name to identify the free version. The branding is now DaVinci Resolve 12 (free) and DaVinci Resolve 12 Studio ($995). The free version includes the majority of features and is limited to an output no larger that UltraHD 4K. The paid version adds advanced features, including stereoscopic functions, networked collaboration between users, multiple GPU support, and the ability to output at larger than UltraHD 4K frame sizes.

Blackmagic Design hardware products are required to output an analog or digital signal to an external video monitor or tape deck. If you are comfortable making color judgements based on the viewer image, then no hardware is require for operation and rendering. You can also hot rod your system with the DaVinci Control Surface ($29,995) or a number of supported third-party surfaces that are less costly.

Refreshing the user interface

df3115_R12_3DaVinci Resolve 12 ushers in a fresh user interface. Previous versions mimicked the style of Apple Final Cut Pro X, but the new UI is flatter with thinner fonts. It takes on the trendy design aesthetic employed in Windows 8/10 and Mac OS X/iOS. The background colors are a lighter grey with a faint blue cast to them. Although pleasing, I find that last part strange for a color correction application, where a true grey is considered the norm.

The interface has been optimized for single and dual-monitor systems, as well as higher-density displays, like Apple’s Retina. Resolve 12 is divided into four modes or pages: Media, Edit, Color, and Deliver. Software control panels can be opened or closed as needed, including videoscopes, media storage locations, mixers, audio meters, inspector, effects, and more. There are some interesting options to control whether or not a panel or window runs the full horizontal or vertical length of your display. However, there is no way to create a custom workspace by docking panels in different places and then saving that as your personal layout. Interface colors also can’t be personalized.

As before, timelines support sources with mixed formats and frame rates, however, the base timeline setting must match that of the project. This means you cannot have a 720p/59.94 and a 1080i/29.97 timeline within the same project. You can’t have multiple timelines open, but it’s easy to access different timelines in the same project quickly. You can also cut one timeline into another as a nested sequence. Such nests (as well as compound clips) can be decomposed in the timeline, leaving the original source clips to work with.

Resolve 12 no longer includes a separate section in the UI for timelines, as these are placed together with the source media in the Media Pool. One simple solution is to create a Bin for your edits and manually drag the timelines you’ve created into that Bin. Another option is to filter timelines into a Smart Bin by including some common element in the name. For example, you could append “seq” (for sequence) to the end of the name of each timeline. Set your filtering criteria to names that contain “seq” and then timelines will automatically show up in the Smart Bin that you’ve created for timelines.

Editing with Resolve 12

df3115_R12_4As a a nonlinear editing application (NLE), Resolve 12 is an interesting mash-up among several other NLEs, including Premiere Pro, FCP 7 and FCP X. There are new features clearly intended for editors, including multi-camera editing. You can now organize clips and timelines into custom bins, add metadata, assign sortable color flags and other metadata values, and automatically filter clips into Smart Bins. You can sync grouped clips (double-system sound) and multi-camera clips using in-points, timecode, or audio waveforms. The multi-cam editing routine is similar to other NLEs, where you drop a multi-cam clip onto your main timeline and then cut between camera angles.

Blackmagic placed a lot of attention on timeline trim functions. It’s now possible to do some very elaborate asymmetrical trims of multiple clips. Slip/slide trimming and split audio is all very easy and fluid. There is no trim window, so on-the-fly JKL trimming – a la Media Composer – isn’t possible. When you trim via the mouse or keyboard, you get a 2-up preview in the viewer and a 4-up display when slipping and sliding clips. You can access a curve editor in the timeline for transitions, which lets you control the transition acceleration. When you select source clips in the list view mode of the browser, you get a skimmable filmstrip of the selected clip, much like in FCP X.

Video effects are still based on OpenFX, so any third-party filters and transitions that offer OFX host support (FilmConvert, BorisFX, NewBlueFX, etc.) will show up in either the Edit page effects palette or the Color page, depending on whether the filter is something that requires a color correction node in order to be applied. Blackmagic also includes its own toolbox of effects and transitions, including the new Smoothcut transition. This is a morphing dissolve designed to smooth jumpcuts between edited soundbites from on-camera interviews. It is similar to Adobe’s Morph Cut or Avid’s FluidMorph, but seems to rely more heavily on GPU processing. Therefore, you don’t have to wait until a lengthy analysis pass is completed before you can review the results. As with all of these effects, real-world results vary with how closely the alignment is on both sides of the cut. It tends to work best with a duration of two to four frames.

Audio went through big changes in Resolve 12 to improve performance and to add features. VST and AU plug-ins are supported. Any that are installed on your system will show up in the audio effects palette. Effects can be applied to clips or tracks and there’s automation-style track mixing. The way audio tracks are implemented seems confusing to me – especially audio track patching. Tracks can be mono, stereo, 5.1, or adaptive, but there’s no indication in the timeline window as to what type of track it is. When you edit a multi-cam clip to the timeline and the source audio contains several channels, then it is no longer possible to break those clips apart or access individual channels from the timeline. Both Adobe and Apple use similar methods, but with a better approach in each’s implementation. Like in Premiere Pro, it is best to start out by properly setting the source audio channel configuration in the clip properties menu for each clip. You can access this in the Media page.

Other improvements

df3115_R12_5DaVinci Resolve 12 is not only about editing. Since Resolve is used a lot as a DIT tool to generate dailies, there’s a new capability in the Media page to apply color space changes and camera LUTs to a group of clips. If you shot log-encoded footage and apply a Rec709 LUT on the Media page, you’ll now see the corrected color throughout. The downside is that such LUTs are not visible on the Color page and can’t be removed in any of the color adjustment nodes.

The new blue and greenscreen 3D keyer is accessible on the Color page. It yields high-quality results and is aided by new, matte finesse controls, plus Resolve’s great masking and tracking capabilities. There’s also improved ACES support, better shot-matching between clips, and more.

Resolve 12 uses a central database to house all project files. This makes it harder to move files between users than with other NLEs. Previous versions let you export Resolve projects to move them to other systems, but now Resolve 12 adds copy, move, transcode, relink, and consolidate functions. Support for FCPXML (for projects offline-edited using FCP X) has been updated to the newest version of this format.

There had been a bug in how Resolve wrote FCPXML files, so going back into FCP X from Resolve exhibited relinking issues. This only occurred when importing on a different machine than where the files were generated. This bug appears to have been fixed in version 3 of the public beta build.

To include another tool for editors, Blackmagic added an AAF export to Pro Tools feature. I don’t have ProTools, so I wasn’t able to test the Pro Tools export properly. All audio clips are exported in .MXF format, which means many applications can’t play the audio. For example, when I imported the AAF into Apple Logic Pro X, the track sheet was blank. I have been able to send audio from Final Cut Pro X into Logic Pro X using X2Pro Audio Convert to create an AAF.

Performance

df3115_R12_2Real-time media performance is critical to a good editing experience. Resolve 12 is optimized for hardware using the PCIe 3.0 bus, which supports greater bandwidth. Older Mac Pro towers or Windows computers that use PCIe 2.0, are going to be challenged when loaded with PCIe cards. You see this mainly in the Edit page, because more things are going on in the interface on that page. Windows user with the newest hardware and Mac users who own new “trash can” Mac Pros will most likely have a better editing experience than owners of legacy machines.

I experienced choppy video being displayed in the viewer of the Edit page, even though output through the Decklink was fine. Ironically, viewer and video output were smooth on the other pages. After consulting with Blackmagic, the following recommendations gave me the performance I would expect out of an NLE: run in the single-screen layout, close the audio mixer panel, close the audio meters, and/or switch the video monitoring setting to 8-bit. Of these, the mixer suggestion made the biggest difference. The ability to create on-the-fly, low-resolution proxies for editing wasn’t enabled with the first few builds of the public beta. It was turned on in build three. This gives you similar results to that of other NLEs running in a half-resolution, quarter-resolution or “dynamic real-time” mode.

One common mistake that I see users make, when I read some of the internet forum posts, is that they load up the timeline clips with color correction nodes and still expect real-time editing performance. Physics hasn’t changed. Adding effects and color correction to clips is going to negatively impact playback. As a general rule, get all of your editing done first and then save your color correction until last. You’ll be a lot happier.

Final thoughts

Once the official Resolve 12 release rolls out, we’ll see where it finds a place as an editor. This release won’t sway editors who are currently happy with one of the other popular NLEs to switch to Resolve 12 as their main axe. However, I suspect it will increasingly become the finishing tool of choice – probably edging out Autodesk Smoke over time. Now that the editing tools and performance are there, it becomes the ideal application for final edit revisions, grading, and mastering. It can already combine lists and media from a range of creative editing systems.

The other element in this equation is Fusion, the node-based composting application they picked up from EyeOn. There’s already a connecting plug-in between it and NLE timelines that Avid has enjoyed. With a bit more development time, I could clearly see some integration between Resolve and Fusion. That might be why “Studio” is now part of the name change. Hmmm…

When Resolve 11 came out, it, too, was touted as an editor. My critical assessment was that it was a grading tool that could be used as an editor, but you wouldn’t want to. With Resolve 12, Blackmagic has produced an application that is both grading tool and an editor. I could easily see myself using it as my secondary NLE. There is certainly great synergy between Final Cut Pro X and Resolve. Why not have both in your arsenal?

The enticement of a free editing application to many new users is hard to resist. Not to mention that it is cross-platform and unfettered by a software subscription business model. Clearly the development pace by Blackmagic Design since they acquired the product has been impressive. This makes me believe that Resolve will find a new audience willing to use it as their primary creative tool for start-to-finish post production.

Click here for a look back at Resolve 11, which will give you an additional insight into some of Resolve’s feature set.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

Final Cut Pro X Organizing Tips

df1415_organize_1_sm

Every nonlinear editing application is a database; however, Apple took this concept to a higher level when it launched Final Cut Pro X. One of its true strengths is making the organization of a mountain of media easier than ever. To get the best experience, an editor should approach the session holistically and not simply rely on FCP X to do all the heavy lifting.

At the start of every new production, I set up and work within a specific folder structure. You can use an application like Post Haste to create a folder layout, pick up some templates online, like those from FDPTraining, or simply create your own template. No matter how you get there, the main folder for that production should include subfolders for camera files, audio, graphics, other media, production documents, and projects. This last folder would include your FCP X library, as well as others, like any After Effects or Motion projects. The objective is to end up with everything that you accrue for this production in a single master folder that you can archive upon completion.

FCP X Libraries

df1415_organize_5It helps to understand the Final Cut Pro X Library structure. The Library is what would otherwise be called a project file, but in FCP X terminology an edited sequence is referred to as a Project, while the main session/production file is the Library. Unlike previous versions and other NLEs, the Library is not a closed, binary data file. It is a package file that you can open and peruse, by right-clicking the Library icon and using the “show package contents” command. In there you will find various binary files (labeled CurrentVersion.fcpevent) along with a number of media folders. This structure is similar to the way Avid Media Composer project folders are organized on a hard drive. Since FCP X allows you to store imported, proxy, transcoded, and rendered media within the Library package, the media folders can be filled with actual media used for this production. When you pick this option your Library will grow quite large, but is completely under the application’s control, thus making the media management quite robust.

df1415_organize_4Another option is to leave media files in their place. When this is selected the Library package’s media folders will contain aliases or shortcut links to the actual media files. These media files are located in one or more folders on your hard drive. In this case, your Library file will stay small and is easier to transfer between systems, since the actual audio and video files are externally located. I suggest spreading things out. For example, I’ll create my Library on one drive, the location of the autosaved back-up files on another, and my media on a third. This has the advantage of no single point of failure. If the Library files are located on a drive that is backed up via Time Machine or some other system-wide “cloud” back-up utility, you have even more redundancy and protection.

Following this practice, I typically do not place the Library file in the projects folder for the production, unless this is a RAID-5 (or better) drive array. If I don’t save it there during actual editing, then it is imperative to copy the Library into the project folder for archiving. The rub is that the package contains aliases, which certain software – particular LTO back-up software – does not like. My recommendation is to create a compressed archive (.zip) file for every project file (FCP X Library, AE project, Premiere Pro project, etc.) prior to the final archiving of that production. This will prevent conflicts caused by these aliases.

If you have set up a method of organization that saves Libraries into different folders for each production, it is still possible to have a single folder, which shows you all the Libraries on your drives. To do this, create a Smart Folder in the Finder and set up the criteria to filter for FCP X Libraries. Any Library will automatically be filtered into this folder with a shortcut. Clicking on any of these files will launch FCP X and open to that Library.

Getting started

df1415_organize_2The first level of organization is getting everything into the appropriate folders on the hard drive. Camera files are usually organized by shoot date/location, camera, and card/reel/roll. Mac OS lets you label files with color-coded Finder tags, which enables another level of organization for the editor. As an example, you might have three different on-camera speakers in a production. You could label clips for each with a colored tag. Another example, might be to label all “circle takes” picked by the director in the field with a tag.

The next step is to create a new FCP X Library. This is the equivalent of the FCP 7 project file. Typically you would use a single Library for an entire production, however, FCP X permits you to work with multiple open Libraries, just like you could have multiple projects open in FCP 7. In order to set up all external folder locations within FCP X, highlight the Library name and then in the Inspector panel choose “modify settings” for the storage locations listed in the Library Properties panel. Here you can designate whether media goes directly into the internal folders of the Library package or to other target folders that you assign. This step is similar to setting the Capture Scratch locations in FCP 7.

How to organize clips within FCP X

df1415_organize_8Final Cut Pro X organizes master source clips on three levels – Events, Keyword Collections, and Smart Collections. These are an equivalent to Bins in other NLEs, but don’t completely work in the same fashion. When clips are imported, they will go into a specific Event, which is closest in function to a Bin. It’s best to keep the number of Events low, since Keyword Collections work within an Event and not across multiple Events. I normally create individual Events for edited sequences, camera footage, audio, graphics, and a few more categories. Clips within an Event can be grouped in the browser display in different ways, such as by import date. This can be useful when you want to quickly find the last few files imported in a production that spans many days. Most of the time I set grouping and sorting to “none”.

df1415_organize_7To organize clips within an Event, use Keywords. Setting a Keyword for a clip – or a range within a clip – is comparable to creating subclips in FCP 7. When you add a Keyword, that clip or range will automatically be sorted into a Keyword Collection with a matching name. Keywords can be assigned to keyboard hot keys, which creates a very quick way to go through every clip and assign it into a variety of Keyword Collections. Clips can be assigned to more than one Collection. Again, this is equivalent to creating subclips and placing them into separate Bins.

On one set of commercials featuring company employees, I created Keyword Collections for each person, department, shoot date, store location, employees, managers, and general b-roll footage. This made it easy to derive spots that featured a diverse range of speakers. It also made it easy to locate a specific clip that the director or client might ask for, based on “I think Mary said that” or “It was shot at the Kansas City store”. Keyword Collections can be placed into folders. Collections for people by name went into one folder, Collections by location into another, and so on.

df1415_organize_3The beauty of Final Cut Pro X is that it works in tandem with any organization you’ve done in the Finder. If you spent the time to move clips into specific folders or you assigned color-coded Finder tags, then this information can be used when importing clips into FCP X. The import dialogue gives you the option to “leave files in place” and to use Finder folders and tags to automatically create corresponding Keyword Collections. Camera files that were organized into camera/date/card folders will automatically be placed into Keyword Collections that are organized in the same fashion. If you assigned clips with Mary, John, and Joe to have red, blue, and green tags for each person, then you’ll end up with those clips automatically placed into Keyword Collections named red, blue, and green. Once imported, simply rename the red, blue, and green Collections to Mary, John, and Joe.

df1415_organize_12

The third level of clip organization is Smart Collections. Use these to automatically filter clips based on the criteria that you set. With the release of FCP X version 10.2, Smart Collections have been moved from the Event level (10.1.4 or earlier) to the Library level – meaning that filtering can occur across multiple Events within the Library. By default, new Libraries are created with several preset Smart Collections that can be used, deleted, or modified. Here’s an example of how to use these. When you sync double-system sound clips or multiple cameras, new grouped clips are created – Synchronized Clips and Multicam Clips. These will appear in the Event along with all the other source files, which can be unwieldy. To focus strictly on these new grouped clips, create a Smart Collection with the criteria set by type to include these two categories. Then, as new grouped clips are created, they will automatically be filtered into this Smart Collection, thus reducing clutter for the editor.

Playing nice with others

df1415_organize_9Final Cut Pro X was designed around a new paradigm, so it tends to live in its own world. Most professional editors have the need for a higher level of interoperability with other applications and with outside vendors. To aid in these functions, you’ll need to turn to third party applications from a handful of vendors that have focused on workflow productivity utilities for FCP X. These include Intelligent Assistance/Assisted Editing, XMiL, Spherico, Marquis Broadcast, and Thomas Szabo. Their utilities make it possible to go between FCP X and the outside world, through list formats like AAF, EDL, and XML.

df1415_organize_11Final Cut’s only form of decision list exchange is FCPXML, which is a distinctly different data format than other forms of XML. Apple Logic Pro X, Blackmagic Design DaVinci Resolve and Autodesk Smoke can read it. Everything else requires a translated file and that’s where these independent developers come in. Once you use an application like XtoCC (formerly Xto7) from Intelligent Assistance to convert FCPXML to XML for an edited sequence, other possibilities are opened up. The translated XML file can now be brought into Adobe Premiere Pro or FCP 7. Or you can use other tools designed for FCP 7. For instance, I needed to generate a print-out of markers with comments and thumbnail images from a film, in order to hand off notes to the visual effects company. By bringing a converted XML file into Digital Heaven’s Final Print – originally designed with only the older Final Cut in mind – this became a doable task.

df1415_organize_13Thomas Szabo has concentrated on some of the media functions that are still lacking with FCP X. Need to get to After Effects or Nuke? The ClipExporter and ClipExporter2 applications fit the bill. His newest tool is PrimariesExporter. This utility uses FCPXML to enable batch exports of clips from a timeline, a series of single-frame exports based on markers, or a list of clip metadata. Intelligent Assistance offers the widest set of tools for FCP X, including Producer’s Best Friend. This tool enables editors to create a range of reports needed on most major jobs. It delivers them in spreadsheet format.

Understanding the thought processes behind FCP X and learning to use its powerful relational database will get you through complex projects in record time. Better yet, it gives you the confidence to know that no editorial stone was left unturned. For more information on advanced workflows and organization with Final Cut Pro X, check out FCPworks, MacBreak Studio (hosted by Pixel Corps), Larry Jordan, Lynda.com and Ripple Training.

For those that want to know more about the nuts and bolts of the post production workflow for feature films, check out Mike Matzdorff’s “Final Cut Pro X: Pro Workflow”, an iBook that’s a step-by-step advanced guide based on the lessons learned on Focus.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

A Deeper Dive into Lumetri Color

df2715_lumetri_1_sm

With the introduction of Premiere Pro CC 2015, Adobe altered how color correction can be handled within its editing application. The addition of the Lumetri Color effect puts a very powerful and intuitive color correction tool at the editor’s fingertips. I touched on some of its capabilities with SpeedGrade look files in a previous post, but now I’d like to dive into a deeper explanation of the features of Lumetri Color.

Previously in Premiere Pro CC 2014, the Lumetri effect was the conduit between grades in SpeedGrade and Premiere Pro. When you sent a sequence to SpeedGrade CC via Direct Link, the correction done there would show up back in Premiere Pro CC as a self-contained Lumetri effect applied to the clip or an adjustment layer. You could add more effects to the clip, but not edit the Lumetri effect itself in Premiere Pro. If you bounced back into SpeedGrade, then you had further edit control to change the settings from the earlier SpeedGrade session.

Now in Premiere Pro CC 2015, that previous method has been altered. When a Lumetri Color effect is added in the Premiere Pro CC timeline, that is no longer editable when you send it to SpeedGrade CC via Direct Link. Any grading added in SpeedGrade is in addition to the Lumetri Color effect. When you go back to Premiere Pro, those corrections will show up as a SpeedGrade Custom group at the bottom of the Lumetri Color effect stack. It is a separate, self-contained, uneditable correction applied to the clip. It can only be disabled if desired. In other words, Lumetri Color adjustments made in Premiere Pro are separate and apart from any color corrections done in SpeedGrade.

You can apply a Lumetri Color effect in two ways. The first, traditional way is to drag-and-drop the filter from the Effects palette (Color Correction folder) onto the clip or adjustment layer. The new, CC 2015 way is to select the Color workspace, which automatically reveals the Lumetri Color panel and the new, real-time Lumetri scopes. If you change any setting in the panel, it immediately applies a Lumetri Color effect to that clip. Color corrections can be made either in the Lumetri panel or in the standard Effects Control panel. If you don’t like the Lumetri Color effect or panel, you can still use the other color correction filters, like the Three-Way Color Corrector, Luma Curve, etc. These options have not been removed. (Click on any image for an expanded view.)

Master Clip Effects

df2715_lumetri_2_smSince CC 2014, Premiere Pro has enabled Master Clip effects. These are source-side settings and any change made as a Master Clip effect will affect all instances of that clip throughout the timeline. This is important with camera raw files, like CinemaDNG or REDCODE raw, because there are color metadata adjustments that can be made at the point where the raw image is encoded into RGB video. This is in addition to any color corrections made in the Lumetri Color panel, another filter, or in SpeedGrade. Previously these controls were accessed as a right-click contextual menu option called Source Settings.

With CC 2015, source setting adjustments have been moved to the Effects Control panel. At the top of the panel you’ll see the clip name appear twice – once as the master clip (left) and once in the sequence (right). The sequence portion has all the usual controls, like motion, opacity, time remapping, and any applied filters. The master clip portion will show all the source color controls. In the case of RED files, you’ll find the full range of RED controls made available from their SDK. For CinemaDNG files, such as from Blackmagic cameras, the options are limited to exposure, temperature and tint. You should make any necessary camera raw adjustments to these clips here, before applying Lumetri Color effects.

In addition to raw adjustments, Lumetri Color effects can also be applied as Master Clip effects and/or as timeline effects. The Lumetri Color panel also displays the clip name twice – master clip (left) and sequence clip (right). Generally you are going to make your corrections to sequence clips, however, some common settings, like adding a Log-to-Rec709 LUT might be best done as a Master Clip effect. Just understand that adjustments in the Lumetri Color panel can be applied to either or both sides, but that Master Clip effects will automatically ripple to other instances of that same clip elsewhere on the timeline. When you make changes to the sequence side (right), you are only altering that one location on the timeline.

The Lumetri Color Panel

df2715_lumetri_8_smThe Lumetri Color panel is organized as a stack of five control groups – Basic Correction, Creative, Curves, Color Wheels and Vignette. The controls within each group are revealed when you click on that section. You can enable or disable a group, but you can’t change the order of the stack, which flows from Basic out through Vignette. This control method and the types of controls offered are very similar to Adobe Lightroom’s Develop page. Its control groups include Basic, Tone Curve, HSL/Color/B&W, Split Toning, Detail, Lens Corrections, Effects and Camera Calibration. There are more groups in Lightroom simply because there are more image attributes available to be adjusted within a still photo image.

Basic Correction 

df2715_lumetri_3_smThe Basic Correction group is where you’ll perform the majority of your primary color grading. It includes a pulldown for input LUTs (camera-specific color transforms), white balance, tone and saturation. White balance adjusts temperature and tint. When you move the temperature slider it increases or decreases red versus blue in an inverse relationship of one to the other, with minimal change of green. Sliding tint alters red and blue together versus green.

Tone gives you control over the luminance of the image with sliders for exposure, contrast, highlights, shadows, whites and blacks. White and black controls move the top and bottom ends of the image up or down toward clip points, while the highlight and shadow sliders adjust the upper and lower portions of the image within the parameters set by the white and black sliders. The highlight and shadow sliders would be what you use to see more or less detail within the bright or dark areas of the image.

Creative 

df2715_lumetri_4_smThe Creative group is where stylistic adjustments are made, including the addition of creative “looks” (.look or .cube LUTs).  There are sliders for the intensity of the LUT, plus adjustment controls for a faded film effect, sharpening, vibrance and saturation. Finally, there are shadow and highlight tint controls with a balance slider to change the crossover threshold between them.

The faded film slider moves the black level you’ve established for the image higher for elevated blacks, but without opening any shadow detail. If you slide the control more to the right it will also compress the highlights, thus creating an overall flatter image. The sharpen slider blurs or enhanced detail in the image. Saturation uniformly increases the intensity of all chroma. Vibrance is a smart tool that increases the saturation of the more muted colors and has less change on the already-intense colors. The highlight and shadow tint controls shift the color balance of those portions of the image towards any area on the color wheel. The tint balance slider changes how much much of the image is considered to be the shadow or highlight range. For example, if you move the slider all the way to the left, then all of the image is affected by the highlight tint wheel only.

Curves

df2715_lumetri_5_smThe Curves group includes both standard RGB curves and a color wheel for control of the hue/saturation curve. The RGB curves offer four dots – white (overall control), plus red, green and blue for individual control over each of the R, G or B curves. The hue/sat curve is really a vector-based secondary color control and is akin to Lightroom’s HSL group. However, in the Lumetri Color panel a wheel control is used.

If you select one of the six color vector dots under the hue/sat curve wheel, then three control points are added along the circular curve. The center point is the color chosen and the points to the left and right establish a boundary. Pull the center point up or down to increase or decrease the saturation of the curve. Pulling the point left or right doesn’t change the hue of that color. The wheel works like a “hue vs. sat” curve and not as “hue vs. hue” when you compare it to the way in which other color correction tools operate. If I select red, I can increase or decrease the intensity of red, but pulling the control point towards orange or magenta doesn’t shift the red within the image itself towards that hue. You can also select one or more points along the curve without selecting a vector color first and make more extensive adjustments to the image.

Color Wheels 

df2715_lumetri_6_smColor Wheels is the next control group and it functions as an standard three-way corrector would. There are luma sliders and a color wheel for shadows, midtones and highlights. Moving the color wheel control effectively adds a color wash to that portion of the image instead of shifting the color balance. If you shift a wheel towards blue, the blue portion of the parade signal on a scope is increased, but red and green are not lowered in a corresponding fashion. Therefore, these wheels act as secondary color controls, which explains why Adobe placed them further down in the stack.

Vignette 

df2715_lumetri_7_smThe last group is Vignette and it works in much the same fashion as the Post-Crop Vignetting control in Lightroom. There are sliders for amount, midpoint, roundness and feather. In general, it acts more like a photographic vignette or one that’s a result of a lens artifact – and less like masks that you typically add in creative grading for vignette effects. Moving the amount slider controls the lightness or darkness of the vignette (yes, you can have a white vignette), but it only changes the outer edges of the frame. You cannot invert the effect. Midpoint moves the vignette edge farther into or out of the frame. Roundness adjusts the aspect ratio of the vignette and feather controls the softness of the edge.

There is no position control to move the vignette away from dead center. While the vignette group is useful for “pinching in the edges of the frame” (as a DP friend of mine is fond of saying), it’s less useful for directing the viewer’s attention. That’s the “power windows” approach, which I often use in tools like Resolve, Color, or SpeedGrade. There are other ways to achieve that inside of Premiere Pro, but just not self-contained within a single instance of the Lumetri Color effect.

It’s clear that Adobe has added a very deep toolset within this single effect and its corresponding control panel. For most color correction sessions, you can pretty well get everything done using just Lumetri Color. I believe most editors prefer to use a comprehensive grading tool that allows them to stay within the confines of the editing application. Lumetri Color within Premiere Pro CC 2015 brings that wish to reality without the need for roundtrips or third-party color correction filters.

©2015 Oliver Peters

Adobe Premiere Pro CC 2015

df3015_PremierePro2015_Workspace_Editing

To reinforce the value of the Creative Cloud subscription, Adobe continues to improve its core video and design products, but is also expanding the implementation of mobile-to-desktop and cloud workflows. The Creative Cloud 2015 video products were previewed at NAB and released this summer.

Mobile-to-desktop

Incorporation of mobile products into the production pipeline has become an important theme for Adobe. For Premiere Pro CC users, this primarily involves two products: Premiere Clip and Adobe Hue CC. Premiere Clip is a lightweight video editor for smartphones. Shoot your video on your phone and start cutting. Now Premiere Pro allows you to import Premiere Clip projects so you can continue cutting there. Media assets and projects can be moved among systems via Creative Cloud Libraries, powered by Adobe CreativeSync. With a Creative Cloud subscription you can access your own library, as well as shared libraries created by other users.

df3015_AdobeHueCC_editAdobe Hue CC supports the new color workflow within Premiere Pro CC. This smartphone application was previewed at NAB under the code name “Project Candy”. It will analyze the color tonality of any photo in 3D color space on your smartphone and turn that into a 3D LUT (color look-up table). Adobe Hue CC displays this analysis in the form of floating color bubbles over the image. You can rotate the cloud of bubbles on your smartphone screen to change the relative values of the selected colors. When you’re happy with the choice, this is saved as a 3D LUT to your Creative Cloud Library. Back on your laptop or desktop in Premiere Pro CC, access this LUT through the Creative Cloud Library and apply it as a “look” using Adobe’s new color controls.

New color workflow

The most visible addition to Premiere Pro CC 2015 is the new Lumetri Color panel. If you are familiar with Adobe Lightroom or SpeedGrade CC, then you’ll instantly recognize the similarities. It combines several color grading functions into a single, multi-tabbed interface panel. These controls are accessible through either the standard Effect Control panel or the separate Lumetri Color panel. The best part is that you can keyframe all of the functions. With either control panel you get a set of task-specific color wheels and curves. When the color workspace is activated, the display automatically docks the Lumetri Color panel, along with a new set of high-resolution, real-time videoscopes brought over from SpeedGrade.

df3015_Premiere_LumetriPanel_CurvesHueSaturationThere are two points within Lumetri Color to introduce LUTs. For example, in the Basic Correction tab’s pulldown menu, you can add a log-to-rec709 color transform LUT. Then in the Creative tab’s pulldown, add a stylized look. Premiere Pro CC comes with a number color transform and custom look files created by Adobe and LookLabs (SpeedLooks). Some of these, like the SpeedLooks options, work in two steps for the best results. For instance, if you were applying the SpeedLooks Blue Ice creative LUT to an ARRI Alexa log-C file, you would also need to use the SpeedLooks profile for ARRI cameras. Both generic .cube and Adobe’s .look formats work, so if you’ve purchased other LUT collections, like Osiris, Rocket Rooster, SpeedLooks, Koji, or others, then these will work with Premiere Pro CC. I created a set of SpeedGrade Look files last May and these can be easily accessed and applied inside Premiere Pro from the new Lumetri Color panel.

Editorial enhancements

There are a number of improvements that editors will appreciate. Workspace selections are now grouped across the top of the viewers. They are still available as pulldowns, but by having them grouped across the top, it’s easy to change between layouts that have been organized for editing, color, effects, audio, etc. These presets can be customized according to your needs.

One new marquee effect is Morph Cut, which is intended to make jump cuts in interviews appear seamless. This transition is similar to the FluidMorph effect available in Avid Media Composer. Editors cutting talking-head corporate videos and documentaries are frequently challenged to assemble cogent soundbites from sentence fragments – the so-called “frankenbite”. The inevitable jump cuts in the interviewee’s video are either left to jump or are covered with B-roll cutaway shots. When you apply a Morph Cut transition, Adobe’s warp stabilizer technology is used to analyze the video and create new in-between frames for a seamless transition across the cut.

In actual practice Morph Cut isn’t a panacea for all situations. If the frame size and position matches, the person is largely in the exact same spot, and they paused mid-sentence at the cut, then Morph Cut works quite well. However, if the camera has reframed, the person has their head turned at either the out or in-point of the cut but not the other, or they are still quickly talking through the cut, then the result isn’t very pleasing. Morph Cut requires analysis before being applied, which can proceed in the background.

A few of the less obvious improvements include trimming and timeline scrolling. These came with prior versions, but are still worth noting. You can now loop the trim window and make trim adjustments, which are dynamically updated. You can also JKL-play the middle of the cut or either side of the cut in the trim window to make a direct “double-roller” or “single-roller” trim. The point at which you stop the playback is the point to which the cut is then updated. The timeline will scroll smoothly or page as you play, depending on your preference. Auto-selection of clips is new with Creative Cloud 2015. As you move through the timeline, the playhead auto-selects the clips that it is parked over, based on the enabled target tracks. This is a handy feature, but it’s always on, unless you deselect the target tracks containing your video clips.

Interoperability

df3015_AfterEffects_FaceTracker_DetailedTrackingAdobe’s strength has always been its interoperability among the applications. Dynamic and/or Direct Links to Adobe After Effects CC, Adobe Audition CC, Adobe Media Encoder CC, and SpeedGrade CC make it easy to use Premiere Pro CC as the central hub in your workflow. After Effects got a huge update with CC 2015. I won’t go into depth, since this is mainly a Premiere Pro review, however, for editors the most important thing is the performance bump. Playback in After Effects is now as easy as a spacebar tap. This will be in near real-time after caching, complete with audio. You can make dynamic changes without stopping playback. As you loop the playback, these changes are quickly re-cached. The bottom line for editors is that After Effects now finally becomes a more interactive tool that fits with the temperament and workflow of most editors.

It’s not new with this version, but another workflow improvement is Premiere Pro’s Render and Replace command. When you send a set of clips from Premiere Pro to After Effects using Dynamic Link, those clips are replaced with an After Effects composition on the timeline. Until rendered, the After Effects composition is always “live” and negatively affects Premiere Pro’s performance. If you have a lot of compositions in the timeline, it can become bogged down. With Render and Replace, the “live” composition is replaced with rendered, “flattened” media. You are no longer having to access dynamic After Effects compositions, thus returning real-time playback to normal. Thanks to Adobe’s linking, you can still choose to edit that rendered file, which automatically sends you back to the original After Effects composition.

Interoperability between Premiere Pro CC and SpeedGrade CC has changed. Adobe had previously added Direct Link, which sends the Premiere Pro timeline to SpeedGrade. In the CC 2014 versions, color corrections applied in SpeedGrade show up as a Lumetri effect applied to the clip or adjustment layer when you send it back to Premiere Pro. The addition of the Lumetri Color panel in CC 2015 creates Lumetri Color effects in the Premiere Pro timeline, but these are not editable inside of SpeedGrade. The same is true going back to Premiere Pro.

The performance of SpeedGrade CC 2015 varies on my two Macs. It’s very sluggish when using the Direct Link path on the 2009 Mac Pro with a Sapphire 7950 graphics card. But when I run it on my Retina MacBook Pro with the built-in NVIDIA card, it’s an entirely different story. I don’t know if that’s an AMD versus NVIDIA issue, but whatever the reason, newer software runs best on newer hardware configurations. Yet, Premiere Pro seems about the same.

During the testing period, when I had installed CC 2015 preview versions alongside CC 2014 applications, SpeedGrade was extremely unstable on both Macs. Fortunately, now that the release versions are out, I’m glad that Adobe fixed these problems. It’s noteworthy that the CC 2015 update replaces all previous versions, so maybe they found that running multiple versions caused problems. It now works likes it’s supposed to. Nevertheless, with the Lumetri Color panel covering 90% of what nearly any editor would want, there seems less justification to use the SpeedGrade roundtrip, when you can get nearly everything done right inside Premiere Pro.

Other

df3015_CA_big_tracking_but_no_timelineSince After Effects is integral for many editors, a few more features are worth noting. New in CC 2015 is a Face Tracker. This is a simple mask based on identifying points on the face, like eyes, pupils, mouth and nose. The Face Tracker will follow the shot’s or person’s movement. It will even track exaggerated mouth movements without frame-by-frame adjustments. This is a very useful tool for locking an object to head movement or facial blurs to protect identity.

The Face Tracker ties into a new Adobe application – Adobe Character Animator. As the name implies, this is an application that enables you to create 2D character animation. Facial tracking technology can be used to animate the characters according to prerecorded tracking data, as well as to live, real-time tracking. For example, a webcam could be used to animate the characters live, complete with lip-sync. Animation passes can be recorded and edited for a complete production featuring multiple interactive characters.

This release has a number of large and small upgrades that will make editors and compositors quite happy. I like the direction Adobe has taken. It just reiterates that the designers are working hard to integrate user input and build upon the professional momentum that Adobe has earned to date.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

The FCP X – RED – Resolve Dance II

df2415_roundtrip2_sm

Last October I wrote about the roundtrip workflow surrounding Final Cut Pro X and Resolve, particularly as it relates to working with RED camera files. This month I’ve been color grading a small, indie feature film shot with RED One cameras at 4K resolution. The timeline is 1080p. During the course of grading the film in DaVinci Resolve 11, I’ve encountered a number of issues in the roundtrip process. Here are some workflow steps that I’ve found to be successful.

Step 1 – For the edit, transcode the RED files into 1080p Apple ProRes Proxy QuickTime movies baking in camera color metadata and added burn-in data for clip name and timecode. Use either REDCINE-X Pro or DaVinci Resolve for the transcode.

Step 2 – Import the proxies and double-system audio (if used) into FCP X and sync within the application or use Sync-N-Link X. Ideally all cameras should record reference audio and timecode should match between the cameras and the sound recorder. Slates should also be used as a fall-back measure.

Step 3 – Edit in FCP X until you lock the cut. Prepare a duplicate sequence (Project) for grading. In that sequence, strip off (detach and remove) all audio. As an option, you can create a mix-down track for reference and attach it as a connected clip. Flatten the timeline down to the Primary Storyline where ever possible, so that Resolve only sees this as one track of video. Compound clips should be broken apart, effects should be removed, and titles removed. Audition clips should be finalized, but multicam clips are OK. Remove effects filters. Export an FCPXML (version 1.4 “previous”) list. You should also export a self-contained reference version of the sequence, which can be used to check the conform in Resolve.

Step 4 – Launch Resolve and make sure that the master project settings match that of your FCP X sequence. If it’s supposed to be 1920×1080 at 23.976 (23.98) fps, then make sure that’s set correctly. Resolve defaults to a frame rate of 24.0fps and that won’t work. Locate all of your camera original source media (RED camera files in this example) and add them to your media bin in the Media page. Import the FCPXML (1.4), but disable the setting to automatically load the media files in the import dialogue box. The FCPXML file will load and will relink to the RED files without issue if everything has gone correctly. The timeline may have a few clip conflicts, so look for the little indicator on the clip corner in the Edit window timeline. If there’s a clip conflict, you’ll be presented with several choices. Pick the correct one and that will correct the conflict.

Step 5 – At this point, you should verify that the files have conformed correctly by comparing against a self-contained reference file. Compound clips can still be altered in Resolve by using the Decompose function in the timeline. This will break apart the nested compound clips onto separate video tracks. In general, reframing done in the edit will translate, as will image rotation; however, flips and flops won’t. To flip and flop an image in FCP X requires a negative X or Y scale value (unless you used a filter), which Resolve cannot achieve. When you run across these in Resolve, reset the scale value in the Edit page inspector to normal from that clip. Then in the Color page use the horizontal or vertical flip functions that are part of the resizing controls. Once this is all straight, you can grade.

Step 6 option A – When grading is done, shift to the Deliver page. If your project is largely cuts-and-dissolves and you don’t anticipate further trimming or slipping of edit points in your NLE, then I would recommend exporting the timeline as a self-contained master file. You should do a complete quality check the exported media file to make sure there were no hiccups in the render. This file can then be brought back into any NLE and combined with the final mixed track to create the actual show master. In this case, there is no roundtrip procedure needed to get back into the NLE.

Step 6 option B – If you anticipate additional editing of the graded files – or you used transitions or other effects that are unique to your NLE – then you’ll need to use the roundtrip “return” solution. In the Deliver page, select the Final Cut Pro easy set-up roundtrip. This will render each clip as an individual file at the source or timeline resolution with a user-selected handle length added to the head and tail of each clip. Resolve will also write a corresponding FCPXML file (version 1.4). This file will retain the original transitions. For example, if you used FCP X’s light noise transition, it will show up as a dissolve in Resolve’s timeline. When you go back to FCP X, it will retain the proper transition information in the list, so you’ll get back the light noise transition effect.

Resolve generates this list with the assumption that the media files were rendered at source resolution and not timeline resolution. Therefore, even if your clips are now 1920×1080, the FCPXML represents these as 4K. When you import this new FCPXML back into FCP X, a spatial conform will be applied to “fit” the files into the 1920×1080 raster space of the timeline. Change this to “none” and the 1080 media files will be blown up to 4K. You can choose to simply live with this, leave it to “fit”, and render the files again on FCP X’s output – or follow the next step for a workaround.

Step 7 – Create a new Resolve project, making sure the frame rate and timeline format are correct, such as 1920×1080 at 23.976fps. Load the new media files that were exported from Resolve into the media pool. Now import the FCPXML that Resolve has generated (uncheck the selection to automatically import media files and uncheck sizing information). The media will now be conformed to the timeline. From the Edit page, export another FCPXML 1.4 for that timeline (no additional rendering is required). This FCPXML will be updated to match the media file info for the new files – namely size, track configuration, and frame rate.

At this stage, you will encounter a second serious flaw in the FCP X/Resolve/FCP X roundtrip process. Resolve 11 does not write a proper FCPXML file and leaves out certain critical asset information. You will encounter this if you move the media and lists between different machines, but not if all of the work is being done on a single workstation. The result will be a timeline that loads into FCP X with black clips (not the red “missing” icon). When you attempt to reconnect the media, FCP X will fail to relink and will issue an “incompatible files” error message. To fix the problem, either the colorist must have FCP X installed on the Resolve system or the editor must have Resolve 11 installed on the FCP X system. This last step is the one remaining workaround.

Step 8 option A – If FCP X is installed on the Resolve machine, import the FCPXML into FCP X and reconnect the media generated by Resolve. Then re-export a new FCPXML from FCP X. This new list and media can be moved to any other system. You can move the FCP X Library successfully, as well.

Step 8 option B – If Resolve is installed on the FCP X machine, then follow Step 7. The new FCPXML that you create there will load into FCP X, since you are on the same system.

That’s the state of things right now. Maybe some of these flaws will be fixed with Resolve 12, but I don’t know at this point. The FCPXML list format involves a bit of voodoo at times and this is one of those cases. The good news is that Resolve is very solid when it comes to relinking, which will save you. Good luck!

©2015 Oliver Peters

Building a Free FCP X Color Correction Filter

df2315_opcolor_1One nice aspect of the symbiotic relationship between Final Cut Pro X and Motion is that Motion can be used to create effects, transitions, titles and generators for use in FCP X. These are Motion Templates and they form the basis for the creation of nearly all third-party effects filters, both paid and free. This means that if you learn a bit about Motion, you can create your own custom effects or make modifications to the existing ones supplied with FCP X. This has become very easy to do in the newest versions (FCP X 10.2.1 and Motion 5.2.1).

I decided to build a color correction filter that covered most of the standard adjustments you need with the usual types of footage. There are certainly a number of really good color correction/grading filters already on the market for FCP X. Apple’s own color board works well and with 10.2 has been broken out as a normal effects filter. However, a lot of folks don’t like its tab/puck/swatch interface and would still rather work with sliders or color wheels. So as an experiment, I built my own color correction filter for use with FCP X – and you may download here and use it for free as well.

df2315_opcolor_4_smLet me point out that I am no Motion power user. I have nowhere near the skills of Mark Spencer, Simon Ubsdell or Alex Gollner when it comes to using Motion to its fullest. So all I’ve done is combine existing Motion filters into a single combined filter with zero modifications. But that’s the whole point and why this function has so much potential. A couple of these individual filters already exist singly within FCP X, but Motion has a lot more to choose from. Once you launch Motion, the starting point is to open a new Final Cut Effects project from the Motion project browser. This will default to a blank composition ready to have things added to it. Since I was creating a color correction filter, all I needed to do was select the existing Motion filters to use from the Library browser and drag-and-drop the choices into the composition.

df2315_opcolor_5I decided to combine Brightness, Contrast, Color Balance, Hue/Saturation and Tint, which were also stacked in that exact order. The next step in the process was to determine the state of the filter when you apply it and which parameters and sliders to publish. Items that are published, such as a slider, will show up in the inspector in FCP X and can be adjusted by the editor. In my case, I decided to publish every parameter in the stack. To publish, simply click on the right side edge of each parameter line and you’ll find a pulldown selection that includes a publish/unpublish toggle. Note that the order in which you click the publish commands will determine the order of how these commands are stacked when they show up inside FCP X. To make the most sense, I followed a straight sequence order, top to bottom.

df2315_opcolor_3_smYou can also determine the starting state when you first apply or preview the effect.  For example, whether a button starts out enabled or disabled. In the case of this filter, I’ve enabled everything and left it at a neutral or default value, with the exception of Tint. This starts in the ‘off’ position, because I didn’t want a color cast to be applied when you first add the filter to a clip. Once everything is set-up, you simply save the effect to a desired location in the Motion Templates folder. You can subsequently open the Motion project from there to modify the effect. When it’s saved again, the changes are updated to the filter in FCP X.

If you’ve downloaded my effects filter, unzip the file and follow the Read Me document. I’ve created an “Oliver FX” category and this complete folder should be placed into the User/Movies/Motion Templates/Effects folder on your hard drive.df2315_opcolor_2

Applying the filter inside Final Cut Pro X is the same as any of the other effects options. It has the added benefit that all parameters can be keyframed. The Color Balance portion works like a 3-way color corrector, except that it uses the OS color picker wheels in lieu of a true 3-color-wheel interface. As a combination of native filters, performance is good without taxing the machine.

UPDATE (12 June 2015) : I have added one addition filter into the download file. The second filter is called “Oliver DVE” and designed to give you a full set of transform controls that include XYZ rotation. It comes from the transform control set included with Motion. This provides you with the equivalent of a 2.5D DVE, which is not available in the default control set of FCP X.

UPDATE 2 (15 June 2015) : These filters are not backward compatible. They will work in FCP X 10.1.2 and Motion 5.1.2 and forward (hopefully), but not in earlier versions. That’s due to technology changes between these versions. If you downloaded these prior to June 15, for FCP X 10.1.2 or 10.1.4 and they aren’t working, please download again. I have modified the files to work in FCP X 10.1.2 and later. Thank you.

Download the free “Oliver Color” and “Oliver DVE” filters here. My previously-created, free FCP X color board presets may be found here.

©2015 Oliver Peters