DaVinci Resolve 21.1.1 tightens trim workflow, adds CR3 RAW and USAC decode

Blackmagic Design has issued DaVinci Resolve 21.1.1, a maintenance update that concentrates on editor ergonomics, extra decode formats and a batch of bug fixes intended to smooth day‑to‑day grading and finishing work.

The headline changes land in the trim editor. The update expands how the viewer and mouse behave during trimming, brings audible feedback into the tool, and gives users new ways to operate on multiple edit points at once. Blackmagic summarised the trim improvements with the phrase "audio previews, support for audio-only clip editing, and actions that affect all selected edit points." Those three capabilities aim to make fine cuts faster and reduce repeated trips back to the timeline.

Specifically, the viewer and mouse now provide audio previews during trim actions so editors can hear how edits flow while they nudge in or out points. The trim tools also accept audio-only clip edits, letting sound edits be made without altering picture handles, and a set of actions has been added that apply the same change across every edit point that’s selected — useful when a scene needs consistent micro-adjustments across multiple cuts.

Beyond the trim toolset, Resolve 21.1.1 expands decode support for both picture and audio formats. The release adds support for Canon CR3 RAW files produced by the EOS R8 Mark II; Blackmagic listed this specifically as "Support for CR3 RAW decodes for EOS R8 Mark II." That means footage shot on that camera should be readable inside Resolve without third‑party transcodes, allowing grading and edit workflows to proceed from native CR3 source material.

On the audio front, the update brings USAC decoding to Windows machines running Windows 11. Editors and sound mixers working on that platform will now be able to decode content encoded with the USAC codec directly inside Resolve, removing a conversion step for media that uses that audio profile.

There are also platform and media‑specific decoder improvements. Blackmagic notes better NVIDIA decode memory usage for some R3D NE clips; that should reduce GPU memory pressure when working with certain RED formats, which in turn can keep playback and render operations more consistent on systems using NVIDIA acceleration.

Fusion, Resolve’s compositor and effects sub‑system, receives a series of fixes in this release as well. While the update log doesn’t list every Fusion correction in detail, the release note indicates several targeted updates to handling of Fusion effects and clip controls. Users who layer multiple Fusion nodes or apply several Fusion effects to a single clip should see improved controls and more predictable behaviour when moving or trimming those clips.

Across the build, Blackmagic says there are broader performance and stability improvements intended to reduce crashes and improve responsiveness in common tasks. Combined with the trim editor changes, the company suggested these adjustments will help users "speed up their workflows and declutter their timelines." The focus here is on small quality‑of‑life wins that add up during lengthy editing or finishing sessions.

For editors who rely on native camera formats and contemporary audio codecs, the new CR3 and USAC decodes are the most immediately tangible additions. For those who spend time in the timeline sculpting performance with the trim tools, the audio‑aware trim feedback and the ability to affect multiple points at once should cut repetitive work.

The update is positioned as a targeted maintenance release: a blend of new decode options, trim‑editor refinements and a collection of bug fixes in Fusion and decoding pipelines. Users who want the mend and polish of a small but practical release will find DaVinci Resolve 21.1.1 concentrates on everyday editor pain points and media handling edge cases.

If your projects include Canon EOS R8 Mark II files, content encoded with USAC, or RED R3D NE material on NVIDIA systems, this build addresses those specific workflows alongside broader editor usability improvements. As always, test new releases on backup projects or drive images before introducing them into critical deadlines, especially on machines with complex plugin stacks or studio pipelines.