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.
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 a video monitor or tape deck.
Refreshing the User Interface
DaVinci 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 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.
Editing with Resolve 12
As an NLE, Resolve 12 is an interesting mash-up between FCP 7 and FCP X. There are new features clearly intended for editors, including multicamera editing. You can now organize clips and timelines into custom bins, add metadata, and automatically filter clips into Smart Bins. You can sync group clips (double-system sound) and multicamera clips using in-points, timecode, or audio waveforms. The multicam editing routine is similar to other NLEs, where you drop a multicam clip onto your main timeline and then cut between camera angles.
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.
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 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.
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 multicam 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.
DaVinci 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 Rec. 709 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 add 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.
Real-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.
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.
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. It can already combine lists and media from a range of creative editing systems. Now that the editing tools and performance are there, it becomes the ideal application for final edit revisions, grading and mastering.