Apple Final Cut Pro X 10.4

December finally delivered the much-anticipated simultaneous release of new versions of Apple Final Cut Pro X, Motion, and Compressor – all on the same day as the iMac Pro officially went on sale. In the broader ecosystem, we also saw updates for macOS High Sierra, Logic Pro X, Pixelmator Pro, and Blackmagic Design DaVinci Resolve.

Final Cut Pro X (“ten”), version 10.4 is the fifth major release of Apple’s professional NLE in a little over six years. There are changes under the hood tied to technologies in High Sierra (macOS 10.13), which won’t get much press, but are very important in the development and operation of an application. This version will still run on a wide range of recent and older Macs. The minimum OS requirement is 10.12.4, but 10.13 or later is recommended. There are four new, marquee features in this release: advanced color correction tools, 360° editing, HDR (wide gamut) color space support, and HEVC/H.265 codec support for editing and encoding.

New advanced color tools

Final Cut Pro X was first launched with a color correction tool called the color board. It substituted sliders on a color swatch for the standard curves and color wheel controls that editors had been used to. While the color board was and is effective, as well as a bit deceptive in what you can accomplish, it was an instant turn-off for many. The lack of a more advanced color correction interface opened the field for third party color correction plug-in developers who came up with some great tools. With the release of FCPX 10.4, it’s hard for me to see why FCPX diehards would still buy a color correction plug-in. Yet, I have heard from at least one plug-in developer that their color corrector plug-in sales are staying stable. Clearly users want choice and that’s a good thing.

With this update, you’ve gained three new, native color tools, including color wheels, curves, and hue vs. saturation curves. All are elegantly designed, operate quite fluidly, and generally mimic what you can do in DaVinci Resolve. However, the color board didn’t go away however. There’s a preference setting for which of these four color tools is the default effect when first applying color correction (CMD+6).

Once you start color correcting, you can add more instances of any of these four tools in any combination. Final Cut Pro X sports robust performance, so you can apply several layers of correction to a clip and still have real-time playback without rendering. There are also additional keyboard commands to quickly step through effects or clips on your timeline. While not quite as fluid of a grading workflow as you’d have in a true color correction application, like Resolve, you can get pretty close with some experience. My biggest beef is that you are limited to the controls being locked within the inspector pane. You can’t move the controls around and there is no special color correction workspace. So for me, the ergonomics are poor. In my testing, I’ve also hit some flaws in how the processing is done (more on that in a future post). Ironically the color board actually seems to achieve more accurate correction than the color wheels.

There are a few quirks. Previously created presets for the color board will be converted into color preset effects, which now appear in the effects browser. This enables you to preview a color preset applied to a clip by skimming over the effect thumbnail. Unfortunately, I found this conversion didn’t always work. On a Sierra machine (10.12), the older presets were automatically converted after waiting a few minutes; however, nothing happened on a High Sierra machine (10.13). I eventually resorted to copying my converted effects presets from the Sierra Mac over to the High Sierra Mac. I suspect, that because the High Sierra update automatically reformats the internal SSD drive to the new Apple File System (APFS), this conversion process is somehow impeded. Of course, if you don’t already have any existing custom presets, then it’s not an issue.

(You can check out my previously-created color presets for instructions and downloads here.)

There is no control surface support yet, although future support for third party color correction controllers has been alluded to. It would be nice to see support for Tangent or Avid panels at the very least. There’s a new FCPXML version (1.7) that includes this new color metadata; however, it doesn’t seem to be imported into the newest version of Resolve. It’s possible that color metadata in the FCPXML file is only intended for FCPX-to-FCPX transfers and not round tripping to other applications.

360° editing

Let me say up front that this doesn’t hit my hot button. It’s an area where Apple is playing catch-up to Adobe. Quite frankly, for both of these companies, it only appeals to a small percentage of users. Not all 360° formats are supported. Your footage must be equirectangular (stitched panorama), in order that FCPX can properly correct its display. Nevertheless, if you do work on 360° productions, then FCPX provides you a nice tool kit.

You can set up your timeline sequence for monoscopic or stereoscopic 360° editing. Once set up, simply open a separate 360° viewer, side-by-side to the normal viewer. When you do this, you’ll see the uncorrected image on the right and the adjusted point-of-view image on the left. What’s really cool, is that you can play the timeline and actively navigate your view of the content within of the 360° viewer, without ever stopping playback. Plus I’m talking about 4K material here! Clearly the engineers have tweaked the performance and not just integrated a plug-in.

There are also a set of custom effects designed for seamless use on 360° images. For example, if you apply a standard blur, there will be a visible seam where the left and right edges meet. If you apply a 360° blur effect, then the image and effect are properly blended. If you want to get the full effect, just attach an HTC Vive VR headset to view clips in full 360°. Want to test this, but don’t have any footage? A quick web search will provide a ton of downloadable, equirectangular clips to play with.

Wide gamut / high dynamic range (HDR)

Apple is trying to establish leadership with the integration of workflows to support HDR editing. I suspect that their ultimate goal is proper HDR support for Apple TV 4K and the iPhone X. The state of HDR today is very confusing without any real standards. There’s DolbyVision and HDR10, an open standard. The latter leaves the actual implementation up to manufacturers, while Dolby licenses its technology with tight specs. The theoretical DolbyVision brightness standard is 10,000 nits (cd/m2), but their current target is only 4,000 nits. HDR10 caps at 1,000 nits. Current consumer TV sets run in the 300 to 500 nit range with none exceeding 1,000 nits. Finally, projected brightness in movie theaters is even lower.

To work in HDR within Final Cut Pro X, first set up the FCPX Library as wide instead of standard gamut. Then set the Project (sequence) to one of four standards: Rec 709 (standard dynamic range), Rec 2020, Rec 2020 PQ, or Rec 2020 HLG. The first Rec 2020 mode simply preserves the full dynamic range of log-encoded camera files when FCPX applies its LUTs. The PQ and HLG options are designed for DolbyVision and/or HDR10 mastering. HDR tools are provided to go between color spaces, such as mastering in Rec 2020 PQ and delivering in Rec 709 (consult Apple’s workflow document). However, it is only in the Rec 2020 PQ color space that the FCPX scope will display in nits, rather than IRE. When set to nits, the scale is 0 to 10,000 nits instead of 0 to 120 IRE.

To edit in one of these wide gamut color spaces, set your preferences to display HDR in raw values. Then Final Cut interacts with the color profile of the monitor through macOS to effectively dim the viewer image for this new color space. However, this technique is not applied to the filmstrips and thumbnail images in the browser, which will appear with blown out levels unless you manually override the colorspace setting for each clip. If your footage was shot with camera raw or log-encoding, using a RED, ARRI or similar camera, then you are ready to work in HDR today.

It’s critical to note that no current computer display or consumer flat panel will give you an accurate HDR image to grade by. This includes the new iMac Pro screens. You will need the proper AJA i/o hardware and a calibrated HDR display to see a proper HDR image. Even then, it’s still a question of which HDR levels you are trying to master to. For example, if you are using the scope in FCPX with a brightness level up to 10,000 nits, but your target display can only achieve 1,000 nits, then what good is the reading on the scope? We are still early in the HDR process, but I’m concerned that FCPX 10.4 will give users a false impression of what it really takes to do HDR properly.

HEVC / H.265

You can now import iMovie for iOS projects into FCPX 10.4.  Support for the H.265 (HEVC) codec has been added with this release, but you’ll need to be on High Sierra. If you shot video with an iPhone X and started organizing it in iMovie on the phone, then that video may have used the H.265 codec. Now you can bring that into FCPX to continue the job.

Going the other way will require Compressor encoding. HEVC is also the required format to send HDR material to the web. Apple is late to the game in H.265 support, as Sorenson and Adobe users have been able to do that for a while. I tested H.265 encoding of short clips in Compressor on my mid-2014 Retina MacBook Pro and it was extremely slow. There was no issue with H.264 encoding. The same H.265 test in Adobe Media Encoder – even when it was uprezzing a 1080p file to 4K – was significantly faster than Compressor.

Final thoughts

For current users. When you update to Final Cut Pro X 10.4, please remember that it will update each FCPX library file that you open afterwards. Although this has generally been harmless for most users, it’s best to follow some precautions. Zip your 10.3 (or earlier) version of the application and move that .zip file out of the applications folder before you update. Archive all of your existing Final Cut libraries. This way you can find your way back, in case of some type of failure.

Final Cut Pro X 10.4 is a solid upgrade that will have loyal FCPX users applauding. Overall, these new tools are useful and, as before, FCPX is a very fluid, enjoyable editing application. It slices through 4K content better than any other NLE on the Mac platform. If you like its editing paradigm, then nothing else comes close.

Unfortunately, Apple didn’t squash some long-standing bugs. For example, numerous users online are still complaining about the issue where browser text intermittently disappears. I do feel that there were missed opportunities. The functionality of audio lanes – a feature introduced in 10.3 as a way to get closer to track-style audio mixing – hasn’t been expanded. The hope for an enhanced, roles-based audio mixer has once again gone unanswered. On the other hand, the built-in audio plug-ins have been updated to those used by Logic Pro X and there’s a clean path to send your audio to Logic if you want to mix there.

I definitely welcome these updates. The new color tools make it a more powerful application to use for color grading, so I’m happy to see that Apple has been listening. Now, I hope that we’ll see some of the other needs addressed before another year passes us by.

Originally written for Digital Video magazine / Creative Planet Network

©2017, 2018 Oliver Peters