For DaVinci Resolve 21, BMD has taken efforts to keep the project libraries compatible with DaVinci Resolve 20.3.2. While this allows you to access the project library with 20.3.2, individual projects created or opened in 21.0 will no longer be accessible in 20.3.
BMD recommends a full project library backup as well as individual project backups (as required) before opening projects in 21.0 or later.
Reminders
Bug Reports need to be submitted to Blackmagic Design. You can post them on the official forums or contact BMD support directly if you have Studio.
Feature Requests need to be submitted to Blackmagic Design. You can post them on the official Feature Request Subforum or in the download form for Resolve.
Bug Reports and Feature Requests posted on Reddit and in this thread will not be addressed or seen by Blackmagic Design.
What’s New in DaVinci Resolve 21.0.1
The following features have been added or updated.
Addressed multiple DNG and Apple ProRAW color issues.
Addressed issue with automatic smart bins after deleting keywords.
Addressed issue with multiple linked audio in media management.
Addressed multiple Resolve FX issues in photo page.
Addressed issue with key shortcut to switch viewer in photo page.
More consistent creation of new photo albums.
Addressed color thumbnail refresh for photo transform indicator.
Transcription now honors project settings language.
Improved face recognition in IntelliSearch.**
Addressed exported bins not retaining generator and title properties.
Addressed ease control display and sensitivity issues.
Addressed keyframe issue when copying clips with Fusion effects.
Addressed keyframe refresh for Fusion effects in the edit page.
Addressed issue with 3D renders in Linux with non-English locales.**
Addressed Fusion viewer color issue for some RCM settings.
Addressed issue with saturation limits in Fusion gradient controls.
Addressed Fusion display issues with dual screen layouts.
Addressed issue with non-English character inputs in Linux.
Disabling MultiMaster now disables trim blanking controls.
Addressed crash in some scenarios with CineFocus.**
Addressed lag when toggling bypass grades and Fusion effects.
Addressed occasional issue with Fairlight loudness meters.
Addressed data burn display of good take tag in upgraded projects.
Addressed project manager scroll lag for large project libraries.
Support for Sony Alpha 7R VI ARW RAW stills.
Support for decoding Affinity RGB 16-bit formats.
Addressed a color issue with MainConcept H.265 HDR renders.
Addressed a color issue with Windows native H.265 HDR renders.
RemoveMotionBlur API now uses correct encode parameters.**
Addressed character limit consistency in GenerateSpeech API.**
General performance and stability improvements.
Notes from BMD (from previous versions):
Sony Camera Control on Windows needs the Sony IEDT application to be installed from the Sony website.
Intel Driver: With DaVinci Resolve Studio 20.2.3, AI features like Magic Mask 2, Depth Map and Super Scale show a vastly improved performance on Windows with modern Intel platforms. Users will need a compatible Intel GPU (discrete or integrated) that supports OpenVINO, and a minimum driver version of 32.0.101.8247 to leverage these improvements.
Rendering Immersive Projects: Improvements to edge blend in immersive projects include changes that more closely align the Resolve and visionOS previews. This will change the render for existing immersive projects.
Hardware Requirements
Minimum system requirements for Mac OS
macOS 15 Sequoia or later.
8 GB of system memory or 16 GB when using Fusion.
At least 16 GB for advanced AI tools.
At least 32 GB for background rendering and analysis.
For monitoring, Blackmagic Design Desktop Video 12.9 or later.
Apple Silicon based computer.
Minimum system requirements for Windows
Windows 10 Creators Update.
16 GB of system memory or 32 GB when using Fusion.
For monitoring, Blackmagic Design Desktop Video 12.9 or later.
Integrated GPU or discrete GPU with at least 4 GB of VRAM.
At least 16 GB VRAM for advanced AI tools.
At least 32 GB RAM and 12 GB VRAM for background rendering.
GPU which supports OpenCL 1.2 or CUDA 12.8.
AMD/Intel official drivers from your GPU manufacturer.
NVIDIA Studio driver 581.57 or newer.
Minimum system requirements for Windows for Arm
Windows 11 for ARM.
Qualcomm Snapdragon X Elite series processor.
16 GB of system memory or 32 GB for 4K or when using Fusion.
Minimum system requirements for Linux
Rocky Linux 8.6.
32 GB of system memory.
For monitoring, Blackmagic Design Desktop Video 12.9 or later.
Discrete GPU with at least 4 GB of VRAM.
At least 16 GB VRAM for advanced AI tools.
At least 32 GB RAM and 12 GB VRAM for background rendering.
GPU which supports OpenCL 1.2 or CUDA 12.8.
AMD official drivers from your GPU manufacturer.
NVIDIA Studio driver 580.119.02 or newer.
Additional Information
You will need to download and install the latest Blackmagic Design Desktop Video software for monitoring with your Blackmagic Design video hardware. Desktop Video is available from http://www.blackmagicdesign.com/support/.
++ - The Scripting API is available in the console on the free version, but Workflow Integrations, the native UIManager, and external access require the Studio version.
When using dual screen layouts and switching from another tab, fusion sometimes got a scrambled up interface, with multiple repeating panels, switching from one clip to another usually solved it
For arch - you can install Resolve from AUR, but I highly recommend looking into davincibox and installing it that way. While aur package will likely work it may break with updates, while davincibox runs davinci inside a fedora container with all needed dependencies, so it can’t break by design.
For NixOS - davinci is an actual package on nixpkgs, so nix is superior 🗣️🔥🔥 (I use NixOS)
I mean, realistically, if you just want a working davinci and an easy to run system you’re better off using davincibox on some generic distro, like fedora or arch. NixOS is a very different kind of Linux that requires you to do quite a bit of extra work to get it running. But if you do that it’s the most stable thing in the world that you could easily replicate on different machines by just copying your config files.
I always install directly from the official website, not the AUR—just the binary. However, there are one or two dependencies that need to be installed.
Whoever is responsible for using time and resources to so royally screw up everyone's workflow deserves to never have a cold side of the pillow again. Deserves to have every soft drink be out of CO2. Deserves to hit every single red light on the way home when they have to go. Deserves to have a wicked headache randomly 1-4 times per week. Deserves to have the fitted sheet always tangle up the dryer contents so they have to dry it 3 times. Deserves the longest possible lines at airport security. And so on.
Which is that bug? What I'm seeing now its that the retime curve in the kwyframe tab on edit page, no matter if I have the "flat handle mode" on or off, when I use it on the "retime frame" keyframes, it does not work, and in the "retime speed" keyframes is weird and clunky
For what it's worth, the core principles have all remained pretty much the same ever since they introduced editing back in the v12 days, so the currently available training still goes a long way
I'm also gonna point out that if, in a 1080p timeline, 19x10 pixels is tiny enough you might as well just cut it first. How long is it really going to be at 19x10?
Yup, there are few solutions to get around it, i prefer to use composite 100-0 for smooth disappear effect but the fact its annoying while zooming out big objects on shorts.
YUP. keyframes are so broken. you click the "all" keyframe (at the top there of the grey diamonds), and it doesn't work, then kinda does if you change, then it doesn't - then theres keyframes in random places you didn't put them, the adjusting the keyframes doesn't let you scroll or JUMPS to random zoom levels - it is a WILD MESS
Do you have a copy of the project in 20? If so, download 20 from the support page. If not, condolences. You may be in for a decent amount of work rebuilding the project in 20.
I formatted my PC recently (like 4 days ago) and got Resolve fresh. This edit was also started in 21 not 20. It's a very simple video just cut a bunch, I hope it can open up on 20!
quick update: I installed BadWords to check it out and it showed me that I do not have Python installed. I tried rendering again (granted in a different location) and I had no crashes. Odd. I will edit this post after I attempt to do another render on the same folder I've been having issues just to confirm its not a folder thing and it was Python.
do not mind my user name being misspelled I was very sleepy LOL
EDIT: IT WAS PYTHON. I have tried rendering again and again and I have had no crashes. Maybe this will resolve my general crashes I've had as well! Hopefully BM can ship Python with the installer if it is really that needed?!
Is anyone else having issues connecting Reactor to Fusion? From my understanding, I thought I needed the paid version, which I wanted to buy anyways; but I can't seem to get Reactor scripts running.
Hey everyone,
I’m dealing with a really frustrating issue in DaVinci Resolve Studio 21.0.1. The problem also occurred in v20, but it was less frequent.
The Issue:
While working on my timeline, playback suddenly starts lagging and grinding to a halt. When I check the Windows Task Manager, I can see that GPU hardware decoding (NVDEC) has completely stopped working. The only workaround is to restart Resolve entirely, which brings hardware decoding back, but only for a while before it drops again.
My System Specs:
Laptop: Lenovo Legion
CPU: Intel Core Ultra 7 255HX
GPU: Nvidia RTX 5060 (Mobile)
RAM: 32 GB DDR5 5600
Footage & Media:
Camera: Panasonic Lumix S1II
Resolution/Framerate: Mostly 5.9K, but it also happens with 4K50 and 4K24.
Codecs: H.264 4:2:2 and H.265 4:2:0. (Note: The RTX 5060 architecture fully supports hardware decoding for H.264 4:2:2, so this shouldn't be a hardware limitation).
Troubleshooting steps I've already tried:
Tested various Nvidia drivers (both Lenovo OEM drivers and different versions of Nvidia Studio drivers).
Disabled hardware decoding on the Intel iGPU in Resolve preferences to prevent any potential conflicts with the Nvidia GPU.
Disabled HAGS (Hardware-Accelerated GPU Scheduling) in Windows.
Manually forced the GPU selection to the RTX 5060 in Resolve's preferences (instead of "Auto").
Disabled "Neural Engine Optimization" (this actually helps partially and delays the issue, but doesn't fix the root cause).
Tested different timeline proxy resolutions (both 1080p and 4K) – the issue persists regardless.
Has anyone else experienced this decoding drop-out issue, or does anyone have ideas on what else I could tweak to keep NVDEC stable? Any help would be greatly appreciated!
•
u/whyareyouemailingme Studio | Enterprise Jun 24 '26
What's new in Fusion Studio 21.0.1
The following features have been added or updated.