Audio Plug-ins for Editors – Part 1

Audio mixers and audio editors who spend their time at the business end of a DAW certainly have a solid understanding of audio plug-ins. But often it’s something many video editors don’t know much about. Every NLE includes a useful complement of audio filter effects (plug-ins) that can also be augmented by a wide range of third party options. So it’s worth understanding what you have at your fingertips. After all, audio is at least 50% or more of most video projects. For this and the following three posts, I’ll focus on some thoughts pertaining to what video editors should know about commonly used audio filters.

Numerous audio effects have been highlighted in previous posts. I personally use various Accusonus and iZotope effects on my work, most often for audio clean-up. That’s been very important in this past year with restricted production activity. Quite a lot of my recent edit jobs worked with source material from Zoom calls and self-recorded smartphone video – all with marginal audio quality. So clean-up tools like iZotope RX have been quite important.

Since a lot of what I do is corporate in nature, the mixes are relatively simple – usually voice and music with a minimum of sound effects. Other than some clean-up processing (noise or reverb removal and so on), my most frequently used effects are equalization and compression. These tools let me shape the mix and control levels. 

All audio plug-ins are the same. Or are they?

Audio effects typically come in two flavors. One group could be described as “digital” and is intended to process audio in a transparent fashion without adding tonal color on its own. The other group is considered “analog,” because these filters are intended to emulate the sound of certain analog processing equipment. Naturally, since these are software plug-ins, the processing is actually digital. However, analog-style emulations are designed to mimic the tonal qualities of classic outboard gear or of channel strip circuits built into analog consoles like Neve and SSL.

Tonal color is often created by how the audio is processed, such as the slope of the attack and release characteristics when the filter begins to affect the sound. In theory, you should be able to take a digital-style EQ and boost a frequency by a given amount and Q value (the width of the effect around that frequency). Then, if you apply a second instance of the EQ and cut (lower) that same frequency by the same dB and Q values, the two should cancel each other out and the signal should sound unaffected. An analog-style filter that has been designed to emulate certain models of peripheral gear will not be transparent if you try this same experience.

If you buy two competing digital audio plug-ins that have the same controls and features, then the way each alters the sound will likely be more or less the same. The only difference is the “skin,” i.e. the user interface. However, when you buy an analog audio plug-in, you are looking for certain sound characteristics found in current or vintage analog hardware. A developer could go the route of licensing the exact signal path from the original company. They can then legally display a branded UI that is skeuomorphic and looks just like the physical version that it represents. Waves has an entire repertoire of such effects. So if you want an SSL 4000-series E-type channel strip, they’ve got a software version for you.

The other development approach is to reverse-engineer the sound of that physical gear and release a plug-in that emulates the sound. It might be dead-on or it might only be reminiscent. The skeuomorphic interface is designed to look and feel like that gear. If you know the real device, then you’ll know what that plug-in can be expected to sound like. Apple Logic Pro has a wealth of effects that are emulations. If you want to use a Vox or a Marshall guitar amp filter, simply pick the one that features a similar faceplate. Nowhere does Logic actually call it a Marshall or a Vox, because Apple hasn’t licensed the exact circuits from the original manufacturer. Instead, they classify these as “inspired by” certain musical eras or genres.

Native versus third party effects

Audio plug-ins are installed using one of several protocols, including AAX, AU, and VST/VST3. This means that you can use the same effect in multiple host applications. However, DAWs and NLEs also install their own native effects that are only available within that single application. This can mean better performance versus third-party effects, which is especially true with current versions of Final Cut Pro and macOS.

One of my favorite native filters is the Logic compressor found in both Logic Pro and Final Cut Pro. It features seven compressor styles built into a single plug-in. The choices start with Platinum Digital, which is the digital (clean or transparent) version of this filter. The next six panes are different analog models, which are emulations of such popular outboard gear as Focusrite and DBX. There are two choices each for VCA, FET, and opto-electrical circuit designs.

Set the exact same adjustments in any of the compressor’s panes and the tonal color will vary slightly as you toggle through them. If you are unfamiliar with these, then check out some of the YouTube tutorials that explain the Logic compressor’s operation and which of the actual gear each of these panes is intended to emulate. I personally like the Studio VCA pane, which is based on a Focusrite Red compressor.

In Part 2, I’ll take a deeper look at two of the most common filtering functions – compression and equalization.

©2021 Oliver Peters

Final Cut Pro at 10 and Other Musings

Recently Final Cut Pro (formerly Final Cut Pro X) hit its tenth anniversary.  Since I’ve been a bit quiet on this blog lately due to the workload, I thought it was a good time to reflect. I recently cut a set of involved commercials using FCP. While I’ve cut literally thousands of commercials in my career, my work in recent years tends to be corporate/branding/image content in the five to ten minute range. I work in a team and the tool of choice is Premiere Pro. It’s simply a better fit for us, since the bulk of staff and freelancers are very fluid in Adobe products and less so with Apple’s pro software. Sharing projects and elements also works better in the Adobe ecosystem.

Cutting the spots in Final Cut Pro

In the case of the four :60s, I originally budgeted about two days each, plus a few days for client revisions – eleven days in total. My objective was to complete the creative cut, but none of the finishing, since these spots involved extensive visual effects. I was covering for the client’s regular editor who had a scheduled vacation and would finish the project. The spots were shot with a Sony Venice, simultaneously recording 6K RAW and 4K XAVC (AVC-Intra) “proxy” files. The four spots totaled over 1200 clips with approximately an hour of footage per spot. My cutting options could be to work natively with the Sony RAW media in Premiere Pro or DaVinci Resolve, or to edit with the proxies in any NLE.

The Sony RAW files are large and don’t perform well playing from a shared storage system. I didn’t want to waste the time copying location drives to the NAS, partially for reasons of time. I also wanted to be able to access media to cut the spots whether at home or at the work facility. So I opted to use the proxies, which allowed me to cut the spots in FCP. Of course, if you think of proxies as low-res files, you’d be wrong. These Sony XAVC files are high-res, camera-original files on par with 4K ProRes HQ media. If it weren’t for VFX, these would actually be the high-quality source files used for the final edit.

I copied the proxy files to a 2TB Samsung T7 SSD portable drive. This gave me the freedom to edit wherever – either on my iMac at home or one of the iMac Pros at work. This is where Final Cut Pro comes in. When you wade through that much footage, it’s easy for an NLE to get bogged down by caching footage or for the editor to get lost in the volume of clips. Thanks to skimming and keyword collections, I was able to cut these spots far more quickly than using any of the other NLE options. I could go from copying proxy files to my first cut on a commercial within a single day. That’s half of the budgeted time.

The one wrinkle was that I had to turn over a Premiere Pro project linked to the RAW media files. There are various ways to do that, but automatic relinking is dicier with these RAW files, because each clip is within its own subfolder, similar to RED. This complicates Premiere’s ability to easily relink files. So rather than go through XtoCC, I opted to import the Sony RAW clips into Resolve, then import the FCPXML, which in turn automatically relinked to the RAW files in Resolve.

There are a few quirks in this method that you have to suss out, but once everything was correct in Resolve, I exported an XML for Premiere. In Premiere Pro, I imported that XML, made sure that Premiere linked to the RAW files, corrected any size and speed issues, removed any duplicate clips, and then the project was ready for turnover. While one could look at these steps and question the decision to not cut in Premiere in the first place, I can assure you that cutting with Final Cut was considerably faster and these roundtrip steps were minor.

Remote workflows

Over the past year, remote workflows and a general “work from home” movement has shifted how the industry moves forward. So much of what I do requires connection to shared storage, so totally working from home is impractical. These spots were the exception for me, but the client and director lived across the country. In years past, they used to fly in and work in supervised sessions with me. However, in more recent years, that work has been unattended using various review-and-approval solutions for client feedback and revisions. Lately that’s through Frame.io. In the case of these spots, my workflow wasn’t any different than it would have been two years ago.

On the other hand, since I have worked with these clients in supervised sessions, as well as remote projects, it’s easy to see what’s been lost in this shift. Remote workflows present two huge drawbacks. The first is turnaround time. It’s inherently an inefficient process. You’ll cut a new version, upload it for review, and then wait – often for hours or even the next day. Then make the tweaks, rinse, and repeat. This impacts not only the delivery schedule, but also your own ability to book sessions and determine fair billing.

Secondly, ideation takes a back seat. When a client is in the room, you can quickly go through options, show a rearranged cut, alternate takes, and so on. Final Cut’s audition function is great for this, but it’s a wasted feature in these modern workflows. During on-prem sessions, you could quickly show a client the options, evaluate, and move on. With remote workflows, that’s harder to show and is subject to the same latency of replying, so as a result, you have fewer options that can be properly vetted in the cut.

The elephant in the room is security. I know there are tons of solutions for “drilling” into your system from home that are supposed to be secure. In reality, the only true security is to have your system disconnected from the internet (but also not totally bulletproof). As Sony Pictures, QNAP owners, Colonial Pipeline, agencies of the US government, or multiple other corporations have found out, if a bad actor wants to get into your system, they can. No amount of encryption, firewalls, VPNs, multi-factor authentication, or anything else is going to be guaranteed to stop them. While remote access might have been a necessary evil due to COVID lockdowns, it’s not something that should be encouraged going forward.

However, I know that I’m swimming against the stream on this. Many editors/designers/colorists don’t seem to ever want to return to an office. This is at odds with surveys indicating the majority of producers and agencies are chomping to get back to working one-on-one. Real estate and commuting costs are factors that affect such decisions, so I suspect hybrids will evolve and the situation in the future may vary geographically.

Final Cut Pro’s future

I mention the WFH dilemma, because remote collaboration is one of the features that Apple has been encouraged to build into Final Cut Pro by some users. It’s clearly a direction Adobe has moved towards and where Avid already has a track record.

I’m not sure that’s in Apple’s best interest. For one thing, I don’t personally believe Apple does a good job of this. Access and synchronization performance of iCloud is terrible compared with Google’s solutions. Would a professional collaboration solution really be industry-leading and robust? I highly doubt it.

Naturally Apple wants to make money, but they are also interested in empowering the creative individual – be that a professional or an enthusiast. Define those terms in whatever way you like, but the emphasis is on the individual. That direction seems to be at odds with what “pro” users think should be the case for Apple ProApps software, based on their experiences in the late years of FCP 1-7/FCP Studio (pre-X).

I certainly have my own feature request list for Final Cut Pro, but ultimately the lack of these did not stop me from a rapid turnaround on the spots I just discussed. Nor on other projects when I turn to FCP as the tool of choice. I use all four major NLEs and probably never will settle on a single “best” NLE for all cases.

The term “YouTube content creator” or “influencer” is often used as a pejorative, but for many filmmakers and marketeers outlets like YouTube, facebook, and Instagram have become the new “broadcast.” I recently interviewed Alexander Fedorov for FCP.co. He’s a Russian photographer/filmmaker/vlogger who epitomizes the type of content creator for whom Apple is designing its professional products. I feel that Apple can indeed service multiple types of users, from the individual, self-taught filmmaker to the established broadcast pro. How Apple does that moving forward within a tool like Final Cut Pro is anyone’s guess. All I know is that using the measurements of what is and isn’t “pro” no longer works in so many different arenas.

©2021 Oliver Peters

5 Easy FCPX Color Tricks

Color correction plug-ins are certainly fun to use, but Final Cut Pro X has plenty of horsepower on its own. There are also a number of features and techniques that often get overlooked. Here are five simple tricks you can use to enhance the look of your videos. (Click any image to see an enlarged view.)

Balance Color / Match Color

Final Cut has offered the ability to auto balance the color of a shot and to match two shots to each other since the early days. Balance color analyzes a shot and corrects it to a neutral tonality. This is typically a “best guess,” based on either an automatic overall adjustment or one focusing on white balance.

You can select all of the clips in your timeline and balance them in a single command. Most of the time, automatic will result in a pleasing enhancement of the image. The exception is when there’s no clear white reference in the shot, like a close-up on fire. In that case, you’d want to retain the orange/yellow qualities of the shot. The balance color results are not adjustable (other than to select between automatic or white balance), so consider it a first step to be further enhanced by the other color correction tools.

Match color is different in that it corrects the tonality of a selected clip to match another clip in the timeline. Park on the clip, select match color, skim to the clip used for the match, click on that frame for a preview, and then click Apply Match if you like the preview results. A common application might be to match A and B cameras to each other.

Match color can be used creatively, as well. For example, let’s say you want your clips to match the tonality of shots from a particular movie. A great resource for film reference frames is the Shotdeck website (free if you register as a beta user). Find and download a reference frame. Import the image file and edit it to the end of your timeline. Now use match color for a selected clip and skim to that reference film image on your timeline.

Obviously it won’t make a sunny daytime shot look exactly like a moody night shot from Bladerunner, but it will adopt the overall tonality as closely as possible. Once you’ve completed the match, delete the reference image from your timeline.

Blend modes

Timeline clips include blend mode attributes. The default is the normal mode, which can easily be changed to screen, overlay, soft light, and so on. Blend modes (also called composite and transfer modes) are commonly used by graphic artists and designers, but they are also useful in creating special looks for video.

To start, option-drag a clip above itself to create a duplicate as a connected clip. You now have two versions of that clip in perfect sync with each other. Adjust the blend mode of the connected clip. Let’s say you have a low-contrast clip. When you drag it above itself and change the top clip’s mode to soft light, it will instantly result in more contrast and saturation.

This same trick can be used to create stylish effects. For example, when you add a gaussian blur to the lower clip, the results are a dreamy image. Add a sharpening filter to the top clip and now you’ve added some localized contrast. Push it far enough and the results are almost cartoon-like.

You can use this trick on single clips or the entire sequence. Simply compound the sequence and then option-drag the compound up to create a duplicate, connected clip. Select the desired blend mode of the connected clip and tweak for your look.

Hue/Saturation Curves – Luma vs Sat

When you push color correction to an extreme, the black and white detail in the image becomes contaminated by the color shift introduced by your correction. You no longer have anything that’s true black or white in the frame. When a colorist is creatively adjusting a shot, they still want to end up with nearly pure black at the darkest part of the image and pure white at the brightest.

One way to achieve this is with the Luma vs Sat curve in the Hue/Saturation Curves tool. From left to right, the base line represents the brightness range from black to white. Pulling the curve up or down increases or decreases saturation at the brightness value corresponding to that point along the line. To reduce color saturation for black and white, add a control point inwards from each end of the line. Now drag the outer points down to decrease saturation. Drag the inner points more or less towards the center to adjust the roll-off from full saturation to zero saturation. The more gentle the slope of the curve, the smoother the roll-off with fewer potential artifacts. However, the trade-off is that you may lose too much saturation overall. So adjust to taste.

Orange and Teal

Filmmakers are enamored with the “orange-and-teal” look – skin tones tend to be warm (orange), while middle-range portions of the image take on a teal color cast. This is aided by proper lighting, costuming, and set design that is conducive to such a grade. For example, walls and furnishings that are neutral, black, gray, or dark in some way tend to be easier to swing towards the teal than a background of bright red walls.

Final Cut Pro X does include a color preset (Spring Sun) that mimics this look. You can also achieve it with any of Final Cut’s grading tools, such as the color wheels. First, use any color tool to establish a normal grade. Then apply color wheels for the look. The objective is to isolate skin tones from the rest of the image. Add an image mask for the wheels and use the HSL keyer. Use the color picker to select a skin tone. View the mask in black-and-white and adjust the HSL settings for a smooth key. It’s OK if the mask includes more than only the skin tones. The smoothness of the key is important.

Once you are happy with the key, go back to the image and grade inside of the mask. Push the midrange color wheel to the orange as needed. Or keep the skin tones neutral if you want to preserve a natural appearance. Change the mask toggle to outside and shift the midrange, shadows, and master towards teal. Finally, add the Luma vs Sat adjustment as described above to restore natural blacks and whites to the shadow and highlight areas.

LUTs

Color look-up tables – LUTs – are used to apply the proper color profile for cameras. Custom LUTs can also be used creatively to create and preserve preset looks such as stylized grades, film stock emulation, and more. Final Cut cannot export LUTs, however, it can import any LUT in the standard .cube format. The internet offers plenty of options to purchase custom, creative LUTs.

Let’s take a more DIY approach. Several third-party color correction plug-ins, including FilmConvert Nitrate and Color Finale 2 Pro, allow the user to export the grade done within that plug-in as a self-contained LUT. Maybe you want to preserve the grade for future use that doesn’t depend on having the plug-in. Or maybe you don’t own that plug-in, but can collaborate with an editor/colorist who does. In that example, send your selected shots or sequence to them for a grade. Then, instead of returning the files to you with the baked-in look, simply export the grades for these clips as LUTs.

Back on your system, apply the Custom LUT effect to each clip and import the corresponding LUT. Make sure the settings match your color space (Rec 709 across the board for Rec 709 libraries and projects). In the case of Color Finale 2 Pro and FilmConvert Nitrate, most aspects of the grade done within their panels will be reproduced. Certain non-grading features, such as film grain emulation will not be included in the LUT. Overall, if I’m looking for a perfect match (same shot to same shot), then I’ve had more accurate results using Color Finale 2 Pro. This method is a great way of creating and transferring custom looks in a non-destructive manner.

I hope these simple tips will give you some ideas on how you can get more out of Final Cut Pro X to create and apply your own special touches.

Originally written for FCP.co.

©2020 Oliver Peters

Drive – Postlab’s Virtual Storage Volume

Postlab is the only service designed for multi-editor, remote collaboration with Final Cut Pro X. It works whether you have a team collaborating on-premises within a facility or spread out at various locations around the globe. Since the initial launch, Hedge has also extended Postlab’s collaboration to Premiere Pro.

When using Postlab, projects containing Final Cut Pro X libraries or Premiere Pro project files are hosted on Hedge’s servers. But, the media lives on local drives or shared storage and not “in the cloud.” When editors work remotely, media needs to be transferred to them by way of “sneakernet,” High Tail, WeTransfer, or other methods.

Hedge has now solved that media issue with the introduction of Drive, a virtual storage volume for media, documents, and other files. Postlab users can utilize the original workflow and continue with local media – or they can expand remote capabilities with the addition of Drive storage. Since it functions much like DropBox, Drive can also be used by team members who aren’t actively engaged in editing. As a media volume, files on Drive are also accessible to Avid Media Composer and DaVinci Resolve editors.

Drive promises significantly better performance than a general business cloud service, because it has been fine-tuned for media. The ability to use Drive is included with each Postlab plan; but, storage costs are based on a flat rate per month for the amount of storage you need. Unlike other cloud services, there are no hidden egress charges for downloads. If you only want to use Drive as a single user, then Hedge’s Postlab Solo or Pro plan would be the place to start.

How Drive works

Once Drive storage has been added to an account, each team member simply needs to connect to Drive from the Postlab interface. This mounts a Drive volume on the desktop just like any local hard drive. In addition, a cache file is stored at a designated location. Hedge recommends using a fast SSD or RAID for this cache file. NAS or SAN network volumes cannot be used.

After the initial set up, the operation is similar to DropBox’s SmartSync function. When an editor adds media to the local Drive volume, that media is uploaded to Hedge’s cloud storage. It will then sync to all other editors’ Drive volumes. Initially those copies of the media are only virtual. The first time a file is played by a remote team member, it is streamed from the cloud server. As it streams, it is also being added the local Drive cache. Every file that has been fully played is now stored locally within the cache for faster access in the future.

Hedge feels that latency is as or more important than outright connection speed for a fluid editing experience. They recommend wired, rather than wi-fi, internet connections. However, I tested the system using wi-fi with office speeds of around 575Mbps down / 38Mbps up. This is a business connection and was fast enough to stream 720p MP4 and 1080p ProRes Proxy files with minimal hiccups on the initial streamed playback. Naturally, after it was locally cached, access was instantaneous.

From the editor’s point of view, virtual files still appear in the FCPX event browser as if local and the timeline is populated with clips. Files can also be imported or dragged in from Drive as if they are local. As you play the individual clips or the timeline from within FCPX or Premiere, the files become locally cached. All in all, the editing experience is very fluid.

In actual practice

The process works best with lightweight, low-res files and not large camera originals. That is possible, too, of course, but not very efficient. Drive and the Hedge servers support most common media files, but not a format like REDCODE raw. As before, each editor will need to have the same effects, LUTs, Motion templates, and fonts installed for proper collaboration.

I did run into a few issues, which may be related to the recent 10.4.9 Final Cut update. For example, the built-in proxy workflow is not very stable. I did get it to work. Original files were on a NAS volume (not Drive) and the generated proxies (H.264 or ProRes Proxy) were stored on the Drive volume of the main system. The remote editing system would only get the proxies, synced through Drive. In theory that should work, but it was hit or miss. When it worked, some LUTs, like the standard ARRI Log-C LUTs, were not applied on the remote system in proxy mode. Also the “used” range indicator lines for the event browser clips were present on the original system, but not the remote system. Other than these few quirks, everything was largely seamless.

My suggested workflow would be to generate editing proxies outside of the NLE and copy those to Drive. H.264 or ProRes Proxy with matching audio configurations to the original camera files work well. Treat these low-res files as original media and import them into Final Cut Pro X or Premiere Pro for editing. Once the edit is locked, go to the main system and transfer the final sequence to a local FCPX Library or Premiere Pro project for finishing. Relink that sequence to the original camera files for grading and delivery. Alternatively, you could export an FCPXML or XML file for a Resolve roundtrip.

One very important point to know is that the entire Postlab workflow is designed around team members staying logged into the account. This maintains the local caches. It’s OK to quit the Postlab application, plus eject and reconnect the Drive volume. However, if you log out, those local caches for editing files and Drive media will be flushed. The next time you log back in, connection to Drive will need to be re-established, Drive information must be synced again, and clips within FCPX or Premiere Pro will have to be relinked. So stay logged in for the best experience.

Additional features

Thanks to the Postlab interface, Drive offers features not available for regular hard drives. For example, any folder within Drive can be bookmarked in Postlab. Simply click on a Bookmark to directly open that folder. The Drop Off feature lets you generate a URL with an expiration date for any Bookmarked folder. Send that link to any non-team member, such as an outside contributor or client, and they will be able to upload additional media or other files to Drive. Once uploaded to Hedge’s servers, those files show up in Drive within the folder and will be synced to all team members.

Hedge offers even more features, including Mail Drop, designed for projects with too much media to efficiently upload. Ship Hedge a drive to copy dailies straight into their servers. Pick Up is another feature still in development. When updated, you will be able to select files on Drive, generate a Pick Up link, and send that to your client for download.

Editing with Drive and Postlab makes remote collaboration nearly like working on-site. The Hedge team is dedicated to expanding these capabilities with more services and broader NLE support. Given the state of post this year, these products are at the right time and place.

Check out this Soho Editors masterclass in collaboration using Postlab and Drive.

Originally written for FCP.co.

©2020 Oliver Peters

Color Finale Connect – Remote Grading for FCPX

Remote workflows didn’t start with COVID, but that certainly drove the need home for many. While editing collaboration at a distance can be a challenge, it’s a far simpler prospect than remote color grading. That’s often a very interactive process that happens on premises between a colorist and a client, director, or cinematographer. Established high-end post facilities, like Company3 with locations in the US, Canada, and England, have pioneered remote color grading sessions using advanced systems like Resolve and Baselight. This allows a director in Los Angeles and a colorist in London to conduct remote, real-time, interactive grading sessions. But the investment in workflow development, hardware, and grading environments to make this happen is not inconsequential.

High-end remote grading comes to Final Cut Pro X

The Color Finale team has been on a quest to bring advanced grading tools to the Final Cut Pro X ecosystem with last December’s release of Color Finale 2. Many editors are working from home these days, so the team decided to leverage the frameworks for macOS and FCPX to enable remote grading in a far simpler method than with other grading solutions.

The result is Color Finale Connect, which is a Final Cut Pro X workflow extension currently in free public beta. Connect enables two or more Final Cut Pro X users to collaborate in near-real-time in a color grading session, regardless of their location. This review is in the context of long distance sessions, but Connect can also be used within a single facility where the participants might be in other parts of the building or in different buildings.

Color Finale Connect requires each user in a session to be on macOS Catalina, running licensed copies of Final Cut Pro X (not trial) and Color Finale 2.2 Pro (or higher). Download and install Color Finale Connect, which shows up as a Final Cut workflow extension. You can work in a Connect session with or without local media on every participant’s system. In order to operate smoothly and keep the infrastructure lightweight, person-to-person communication is handled outside of Connect. For example, interact with your director via Skype or Zoom on an iPad while you separately control Final Cut on your iMac.

Getting started

To start a session, each participant launches the Color Finale Connect extension within Final Cut. Whoever starts a session is the “broadcaster” and others that join this session are “followers.” The session leader (who has the local media) drags the Project icon to the Connect panel and “publishes” it. This generates a session code, which can be sent to the other participants to join the session from within their Connect extension panels.

Once a session is joined, the participants drag the Project icon from the Connect panel into an open FCPX Event. This generates a timeline of clips. If they have the matching local media, the timeline will be populated with the initial graded clips. If they don’t have media, then the timeline is populated with placeholder clips. Everyone needs to keep their Connect panel open to stay in the session (it can be minimized).

Data transfer is very small, since it consists mainly of Color Finale instructions; therefore, crazy-fast internet speeds aren’t required. It is peer-to-peer and doesn’t live anywhere “in the cloud.” If a participant doesn’t have local media installed, then as the session leader makes a color correction change in Color Finale 2 Pro, an “in-place” full-resolution frame is sent for that clip on the timeline. As more changes are made, the frames are updated in near-real-time.

The data communication is between Color Finale on one system and Color Finale on the others. All grading must happen within the Color Finale 2 Pro plug-in, not FCPX’s native color wheels or other plug-ins. The “in-place” frames support all native Final Cut media formats, such as H.264, ProRes, and ProRes RAW; however, formats that require a plug-in, like RED camera raw files, will not transmit “in-place” frames. In that case, the data applied to the placeholder frame is updated, but you won’t see a reference image.

This isn’t a one-way street. The session leader can enable any participant to also have control. Let’s say the session leader is the colorist and the director of photography is a participant. The colorist can enable remote control for the DP, which would permit them to make tweaks on their own system. This in turn would update back on the colorist’s system, as well as for all the other participants.

Color Finale Connect workflows

I’ve been testing a late-stage beta version of Connect and Color Finale 2.2 Pro and the system works well. The “in-place” concept is ingenious, but the workflow is best when each session member has local media. This has been improved with the enhanced proxy workflow updated in Final Cut Pro X 10.4.9. Let’s say the editor has the full-resolution, original media and generates smaller proxies – for example, 50% size H.264 files. These are small enough that you can easily send the Library and proxy media to all participants using services like WeTransfer, MASV, FileMail, or Frame.io.

One of the session members could be a favored colorist on the other side of the world. In this case, he or she would be working with the proxy media. If the editor and colorist are both able to control the session, then it becomes highly interactive. Formats like RED don’t pose a problem thanks to the proxy transcodes, as long as no local changes are made outside of the Color Finale plug-in. In other words, don’t change the RED raw source settings within this session. Once the colorist has completed the grade using proxy media, those grading settings would be updated through a Connect session on the editor’s system where the original media resides.

Color management

How do you know that your client sees the color in the same way as you do on a reference display? Remote color grading has always been hampered by color management and monitor calibration. It would, of course, be ideal for each participant in the session to have Blackmagic or AJA output hardware connected to a calibrated display. If there is an a/v output for FCPX, then the Connect session changes will also be seen on that screen. But that’s a luxury most clients don’t have.

This is where Apple hardware, macOS, and Final Cut Pro X’s color management come to the rescue and make Color Finale Connect a far simpler solution than other methods. If both you and your client are using Apple hardware (iMac, iMac Pro, Pro Display XDR) then color management is tightly controlled and accurate. First make sure that macOS display settings like True Tone and Night Shift are turned off on all systems. Then you are generally going to see the same image within the Final Cut viewer on your iMac screen as your client will see on theirs.

The one caveat is that users still have manual control of the screen brightness, which can affect the perception of the color correction. One tip is to include a grayscale or color chart that can be used to roughly calibrate the display’s brightness setting. Can everyone just barely see the darkest blocks on the chart? If not, brighten the display setting slightly. It’s not a perfect calibration, but it will definitely get you in the ballpark.

Color Finale 2 Pro turns Final Cut Pro X into an advanced finishing solution. Thanks to the ecosystem and extensions framework, Final Cut opens interesting approaches to collaboration, especially in the time of COVID. Tools like Frame.io and Postlab enable better long-distance collaboration in easier-to-use ways than previous technologies. Color Finale Connect brings that same ease-of-use and efficient remote collaboration to FCPX grading. Remember this is still a beta, albeit a stable one, so make sure you provide feedback should any issues crop up.

Originally written for FCP.co.

©2020 Oliver Peters