Blackmagic DaVinci Resolve on Linux

29/04/2022 - 10:53
Average: 4.6 (5 votes)

Blackmagic Design DaVinci Resolve is one of the most powerful video editing suites available that also runs on Linux. There are some quirks with DaVinci Resolve under Linux and this guide will help you with those.

Resolve screenshot

There are two versions available of Blackmagic Design DaVinci Resolve, the free version and the paid studio version:

  • Free version - Free to download and use. It has some limitations on used export resolutions, available plugins and some of the more advanced features (noise reduction, effects, audio and video encoders/decoders, interlaced video handling, GPU usage). For many uses and users this version does pretty much everything you might need for video editing. Does not utilize a GPU as much as the paid Studio version.
  • Studio version - Relatively cheap (~300€) version that has no limitations, all features are available. This version requires a license, either a registration code (allows two installations) or a USB license dongle (that must be connected at all times). Updates from major and minor versions have been free so far. Unfortunately, even with this paid version, there are encoder and decoder limitations under Linux. If you need to work with interlaced material, noise reduction and all possible video effects, then you need this paid version. Also if you need to work with interlaced video, for example editing old SD PAL/NTSC videos, you need the studio version for proper interlacing handling.
    If you get the USB Dongle license version you can also use Fusion, the separate Video FX suite.
  • Note that some of Blackmagics Hardware (Cameras, Editing keyboards) come bundled with the Studio version.

The current stable version of DaVinci Resolve is 17.4.6, a beta version of 18 is also available, and can be downloaded from the support site.

DaVinci Resolve is obviously not free software, open source or anything close to that, but it does use plenty of open source software internally like Qt (5.15 since 17.4 to be specific), SoX Resampler library libsoxr, OpenCV 3.4.1 and FFMPEG. (Yep, ffmpeg, the all decoding and encoding video tool. The irony...). (And yes, I've tried replacing the ffmpeg libraries with ones that support more formats, no luck there unfortunately).

The Studio version also supports scripting with Python and Lua and external encoding plugins in C++. See the documentation and examples under the installation directory in Developer/Scripting for details.

Hardware and software requirements

Resolve does have some hefty hardware requirements, a powerful multi core CPU and GPU with plenty of VRAM is highly recommended, especially if working on anything higher than Full HD or using GPU specific features like noise reduction. The open-source drivers will not work, you do need to use proprietary NVIDIA or AMD Radeon drivers.

Minimum system requirements for Resolve on Linux, according to Blackmagic, are:

  • CentOS 7.3
  • 32 GB of system memory
  • Discrete GPU with at least 2GB of VRAM
  • GPU which supports OpenCL 1.2 or CUDA 11
  • NVIDIA/AMD Driver version – As required by your GPU

You also need to have:

  • CPU with SSE4 (So you are out of luck on older CPUs, for example Phenoms, even if specs would otherwise be just fine for SD/HD editing.)

Experience has shown that you can work with less memory if you keep to basic features, 8-16GB memory is fine for basic cutting of Full HD footage. A NVIDIA GPU is highly recommended, AMD GPU should work too, but afaik, some effects are CUDA only.

Any decent Linux distribution should be OK, the officially supported distribution is a very old CentOS 7.3 but who uses something like that anymore ? Experience has shown that for example Linux Mint works perfectly, and so should any Ubuntu derived distribution. Other distributions shoud be just fine too.

Make sure you have up to date GPU drivers and that your GPU is supported, minimum CUDA version is 11 or OpenCL 1.2. Also GPU with at least 4-6 GB of VRAM is highly recommended for any serious work. And for any GPU based features like noise reduction or effects, 4K resolution the more the better. Note that Resolve is not the only application using precious GPU memory, your desktop environment, X11, Firefox, etc will also be using some it.

Download DaVinci Resolve

You can find downloads of Resolve to the latest versions and also old version (great if your CPU/GPU is not up for the latest and greatest!) at Blackmagics support site, in the Latest downloads section.

Be sure to pick the right version, if it has Studio in the name then you need to buy a license activation code or have the license USB dongle. Unfortunately you can't easily switch between the Studio and Free version, it would be great if the Studio version would just limited the features if no license is found, but alas, it won't work.

Decoding and encoding limitations

Both the Free and Studio versions have very limited support for both audio and video decoders and encoders, especially with Linux. The Studio version is a bit better than the free version in this regard, but it is still much worse than on Windows or OS X.

Video decoder limitations

The free versions has a very limited support for video decoders in all supported operating systems, but it is especially limited under Linux. The de-facto standard (consumer) video formats that are used everywhere like h264 and h265 are not supported at all. Fortunately there are workarounds, a bit time and space consuming, but still, pretty easy and straightforward.

The studio version does support h264 and h265.

Video encoder limitations

There are also limitations in the encoding part, or exporting formats. Here too h264 or h265 is not supported under Linux in the free version.

The studio version support h264 and h265 encoding, but only with NVIDIA GPU encoding.

Quality wise it is also recommended to export in first DNxHR and then encode with ffmpeg to h264.

Audio encoder limitations

Audio encoding support is very bad in both versions, even the paid Studio version won't export anything other than uncompressed PCM. Blame idiotic software patents for this. There is no support for any standard encoding (Advanced audio coding, aac) formats under Linux. Using uncompressed PCM audio is the best (and only) option and then re-muxing with ffmpeg and compressing the audio, see below for examples.

There is nothing wrong with uncompressed audio, it is the best quality you can have after all. The issue is with playback, not all software and especially consumer hardware supports it in video containers.

Audio input

ALSA audio input is working since version 17.3. Note that if you are using anything older then audio input won't work.

Workarounds for encoder and decoder limitations

FFmpeg to the rescue! It does add an extra step, but not a big deal.

Decoding, re-encoding or re-muxing video

Decoding and re-muxing example ffmpeg commands
Operation FFMpeg command
Extract audio from video to raw 16-bit PCM .wav
ffmpeg -i video.flv -c:a pcm_s16le audio-only.wav
Encode to DNxHR-HQ and PCM audio
ffmpeg -i video.mov -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p -c:a pcm_s16le video-dnxhr-gq-raw-pcm.mov
Re-mux video, decoding audio to PCM, copying video
ffmpeg -i video.mov -c:v copy -c:a pcm_s16le video-encoded-audio-raw-pcm.mov
   

Encoding video and audio

Encoding ffmpeg commands
Operation FFMpeg command
Encode audio to AAC, copying video
ffmpeg -i video-h264-audio-raw-pcm.mov -c:v copy -c:a aac video-h264-audio-aac.mov
Encode to DNxHR-HQ and PCM audio
ffmpeg -i video.mov -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p -c:a pcm_s16le video-dnxhr-gq-raw-pcm.mov
Encode high quality h264 video and AAC audio
ffmpeg -i video.mov -c:v libx264 -preset veryslow -crf 14 -c:a aac -b:a 256k video.mp4
Encode high quality h264, force yuv420, video and AAC audio
ffmpeg -i video.mov -c:v libx264 -preset veryslow -pix_fmt yuv420p  -crf 14 -c:a aac -b:a 256k video.mp4

Speed Editor keyboard

Speed Editor keyboard

The Speed Editor keyboard should work fine with 17 (initial support in beta 4) using USB (Bluetooth support unknown).

UDEV rules for Speed Editor keyboard

You might need to fix the device access with a udev rule like:

KERNEL=="hidraw*", ATTRS{idVendor}=="1edb", ATTRS{idProduct}=="da0e", MODE="0660", TAG+="uaccess"

HiDPI issues

Under some desktop environments you might have issues with scaling when using HiDPI displays. A workaround is to set a couple Qt environment variables:

export QT_DEVICE_PIXEL_RATIO=2
export QT_AUTO_SCREEN_SCALE_FACTOR=true

Other quirks or limitations

  • ALT+Mouse button combination is used in Resolve but might be reserved by your desktop system for moving windows. You need to disable or change the combo.
  • ALSA Audio input didn't work until version 17.3

Hints & Tips

  • Running out of GPU memory in Resolve ? You can monitor GPU usage by process with the nvidia-smi utility. For example firefox can be a GPU memory hog and closing it might release enough for Resolve to be happy again.
    |    0   N/A  N/A    202962      G   /usr/lib/firefox/firefox         1610MiB |

Related resources

Color grading and color management

Keywords: 
Blackmagic, FFmpeg, Resolve