PDFviewer for Premiere Pro


Small developers often create the coolest tools for editing. Such is the case with Primal Cuts and their PDFviewer extension for Premiere Pro CC. Ever find yourself shuffling between paper scripts and storyboards, while trying to edit? Or juggling between different apps on-screen to view electronic versions, while going back-and-forth to your NLE? That’s what PDFviewer solves for you.

df4015_pcpdf_3Adobe has created a feature called extensions, which allows a developer to create a custom, dockable panel to perform certain function right inside the application’s interface. TypeMonkey is one example of this for After Effects. The same interface feature is also available in Premiere Pro. Extensions developed for Adobe applications also have the benefit of being cross-platform compatible.

PDFviewer is an extension designed for Adobe Premiere Pro CC. Once installed, it’s accessible from the extensions pulldown menu. When you select it, PDFviewer opens as a floating interface panel that can then be docked anywhere in the interface. If you dock it, make sure to do so in all of your workspaces and save those configurations. That way, if you have a file open, it will stay open as you jump between different layouts.

df4015_pcpdf_2Any PDF file can be opened in PDFviewer, including scripts, storyboards, and other documents. If you work in scripted long-form productions, then check if the script supervisor is using ScriptE Systems products. These are ideal for generating numerous electronic versions of common filming documents, including shot logs and lined scripts. However, any PDF works, including manually scanned PDFs of handwritten reports and lined scripts. Simply open up the lined script in the PDFviewer panel and now you have it right there within Premiere Pro. It’s not exactly the same as Avid’s Script Integration tools in Media Composer, but it’s the next best thing to it.

df4015_pcpdf_4PDFviewer lets you open multiple PDFs by clicking the “+” icon and adding another file. Multiple PDFs are accessible as tabs across the top of the PDFviewer window. It also includes a “hand” tool to easily scroll and pan within larger documents. Search is another great feature, which is perfect for working with transcripts. Search terms will be highlighted throughout the document. You can also copy-and-paste text from within PDFviewer to any metadata field in Premiere Pro.

Primal Cuts’ PDFviewer is a straightforward tool that every Premiere Pro editor will find to be a handy addition to their toolkit. At $10, the price is hard to pass up, simply based on the convenience of not shuffling more paper on your desk.

©2015 Oliver Peters

Fear the Walking Dead


When AMC cable network decided to amp up the zombie genre with The Walking Dead series, it resulted in a huge hit. Building upon that success, they’ve created a new series that could be viewed as a companion story, albeit without any overlapping characters. Fear the Walking Dead is a new, six-episode series that starts season one on August 23. The story takes place across the country in Los Angeles and chronologically just before the outbreak in the original series. The Walking Dead was based on Robert Kirkman’s graphic novels by the same name and he has been involved in both versions as executive producer.

Unlike the original series, which was shot on 16mm film, Fear the Walking Dead is being shot digitally with ARRI ALEXA cameras and anamorphic lenses. That’s in an effort to separate the two visual styles, while maintaining a cinematic quality to the new series. I recently spoke with Tad Dennis, the editor of two of the six episodes in season one, about the production.

Tad Dennis started his editing career as an assistant editor on reality TV shows. He says, “I started in reality TV and then got the bump-up to full-time editing (Extreme Makeover: Home Edition, America’s Next Top Model, The Voice). However, I realized my passion was elsewhere and made the shift to scripted television. I started there again as an assistant and then was bumped back up to editing (Fairly Legal, Manhattan, Parenthood). Both types of shows really do have a different workflow, so when I shifted to scripted TV, it was good to start back as an assistant. That let me be very grounded in the process.”

Creating a new show with a shared concept

Dennis started with these thoughts on the new show, “We think of this series as more of a companion show to the other and not necessarily a spin-off or prequel. The producers went with different cameras and lenses for a singular visual aesthetic, which affects the style. In trying to make it more ‘cinematic’, I tend linger on wider shots and make more selective use of tight facial close-ups. However, the material really has to dictate the cut.”

df3615_ftwd_3Three editors and three assistant editors work on the Fear the Walking Dead series, with each editor/assistant team cutting two of the six shows of season one. They are all working on Avid Media Composer systems connected to an Avid Isis shared storage solution. Scenes were shot in both Vancouver and in Los Angeles, but the editing teams were based in Los Angeles. ALEXA camera media was sent to Encore Vancouver and Encore Hollywood, depending on the shooting location. Encore staff synced sound and provided the editors with Avid DNxHD editorial media. The final color correction, conform, and finishing was also handled at Encore Hollywood.

Dennis described how post on this show differed from other network shows he’s worked on in the past. He says, “With this series, everything was shot and locked for the whole season by the first airdate. On other series, the first few shows will be locked, but then for the rest of the season, it’s a regular schedule of locking a new show each week until the end of the season. This first season was shot in two chunks for all six episodes – the Vancouver settings and then the Los Angeles scenes. We posted everything for the Vancouver scenes and left holes for the LA parts. The shows went all the way through director cuts, producer cuts, and network notes with these missing sections. Then when the LA portions came in, those scenes were edited and incorporated. This process was driven by the schedule. Although we didn’t have the pressure of a weekly airdate, the schedule was definitely tight.” Each of the editors had approximately three to four days to complete their cut of an episode after receiving the last footage. Then the directors got another four days for a director’s cut.

df3615_ftwd_5Often films and television shows go through adjustments as they move from script to actual production and ultimately the edit. Dennis feels this is more true of the first few shows in a new series than with an established series. He explains, “With a new series, you are still trying to establish the style. Often you’ll rethink things in the edit. As I went through the scenes, performances that were coming across as too ‘light’ had to be given more ‘weight’. In our story, the world is falling apart and we wanted every character to feel that all the way throughout the show. If a performance didn’t convey a sense of that, then I’d make changes in the takes used or mix takes, where picture might be better on one and audio better on the other.”

Structure and polish in post

In spite of the tight schedule, the editors still had to deal with a wealth of footage. Typical of most hour-long dramas, Fear the Walking Dead is shot with two or three cameras. For very specific moments, the director would have some of the footage shot on 48fps. In those cases, where cameras ran at different speeds, Dennis would treat these as separate clips. When cameras ran at the same speed (for example, at 24fps for sync sound), such as in dialogue scenes, Susan Vinci (assistant editor) would group the clips as multicam clips. He explains, “The director really determines the quality of the coverage. I’d often get really necessary options on both cameras that weren’t duplicated otherwise. So for these shows, it helped. Typically this meant three to four hours of raw footage each day. My routine is to first review the multicam clips in a split view. This gives me a sense of what the coverage is that I have for the scene. Then I’ll go back and review each take separately to judge performance.”

df3615_ftwd_4Dennis feels that sound is critical to his creative editing process. He continues, “Sound is very important to the world of Fear the Walking Dead. Certain characters have a soundscape that’s always associated with them and these decisions are all driven by editorial. The producers want to hear a rough cut that’s as close to airable as possible, so I spend a lot of time with sound design. Given the tight schedule on this show, I would hand off a lot of this to my long-time assistant, Susan. The sound design that we do in the edit becomes a template for our sound designer. He takes that, plus our spotting notes, and replaces, improves, and enhances the work we’ve done. The show’s music composer also supplied us with a temp library of past music he’d composed for other productions. We were able to use these as part of our template. Of course, he would provide the final score customized to the episode. This score would be based on our template, the feelings of the director, and of course the composer’s own input for what best suited each show.”

df3615_ftwd_2Dennis is an unabashed Avid Media Composer proponent. He says, “Over the past few years, the manufacturers have pushed to consolidate many tools from different applications. Avid has added a number of Pro Tools features into Media Composer and that’s been really good for editors. There are many tools I rely on, such as those audio tools. I use the Audiosuite and RTAS filters in all of my editing. I like dialogue to sound as it would in a live environment, so I’ll use the reverb filters. In some cases, I’ll pitch-shift audio a bit lower. Other tools I’ll use include speed-ramping and invisible split-screens, but the the trim tool is what defines the system for me. When I’m refining a cut, the trim tool is like playing a precise instrument, not just using a piece of software.”

Dennis offered these parting suggestions for young editors starting out. “If you want to work in film and television editing, learn Media Composer inside and out. The dominant tool might be Final Cut or Premiere Pro in some markets, but here in Hollywood, it’s largely Avid. Spend as much time as possible learning the system, because it’s the most in-demand tool for our craft.”

Originally written for Digital Video magazine / CreativePlanetNetwork

©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

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

Adobe Premiere Pro CC 2015


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


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

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

New color workflow

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

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

Editorial enhancements

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

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

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

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


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

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

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

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

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


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

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

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

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

The FCP X – RED – Resolve Dance II


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

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

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

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

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

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

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

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

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

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

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

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

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

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

©2015 Oliver Peters