iZotope RX Loudness Control



As more emphasis is being placed on loudness compliance around the world, it’s important for editors and sound mixers to have the right tools to stay legal. iZotope offers its Insight metering to see where your levels are, but a new addition is the RX Loudness Control plug-in. This not only analyzes your mix, but fixes it to be compliant. This plug-in is designed for Avid ProTools and Media Composer, along with the Adobe Creative Cloud applications. It works with mono, stereo, or surround mixes, but is not a real-time plug-in. Instead, it quickly analyzes your final mix and performs a faster-than-real-time processing of the track.

RX Loudness Control includes presets for eight international loudness standards and correction includes three components: fixed gain to hit a specific target, optional short-term loudness compression, and True Peak limiting. By design, the intent is to leave the mix dynamics in place, but where necessary IRC II (Intelligent Release Control) limiting is used. This style of limiting is also found in iZotope’s Ozone 6 mastering suite.

Operation for editors using Avid Media Composer or Adobe Premiere Pro CC couldn’t be easier. In Media Composer, first create a mixdown clip of your timeline mix and place that on an available track. Mute all other tracks. Apply the RX Loudness Control as an AudioSuite filter to the mixdown clip. Set the loudness standard preset, analyze, and render.

With the Adobe applications, the RX Loudness Control appears as an export preset in the export module of Premiere Pro or through Adobe Media Encoder. Simply export your timeline using the RX Loudness preset. Make adjustments to the settings as needed. If you want the mixed/processed track to automatically be imported back into the same project, make sure to check that box. Now export. The new .wav file will appear in your project, so simply mute all existing audio in your sequence and drop the processed .wav onto an empty audio track.

In the current version, there is no native support for Apple Final Cut Pro X or Logic Pro X. However, if you also own, subscribe to, or have access to Avid or Adobe applications (with the RX Loudness Control plug-in installed), you could use one of those to process your FCP X mix. First export a mix from FCP X as either a self-contained QuickTime movie or an audio file. Bring that into one of the other applications to encode the file using RX Loudness Control. When that’s completed, import the processed audio track back into FCP X. Mute or detach and remove all audio from your project (edited timeline) and connect the newly processed composite mix for your final compliant audio mix.

Originally written for Digital Video magazine / CreativePlanetNetworks.

©2015 Oliver Peters

Automatic Duck Redux


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

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.


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

Blackmagic Design UltraStudio 4K and UltraStudio Express


Post-production technology is changing with the shift to file-based workflows, Thunderbolt data paths, and adoption of 4K. To address the varied needs that range from one-man-band shops to large facilities, Blackmagic Design has developed the UltraStudio Thunderbolt product family. This includes the low-cost Mini Recorder and Mini Monitor modules at one end and the UltraStudio 4K Extreme at the other. I tested the UltraStudio 4K and UltraStudio Express, which sit in the middle of the family.


UltraStudio 4K

The UltraStudio 4K is a rack-mount unit that’s designed for facility or mobile truck installation. It is one rack unit tall, connects to a Mac or PC via a single Thunderbolt cable, and is compatible with Thunderbolt and Thunderbolt 2 protocols. All connections are on the back plane and the fan vents through the sides for tight rack spacing. The sleek front surface features a small confidence LCD display and six illuminated audio/video input selector buttons.

As a 4K unit, it supports numerous 4K UHD, 4K DCI, 2K, 1080p, 720p, NTSC, and PAL formats and frame rates. The back panel connections cover pretty much everything, including SDI, HDMI, composite and component analog video, AES digital audio, as well as XLRs for timecode and two channels of analog audio. If you need more than two channels of audio, then that is designed to be passed as embedded SDI or over AES. There’s a Thunderbolt loop-through, as well as two SDI loops for the two SDI input connections. Finally, UltraStudio 4K supports connection to a VTR, so it includes a standard 9-pin remote connector.

Like other Blackmagic rack units, UltraStudio 4K does not come with a power cord. This is an international, multi-standard system that can be installed into 120-240V/50-60Hz electrical systems. Since power plug configurations vary around the world, Blackmagic has opted to have you provide your own. In the United States, any standard three-prong power cord – like the one on the back of most monitors – should fit. Thunderbolt cables are also not included.

UltraStudio 4K is built around a chipset that supports SDI, 3G-SDI, and 6G-SDI bandwidths. This is essential for high-frame-rate 1080p, stereo 3D, 4:4:4, and 4K workflows. Yet these units are still compatible with SD and HD infrastructures. 6G-SDI (6Gb/s) is fast enough for UltraHD video at up to 30fps to be passed over a single BNC cable. In standard HD operation, the two SDI outputs can be configured for a full HD and a second down-converted signal. This unit doesn’t up or down-convert between 4K and HD or SD. However, if you are working in DCI versus UHD sizes, UltraStudio will up or down-convert to the nearest 4K size – up to 4096 or down to 3840 pixels wide.

In the UltraStudio product line, the big brother is UltraStudio 4K Extreme, a larger, more powerful unit with 12G-SDI bandwidth. That’s enough for 4K 60p video over a single BNC cable. It features even more connections, a larger LCD display, dual power supplies, and built-in hardware encoding for H.265 and Apple ProRes (on Mac OS X). 4K Extreme not only connects via Thunderbolt, but can also connect to a PCIe host using a small PCIe adapter card. Therefore, you aren’t limited to computers with Thunderbolt. This is the same unit that Avid will be selling as the Avid DNxIO. That version will embed hardware encoding of the Avid DNxHR codec and will be sold and supported through Avid and its reseller channels.

df2915_ultrastudioexpress34UltraStudio Express

If you need something portable, then UltraStudio Express fits the bill. This is an SD/HD unit that connects and is powered via a single Thunderbolt line. The small aluminum housing includes SDI and HDMI i/o connectors, as well as a multi-pin port for everything else. The unit ships with two breakout cables for a variety of analog audio and video connectors. One breakout cable features professional BNC and XLR connectors, while the other uses RCA plugs. The “pro” cable also includes a 9-pin VTR remote. UltraStudio Express is fanless and small, so it’s a perfect laptop companion. If you only need SDI or HDMI connectivity, then there’s no need to connect either of the breakout cables.

Like the larger 4K systems, UltraStudio Express supports a wide range of SD and HD standards with some conversion capabilities. On input it can convert HD to SD or SD to HD. On output from HD to SD or 720 to 1080. UltraStudio 4K adds SD to 720 or 1080 conversion on output. So, while there is a good range of conversion options on both systems, these might not cover every combination of frame rates, pulldowns, etc.

Both units are driven by Blackmagic Design’s Desktop Video software. This installer includes drivers, the Desktop Video Utility, Media Express, and Blackmagic Disk Speed Test. On a Mac, you access the Desktop Video Utility through System Preferences to set up the configuration of the unit. Media Express is Blackmagic’s own media player, capture, and print-to-tape software application. This is important for Final Cut Pro X users, since that NLE is designed only as a file-based editor without its own tape capture or output modules.

Diving in

df2915_Media-ExpressSince these are Thunderbolt devices, I tested both the UltraStudio 4K and Express units on my Retina MacBook Pro. I connected the output to a Panasonic 1080p monitor via SDI and later to my home Samsung using HDMI. Thunderbolt is hot-swappable, so it was easy to go back and forth between units. The Blackmagic Desktop Video Utility quickly recognized each unit for fast reconfiguration of settings if needed. Both units work with a wide range of Apple, Adobe, Avid, and Blackmagic Design software, so regardless of whether you are using Resolve, Premiere Pro CC, FCP X, or Media Composer, the systems just seem to work. Check the specs on the website, but a ton of other applications, like Smoke, Fusion, and Photoshop, to name a few, are also compatible.

I spent a fair amount of time running both Apple Final Cut Pro X, as well as Adobe Premiere Pro CC 2015 through both units. These are generally the NLEs I work with today. Naturally I expect DaVinci Resolve to work, but I was pleasantly surprised that Adobe SpeedGrade CC 2015 now also works. Enabling Mercury Transmit out of SpeedGrade through Blackmagic hardware has been a bit of an issue in the past. This meant the user had to decide between working with SpeedGrade and AJA hardware or Resolve and Blackmagic hardware. For Blackmagic owners this dilemma is gone. Finally, with current hardware, it all works as expected.

How 4K is handled with each unit depends on the application and what it’s capable of. For example, I have a test clip of Sony XAVC 4K footage (4096×2160). When I play that in either Premiere Pro CC or Final Cut Pro X through the UltraStudio Express it will display as 1080 even though the sequence is 4K. That’s because the unit can only output 1080. Both applications are savvy enough to downscale the sequence to 1080 and therefore it plays. Naturally this taxes the computer, although FCP X had far less trouble than Premiere Pro is doing so.

This was not the case when I connected the larger UltraStudio 4K. When you use Final Cut Pro X, the video output is determined by the settings in the Desktop Video Utility. If you set it to 1080p (to match the monitor), then FCP X will downscale a 4K timeline to 1080p and it will be happily piped to the monitor. This isn’t true in Premiere Pro, which overrides the Desktop Video settings. Even if you set it to 1080p, because the unit is capable of handling 4K, Premiere Pro will cause it to be set to match the 4K sequence. If you are working in a 4K sequence, UltraStudio 4K will play it at 4K (one of the 2160p choices). When that happens the 1080p monitor goes black. This means that you have to know which unit is right for you based on the monitors you own and the NLE you cut with. Or you may have to upgrade your monitors.

Both units work well. The Thunderbolt loop-through on the UltraStudio 4K came in handy by leaving my second port on the MacBook Pro free. I connected a LaCie Rugged FireWire 800 drive using a FW800-to-Thunderbolt adapter. It could effortlessly play a single stream of 1080p or 4K for a long time without dropping frames or causing any issues. Latency was extremely small over SDI (a bit more on HDMI) and there were no issues with audio sync. The build quality of both units is solid and Blackmagic Design now offers a three-year limited warranty.

The only caveat I would offer is that the UltraStudio 4K (and I’m sure this would go for the Extreme, too) is definitely an item that should only go into a noisy machine room. That’s because the fan is very loud – think hair dryer on low. The nice PR images that show a short rack containing one of these units next to an editor or colorist are pure fantasy.

Blackmagic Design has come a long way in a few short years to be a key player and leader in broadcast, production, and post technology. If you are considering any of the new Macs or even PCs that employ Thunderbolt, then you’d be hard-pressed to beat these units. They perform well, handle 4K, and set the standard for affordability.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

Color Finale


When Apple launched Final Cut Pro X, one of the items that users missed from previous versions was the popular three-way color corrector. Most built-in color correction modules and plug-ins use the common color wheel method for changing color balance. It’s based on the principle that to reduce a certain color cast you push the wheel in the opposite direction of that color. This decreases the color you want to reduce by shifting the balance towards the colors that are on the opposite side of the wheel.

Apple replaced the color wheel model in FCP X with the color board – a set of tabs for exposure, saturation and color (tint or hue). In the color tab, which controls balance, you see a color swatch field divided into positive and negative halves. To decrease one color, you simply move the puck into the negative range for that color. Although this may be intuitive to users who don’t know anything about color theory, it’s contrary to how most other color tools work.

As a result, many FCP X editors have been on the lookout for good color correction plug-ins that use the more common three-way color wheel method. The complication is that the FCP X user interface is very restrictive for software developers, which limits the sort of custom controls they can use. The usual workaround – if they don’t utilize the space of the Inspector panel – is a of HUD (heads-up display) or an overlay on top of the viewer image. To date, plug-ins that offer color wheels have included Yanobox Moods, Red Giant Colorista III, FilmConvert, and Hawaiki Color. Some, like Ripple Tools RT Color Balance and Lawn Road Color Precision, use the Mac OS color picker in a way that functions as a color balance control.

Layer-based correction

df1115_cf_2_smThe newest color correction plug-in for Final Cut Pro X is Color Finale from Color Grading Central. This is a layer-based color corrector that combines four tools into a single filter. These include color wheels, curves, LUTs, and vectors. To solve the interface issue, Color Finale uses a floating panel that lives on top of the regular FCP X interface. When you apply the Color Finale filter to a clip and click Open in the Inspector window, the floating control panel is launched. You can move it around in case it obscures part of the regular FCP X interface. Within this panel you can select any of its four tools for as many layers as you like and rearrange them into any layer order. Each layer has a separate opacity control and the filter has an overall “mix” slider in the Inspector window. This lets you adjust the intensity of the complete filter or of individual layers.

df1115_cf_1_smThese four tools combine most of the functions offered by other individual filters into a single plug-in. The three-way color corrector works as expected with balance and level controls for shadow, mid-range, and highlight sections, plus a global saturation slider. The LUT control is like Color Grading Central’s LUT Utility. Color Finale ships with several basic camera patch and creative look LUTs (same as with LUT Utility). These are installed into a standard Motion Templates directory for FCP X. You can add any .cube format LUT file to this folder and it will show up inside FCP X as one of Color Finale’s LUT options. The curves are unique among FCP X plug-ins, because these are true multi-point curves. Other curve tools are based on an s-curve, but not here. You can add numerous control points along any of the RGB or master curves and make precise adjustments. The vector tool is based on the six color vectors: red, green, blue, cyan, magenta, and yellow. You can adjust the luminance and saturation, as well as shift the hue, for each of these vectors.

df1115_cf_3_smIn a very, very loose sense, Color Finale is a bit like having Resolve inside FCP X and is most similar to FilmLight’s Baselight Editions color correction plug-in. You can easily mix and match tools as layers within the plug-in control panel. If you apply the Color Finale filter to multiple clips on the timeline, once you’ve opened the panel, you can move from clip to clip and add or adjust correction layers within this panel, as long as it stays open. If you’ve closed it, clicking Open in the Inspector will relaunch the control panel. Using “copy” and “paste attributes” enables you to copy-and-paste Color Finale effects from one clip to another. Unfortunately there is no way within the filter to split-screen the uncorrected and corrected image nor to store grades as presets. However, you can toggle individual layers on and off.


df1115_cf_4_smAs with any tool, how the controls work for you is a very subjective thing. Most of the tools feel very good to me, but I have a few minor issues. For me, the range of the color wheels is too extreme. Once you get about 1/4 of the way out from the color wheel’s center, you’ve made a pretty large balance change. At the edges, the change is huge and unusable for anything other than a special effect. Therefore, I’d rather see finer granularity with less extreme change at the edges of the wheel – or the ability to exceed the limits of the wheel for a more extreme change.

df1115_cf_5_smI find the vectors very limiting for secondary adjustments, because you cannot select how wide the envelope is around that vector color. For instance, the red vector will affect a red coat, but not flesh tones that tend to fall into the orange range – and orange is not a true color vector. The developers feel that adhering to true vectors results in a cleaner image as opposed to an HSL model; however, HSL secondary correction (as in Colorista III or Avid Symphony) enables you to be more selective about the colors that you are grabbing for adjustment. I’ve also become used to having contrast, pivot, color temperature, and tint controls. These are a key feature of Adobe SpeedGrade and included with many other filters. Hopefully at some point these will also be added to Color Finale.


A few key features that would be nice to have are tracking, masking, and keying. These aren’t built into the current version, but might be added natively into later versions. However, with the introduction of FCP X 10.2, filters gain a built-in shape mask function courtesy of the host application. This means that Color Finale gets a shape mask that can be use as a form of “power windows”. In addition, if you’ve purchase ColorMelt’s SliceX/TrackX package, its masking and mocha-powered tracking function can be combined with Color Finale grading.

Most importantly, the developers have done a fine job of balancing correction quality with real-time performance. Stacking seven or eight layers of various tools inside Color Finale still leaves you with real-time playback of a sequence with unrendered clips. You would not get this performance if you stacked the same number of individual color correction filters onto a single FCP X clip. Render speeds, when you do choose to render, are fast.

For many, Color Finale will be the color corrector that Apple should have made. It works well and combines a fine set of tools into a single package. Since it works as any standard filter does, you can use it in conjunction with any other effect and with Final Cut’s built-in tools. For example, you can use FCP X’s log processing to correct Log-C gamma-encoded clips upstream of the filter. You can still add a vignette or key mask on top by using the regular FCP X color board tool. As an added bonus, Color Finale also installs and works with Motion 5. If you’re an editor that prefers to do your grading inside the NLE and skip troublesome roundtrips, then Color Finale is a good addition to your Final Cut Pro X toolkit.

Denver Riddle, the developer of Color Finale, has posted an excellent grading tutorial for how you can creatively use this tool with FCP X (click this link).

(Full disclosure: I was involved in the Color Finale beta team and participated in providing testing and feedback during the development phase.)

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

Greater LUT Control with Koji Advance


For folks who like to use film emulsion LUTs (look up tables), Koji Color has recently updated its product line with Koji Advance. Koji Color is a collaboration between Dale Grahnthe highly regarded film lab timer (the film equivalent of a colorist) behind many blockbusters – and plug-in developer Crumplepop. Other products have included an iPad application and an earlier version of the Koji Color plug-in. (Click on any image in this post for an expanded view.)

Typically LUT packages require camera patch LUT files (to correct for each manufacturer’s log encoding scheme) and the “look” file. Some LUT developers split these into two sets of LUTs, while others combine both into a single 3D LUT file. Koji combines their LUTs, so each file is specific to a camera manufacturer and film stock type. The original version of the Koji Color plug-in was designed for Apple Final Cut Pro X and came in the form of two products – Koji DSLR and Koji Log. The lower cost DSLR package used emulation presets designed for Rec709 video signals. The Log package cost a bit more and added files and presets to be used with log gamma encoding, like ARRI Log-C. The FCP X plug-in itself also allowed for control over shadow, mid, and highlight exposure, plus saturation and a Film Stock Mix slider. The Mix slider controlled the amount of the LUT plug-in that was mixed into the image.

df3715_ka_10_smKoji Advance has replaced both the DSLR and Log plug-ins and added more controls and film grain. It is now also compatible with Motion, Premiere Pro CC, and After Effects CC, along with Final Cut Pro X. Koji Color also sells Koji Studio, which is a package of technical versions of these same LUTs intended for facilities outputting to DCI-P3 colorspace. It includes all of the Advance features as part of the package.

df3715_ka_2_smAll packages include presets built around one black-and-white and five color print film stocks. These presets were based on research intended to faithfully reproduce the look of specific Fuji and Kodak print stocks as a medium. 2302 is a black-and-white stock. 2393 is considered by Grahn to be the best print film made. 2383 is similar, but warmer. The other three options are on the cooler side. S versions are more saturation, N versions are more neutral, and LC is low contrast. There is also a 2302 HC (high contract) black-and-white stock.

At this point, it’s important to understand that these LUTs are not designed as creative looks like you’ll find in many other LUT products on the market. The application of any of the LUTs adds the color character of that medium and forms a starting point for your color grade.

When you install Koji Advance, you can opt to install it into any or all of the available host applications. A folder of the Koji 3D LUT files in the .cube format is also installed to your desktop. These are available to be used with other applications that allow LUT files to be imported, like DaVinci Resolve, Avid Media Composer, or Autodesk Smoke. You can move or copy this folder to any location you like.

Fine-tuning the look

df3715_ka_3_smTo use Koji Advance, drop the plug-in effect onto your clip. The first two choices you need to make are the camera preset and film stock. Pick these from the pulldown menus at the top of the control panel. If your footage is from a specific camera encoding scheme, such as ARRI Log-C or RedLogFilm, select the matching choice. If it is already a Rec709 color profile, then select the generic Rec709 choice. Various DSLR camera types also have available options. The film stock selector lets you choose from a number of presets based on the six film stocks and their variants. The LC preset is a brighter version that is more conducive to downstream color correction, which may be added on top of the LUT filter. As before, there’s a Film Stock Mix slider to control how much of this look is being applied to the image.

df3715_ka_4_smThe next series of sliders in the panel turns Koji Advance into a full-on color correction plug-in. You can opt for automatic white balance or manual control. If you pick auto, the controls still let you adjust the image further. There’s a Kelvin-based color temperature slider to warm up or cool off the image. Next are the three lift/gamma/gain controls, which are similar to the exposure sliders in the previous version. These act much like level controls in other applications and plug-ins. Lift adjusts shadow/black levels. Gamma for midrange. Gain for highlights.

df3715_ka_6_smDensity is a film-style control that’s probably unfamiliar to most video operators. It effectively works like an offset control that moves the whole signal higher or lower as you look at the videoscope. Using the density control doesn’t affect saturation in the same way as changing a lift/shadow control. Something to keep in mind is that Lift and Gain will clip the image at 0% and 100% on the scope. Density can move the image into the overshoot and undershoot areas below 0 and above 100. This is actually a good thing, because it preserves the full dynamic range of the image during the processing pipeline; however, it needs be corrected before any broadcast output. Therefore, when you make extreme adjustments, it’s a good idea to use a broadcast safe filter on the final output.

df3715_ka_8_smSaturation controls the chroma level, but this is only true for the color of the image, not including the coloration caused by the LUT file itself. In other words, if a film stock preset is designed to increase blue in the image and is thus a cooler tone, cranking the saturation all the way down will not result in a true black-and-white image. It will still have a slight blue cast. Only the black-and-white presets will be truly black-and-white.

df3715_ka_7_smThe last three color controls are printer point sliders. Again, this is for film-style “color timing” (color correction). The controls work globally for the whole image, so there are no separate color controls for shadows, midtones, and highlights. It works a lot like a single-wheel color corrector. Colors are grouped according to their opposites with sliders for red/cyan, green/magenta, and blue/yellow. To use these controls effectively, it’s best to understand how they work by viewing a vectorscope. If you slide the red/cyan slider all the way to red, it doesn’t increase the intensity of only reds within the image. It shifts the balance of the whole image towards red. Look at the vectorscope and you’ll see the entire chroma signal slide towards the red vector. Same for the other colors.

I’ve seen a few online comments questioning why not put a color wheel here instead of sliders. Apart from the UI issue (especially with design limitations in FCP X), it’s effectively the same thing. Let’s say on a system with color wheels you want to shift the balance towards orange. That’s halfway between red and yellow on the vectorscope. In Koji Advance, you would simply adjust the sliders for more red and more yellow, which results in a combined orange look. Two different methods to achieve the same goal, but sliders offer the advantage of a numerical value, which is easier to repeat for consistent results.

df3715_ka_5_smThe last section, which is new for Koji Advance, is film grain. They’ve picked five stock choices ranging from finer to coarser grain. Since adding grain contaminates the image, the grain section includes three adjustment controls – Film Grain Contrast, Film Grain Saturation, and Film Grain Mix. These let you dial in how subtle the presence of grain is within your shot.

In use

I’ve used the Koji film emulsion looks on previous jobs and they add a nice touch when it’s appropriate. You have to view this as the equivalent to audio engineers working with digital and analog recording systems. Analog tape is said to sound warmer, but that’s because the medium adds its own sonic character to the recording. Many engineers will record digitally, but then use analog somewhere in the final stages. Or, they’ll use a plug-in that emulates the attributes and coloration that analog tape recording gives to the sound. Using a film stock emulation for the purpose of adding character is exactly the same thing. The Koji LUTs are subtle enough that you’ll use them more frequently than some of the other choices. The controls offered by the plug-in enable you to do the work all within Koji’s panel, if you choose.

That being said, LUTs should be used as part of the grading process, not to be the process by itself. Typically I use the Koji plug-in together with other color correction tools, so it’s important to see how it affects the signal when it is part of a stack of several plug-ins. In FCP X, Hawaiki Color is still one of my favorite color correction tools. I like the on-screen controls, the tools are comprehensive, and the results are very pleasing. As a test, I stacked the two filters – Hawaiki Color, then Koji Advance. This let me grade upstream of Koji and use the two filters interactively.

df3715_ka_9_smAn issue I ran into was one of signal clipping. Hawaiki Color also permits overshoot and undershoot, meaning that dark areas can be pushed below zero on the scope. Video can be crushed for extreme contrast. This caused some sparkling color artifacts once those extreme levels hit the Koji plug-in. However, this was easily solved, by selecting Legalize in the Hawaiki Color controls. If you do this with another filter that doesn’t have a “clip” or “legalize” option and you encounter the same issue, then use any filter that does level clipping, such as the Broadcast Safe filter. Place it between your color correction filter and the Koji Advance plug-in and these artifacts will disappear.

The Koji Advance plug-in performance seems fine on most systems and shots I’ve tested. It’s an easy plug-in to understand and use, and will quickly become a tool you’ll use on every production.

©2015 Oliver Peters

Final Cut Pro X Organizing Tips


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.


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