Table of Contents Show
For those who don’t know the tool: Blackmagic Design builds cameras, video hardware and postproduction systems, while DaVinci Resolve rolls editing, Fusion compositing, colour, Fairlight audio and delivery into one application. That puts Resolve across a large portion of the post pipeline, from ingest and editorial through VFX, grading, mixing and mastering. With scripting and now MCP entering the same ecosystem, Studio is also becoming increasingly interesting as a media-automation platform rather than merely a collection of very capable rooms sharing one project.
DaVinci Resolve 21.1 is one of those point releases that contains several things facilities may care about more than the mere version number suggests. Multicam gets better keyboard control, the Photo page grows up, Fusion gains a small zoo of new 3D and shape tools, colour gets better dependency handling, project archiving becomes less adventurous, and Studio acquires a native MCP server for AI assistants. And yes, Resolve now has Inspector presets. In 2026. We truly live in the best timeline.
If you are heading to IBC 2026, Blackmagic Design will be at RAI Amsterdam from 11 to 14 September on stand 7.C49, with DaVinci Resolve 21 among the systems being demonstrated. That provides a convenient opportunity to ask an AI assistant to edit something while standing close enough to Blackmagic’s engineers to ask what happened afterwards.
Presets: welcome to the future
Inspector presets are probably not the feature whose their introduction warrants opening the champagne bottles, but they are exactly the sort of mundane improvement that becomes valuable after the 400th repeated setup. Editors can recall Inspector configurations for audio and video clip effects instead of rebuilding them clip by clip, while Fusion properties can be edited across multiple selected clips. Multicam editing mode is now tied to the timeline viewer, timecode sync can split multicams at gaps, and grid changes retain the page containing the selected angle.
Keyboard users get more room to operate. Resolve can assign shortcuts for decomposing multicams, switching or cutting up to 25 angles, and controlling source and auto-select states across as many as 32 tracks. None of this reinvents editorial. It simply removes little pieces of friction, which is usually what editors actually wanted before somebody invented another flashy AI button that triggers a credit-card dialogue.
There are several more of those small improvements. Audio waveforms can automatically scale to fill the available track height, clip durations can sit beside clip names, and the updated Trim Editor supports direct dragging in the viewer plus one- and five-frame trim actions. The Index can now export marker lists as PDF reports, a wonderfully conventional solution to the equally conventional problem of sending notes to somebody who isn’t sitting inside Resolve.
Compare with Current Timeline also gets a redesigned interface for switching between and navigating the compared edits. On the Cut page, a new timecode menu exposes the sync timecode used by Multi Source and adds timers for replay workflows. Preferences add options like stopping playback when scrubbing, always playing audio when moving the current frame, and selecting the following clip after a blade cut. Small things, everywhere.
MCP enters the machine room
The genuinely intriguing addition is the native MCP server in DaVinci Resolve Studio. MCP gives AI assistants a standardised way to interact with software tools and data. In Resolve, that means assistants can participate directly in media-management, editorial and automation workflows instead of merely discussing them in a chat window.
Blackmagic is considerably more specific about what this means than the words “MCP server” initially suggest. Resolve Studio 21.1 can connect to Claude, Claude Code and ChatGPT Codex, with setup handled through File > Setup AI Assistants. Once connected, you can initiate actions in Resolve through the assistant’s normal chat interface.
Blackmagic’s example isn’t merely conversational project search. It asks Claude to take a long video from the Media Pool, turn it into a three-minute highlight edit, remove edits shorter than one second and render the result as H.265 for review. Blackmagic also lists project analysis, media organisation, project-setting changes and batch rendering among the intended uses.
What Blackmagic does not explain in its primer is the less glamorous facility side: permissions, safeguards around destructive operations, logging and how access should be restricted in shared environments. Before giving an assistant instructions to “tidy up the project”, those questions remain still important.
Still, this is the first Resolve addition in a while that makes me want to immediately connect things together just to see what breaks. And as a half-deaf audio idiot, I am particularly delighted by the prospect of AI-assisted interaction with a system that also contains Fairlight. MCP does not magically make me a re-recording mixer, unfortunately, but it does make Fairlight look slightly less like the cockpit where I personally press the wrong button and apologise to everyone listening.
Photo gets rather more serious
The relatively new Photo page continues its attempt to make Resolve useful before the footage has even become footage. Resolve 21.1 expands live preview, camera control and capture support to Fujifilm GFX and X-series cameras, Leica SL system cameras and additional Sony Alpha models.
Photo Inspector image settings can now be adjusted from Blackmagic’s colour panels, including the Micro Color Panel. Plug-in and OpenFX support has also been expanded so Sky Replacement can be used on album photos.
None of this turns Resolve into a dedicated photographic workflow overnight, but it makes the Photo page harder to dismiss as an interesting appendage. Blackmagic is steadily extending Resolve further in both directions around traditional post-production.
Python joins Studio, mostly
The scripting change in 21.1 is a little more nuanced than “Python is paid now”. Blackmagic labels Advanced Scripting as a Studio feature, but the scripting API remains available from the console in the free edition. Workflow Integrations, the native UIManager and external scripting access require Resolve Studio.
That matters for facilities. Free Resolve can still be scripted interactively through its console, but machines used as externally controlled automation workers, pipeline integrations or UI-based workflow tools increasingly belong on Studio licences.
Blackmagic also gives an unusually direct reason for the restriction: it says the Python API had been used to unlock Studio functionality from the free edition. The company argues that protecting Studio licence revenue is preferable to moving Resolve to the subscription model that has become depressingly fashionable elsewhere.
Taken together with MCP, the decision makes considerably more sense. Studio now looks increasingly like a media-automation suite wrapped around an NLE, compositor, colour system, audio workstation and delivery tool. Python handles deterministic pipeline logic. MCP opens a route for assistant-driven interaction. The artist-facing application sits on top of the same project and media infrastructure.
The scripting API expands accordingly, with Blackmagic saying 20 additional APIs have been added. It can manage keyboard and render presets, query codecs and audio render settings, retrieve Media Pool transcriptions with speaker and timing data, create and flatten multicams, trigger multicam SmartSwitch and auto-align timeline clips.
Automation can also reach more timeline Inspector properties, transitions, fades, speed changes, audio normalisation, project-setting presets, source audio mappings and output blanking. Resolve 21.1 adds built-in Python support for console scripting, while Python 2 support is gone. For pipeline teams, this is the part of 21.1 that deserves a test machine before anyone enthusiastically updates a row of workstations.
Fusion gets some new reptiles
Fusion gains more than 25 new Krokodove shape and 3D tools, ranging from Connect 3D and Tube Create 3D to height-field, region and primitive-shape generators, alongside OpenPBR material shader support.
Connect 3D creates connections between vertices in 3D space, Height Field Create 3D can distort a plane’s depth from an image, and Tube Create 3D produces pipe-like geometry along a defined path. The new 3D Region toolset defines areas in 3D space that can restrict effects to particular regions, while the shape additions include primitive generation and more advanced edge manipulation.
OpenPBR is particularly interesting in mixed DCC pipelines because it aims at more portable material descriptions. That does not magically create flawless round trips through every application bearing an OpenPBR checkbox, but it gives Fusion another connection point to modern material workflows.
The Macro Editor can load macros from DRFX template bundles, automatically recognise single macros or offer selections from multi-macro bundles, and save templates directly into Edit or Cut page categories. Thumbnail management arrives too, while Update from Selected Tools can update a macro from nodes already modified in the flow without throwing away its control selections and layout.
Camera Tracker can import externally tracked results, while tracker controls can trim tracks and change the reference frame. Hard Mix blending arrives for Fusion tools and PSD import, and alpha handling in log conversion tools gains pre-divide and post-multiply controls.
Studio goes further with line-based lens-distortion calibration, deep-image flipbooks, matte objects for Renderer3D, deep motion blur and accelerated deep rendering. The new lens-calibration mode is particularly straightforward: draw lines over edges that should be straight and use those as the calibration reference.
The Fairlight Animator modifier also gains high-pass and low-pass filters. Fusion animation can therefore be driven by selected frequency ranges rather than the entire audio signal. Even I can understand that one: bass makes one thing wobble, treble makes another thing wobble. Fairlight and I may yet reach an understanding.
Lens Distortion also gains a rather practical new calibration method. Instead of relying only on a calibration chart, users can draw lines directly over features in the viewer that should be straight and use them to calibrate the lens distortion. That should be particularly useful for VFX plates arriving without useful lens calibration data: find a conveniently straight wall, window frame or horizon, draw the guides and let Resolve work backwards from the bent reality.
Color finds the missing luggage
The Color page gets a particularly welcome bit of pipeline housekeeping: missing LUTs and DCTLs can be relinked through LUT Manager, and missing DCTLs appear both there and as a viewer overlay. Anyone who has reopened an archived grade and discovered that one mysterious transform apparently lived on Steve’s Desktop will understand the appeal. Especially if your coworker isn’t called Steve.
Colour support expands with DJI D-Gamut2 and D-Log2, GoPro Log, Leica L-Log IDT and LUT support, Vivo Wide Gamut and Vivo Log. There are also more camera-transform LUTs and additional colour-space choices for ACES Transform.
Studio adds individual MultiMaster trim passes for Dolby Vision, HDR10+ and HDR Vivid, allowing the three formats to be graded independently instead of sharing one HDR trim. Output sizing and blanking can be overridden for individual trims, while each trim retains its own colour output and timeline cache so switching deliverables does not automatically mean recaching everything. The playhead position is also retained when moving between stacked clips on the Color page.
Resolve FX gains further CineFocus, Beauty and Film Grain controls, while Apple Immersive workflows receive an option for linear edge blending.
The plumbing also improves
Media review and management receive a surprisingly long list of sensible changes. Geometry assets can be previewed from Media Pool and Media Storage. Multiple clips can have their starting timecode changed together, selected markers can be deleted in list view, and multicams, compound clips and timelines expose creation and modification dates.
A new preference also determines which media AI tools can use. Facilities can require full-resolution media, or let Resolve follow the user’s existing preference for camera originals or proxies and fall back to whatever media is available if the preferred source is offline. It is a small checkbox with fairly large implications once AI tools start operating on projects unattended.
Project archives now offer considerably better control over what gets packed away. Users can choose original media or proxies, restrict the archive to used media and optionally include render cache, LUTs and Gallery stills. Project-level Media Management consolidation now also includes a DRP alongside the rendered project media. Again, not terribly sexy. Also exactly the kind of feature you become emotionally attached to the first time an archived project actually contains the things it needs.
Blackmagic Cloud Presentations gains subtitles plus sharing of annotations and replies to comments. Delivery expands with EXR rendering using HTJ2K compression, improved iXML handling, embedded Canon PL lens metadata, subtitle inclusion in Presentation exports and multiple embedded captions in QuickTime and MXF renders.
Studio additionally gets GPU-accelerated JPEG 2000 and HTJ2K decoding on NVIDIA GPUs. Apple Silicon gets hardware-accelerated HEIC decoding, while Windows gains native support for NVIDIA RTX Spark systems. PostgreSQL 18 is now bundled with Project Server as well.
Mind the project boundary
The most important deployment warning is project compatibility. Resolve 21.1 project libraries remain accessible from Resolve 20.3.3, but individual projects created or opened in 21.1 are no longer accessible from Resolve 20.3.
That means testing 21.1 with a production project is not a casual round trip. Once the project has crossed the boundary, the older version is no longer your emergency escape hatch for that project. A full project-library backup plus individual project backups before migration is therefore not excessive caution. It is cheaper than rediscovering the meaning of “backwards compatibility” at 2 a.m.
Hardware remains serious
On macOS, Resolve requires macOS 15 Sequoia or later and Apple Silicon. The baseline is 8 GB of memory, rising to 16 GB when using Fusion. Windows requires 16 GB of system memory, or 32 GB for Fusion, with at least 4 GB of GPU memory and OpenCL 1.2 or CUDA 12.8 support. Linux starts at Rocky Linux 8.6, 32 GB of system memory and a discrete GPU with at least 4 GB VRAM.
Studio’s advanced AI tools require at least 16 GB VRAM, while background rendering calls for at least 32 GB RAM and 12 GB VRAM. So yes, Resolve can now talk to AI assistants. The assistants should apparently arrive with a respectable GPU.
Studio becomes the automation edition
The free Resolve edition remains remarkably capable, but 21.1 makes the distinction between free Resolve and Studio more architectural. The paid edition isn’t where the extra effects, AI tools, HDR functions and higher-end processing live. It is increasingly where external automation and integration live too.
Python plus MCP is the interesting combination. Python gives technical teams precise, repeatable control. MCP creates a path for more conversational and agent-like control. Fairlight, Fusion, editorial, colour, media management and delivery already share the same project model. The Photo page is now expanding Resolve towards acquisition and stills as well.
Put those together and Resolve Studio starts looking less like five postproduction applications bolted together and more like a programmable media environment spanning acquisition, organisation, editing, VFX, grading, sound, automation and delivery. Which, frankly, is much more exciting than Inspector presets. Although I remain delighted that those finally work too.
| Product | DaVinci Resolve 21.1 |
| Developer | Blackmagic Design |
| Editions | DaVinci Resolve; DaVinci Resolve Studio |
| Project libraries | Resolve 21.1 project libraries are designed to remain accessible from Resolve 20.3.3 |
| Project migration | Projects created or opened in 21.1 are no longer accessible in Resolve 20.3 |
| macOS | macOS 15 Sequoia or later; Apple Silicon |
| Windows | Windows 10 Creators Update; Windows 11 for ARM on Qualcomm Snapdragon X Elite |
| Linux | Rocky Linux 8.6 |
| Baseline memory | macOS: 8 GB, 16 GB with Fusion; Windows: 16 GB, 32 GB with Fusion; Linux: 32 GB |
| Studio AI requirements | At least 16 GB VRAM for advanced AI tools; background rendering requires at least 32 GB RAM and 12 GB VRAM |
| Scripting | Scripting API available from the console in free Resolve; Workflow Integrations, native UIManager and external access require Studio |
| Free-edition output | Mastering and output up to Ultra HD; one processing GPU on Windows and Linux |
| Studio pricing | €305; digital delivery with activation code by email |
| IBC 2026 | RAI Amsterdam, 11–14 September 2026, stand 7.C49 |
| Download | Blackmagic Design Support |
1 comment
Comments are closed.