Fear the Walking Dead

df3615_ftwd_1_sm

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

Advertisements

iZotope RX Loudness Control

 

df3215_rxloud_sm

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

df3915_ad_1_sm

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

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

Knowing the market

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

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

How it works

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

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

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

Some caveats

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

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

Automatic Duck Media Copy 4.0

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

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

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

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

©2015 Oliver Peters

Blackmagic Design DaVinci Resolve 12

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

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

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

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

Refreshing the user interface

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

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

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

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

Editing with Resolve 12

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

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

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

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

Other improvements

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

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

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

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

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

Performance

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

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

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

Final thoughts

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

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

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

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

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

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters