Talk:DaVinci Resolve

Python 3.6 not found problem

I need help with setting python 3.6 that way that:

• I can install packages there (with pip?)
• dr could see the python 3.6
• pycharm could debug scripts in that installation

The problem of not seen python 3.6 is discussed here:

• https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=116859#p798244 - ended up by invoking python via lua, and did not work for me
• https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=141012&p823341#p823341 - ended with working solution for windows, but unknown for linux. PYTHONHOME variable may be needed?
• https://video.stackexchange.com/questions/32458/davinci-resolve-python-3-6-not-found - solution with symlinks to pyenv. It worked for me.

I set External scripting using to Local in General settings. Installed python36 (tried both from aur and with pyenv). Then with variables RESOLVE_SCRIPT_API, RESOLVE_SCRIPT_LIB and PYTHONPATH and with /usr/bin/python3.6 interpreter, I successfully run the example script (it creates the Hello World project). Place it to the ~/.local/share/DaVinciResolve/Fusion/Scripts/Utility/example.py It appears in Workspace -> Scripts.

If I go to Workspace -> Console -> Py3, I now see there is no more error window that python 3.6 it is not found.

I tried with patched (see [1]) python36^AUR and it was detected by dr. But now I am thinking that it is better with virtual environment, because I need other python libs available for scripting, and aur python packages only supposed for latest python version.

Help will be appreciated.

Ashark (talk) 04:40, 7 February 2022 (UTC)

Docker and DR

I have found a project for dr containerization. I did not explored it yet, which benefits it gives versus normal pkgbuild repackaging. And it seems it is targetet for ubuntu and for nvidia. Probably, it may be useful somewhen, so I decided to keep it here for this link not being lost.Ashark (talk) 11:14, 6 April 2022 (UTC)

Workaround for DR Free causes a/v desync

$ ffmpeg -i input.mp4 -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p -c:a pcm_s16le -f mov output.mov

This causes a/v desync to me (15 min video, generated with vlog-toolset).

In case if anybody runs into the same issue, here's the solution:

$ ffmpeg -threads 16 -fflags '+genpts+igndts' -i input.mp4 -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p -af 'aresample=async=1,asetpts=PTS-STARTPTS' -c:a pcm_s16le -f mov output.mov

The downside is that it makes sound in DaVinci Resolve preview choppy, but it's fine after final rendering. Alopatindev (talk) 00:21, 4 March 2024 (UTC)

noborderrule=2 doesn't work on Wayland.

As https://bbs.archlinux.org/viewtopic.php?pid=2165312#p2165312 explains, noborderrule=2 shan't work on Wayland, per the decision at https://bugs.kde.org/show_bug.cgi?id=452240#c1. Is there a better solution available? Regardless, we should probably add something to mention this caveat.

When using a forum, remember to tag the person you are responding to, in case they are not subscribed to the thread. (talk) 16:39, 16 April 2024 (UTC)

Unable to play any video or hear audio despite import succeeding

I uninstalled opencl-amd^AUR and opencl-amd-dev^AUR and installed rocm-opencl-runtime as advised by the DaVinci_Resolve_Checker, and to avoid the whole program from crashing, with the following message:

"Package opencl-amd contains both implementations for amd: legacy orca and modern rocm. But DR crashes when it sees both (no bug report for this yet). And currently the opencl loader does not support specifying specific icd file, see https://github.com/OCL-dev/ocl-icd/issues/7#issuecomment-1522941979. So currently it is recommended to install rocm-opencl-runtime instead of opencl-amd."

But then, I could import videos and add them to the timeline, but not play them, nor hear the sound; the preview stayed black. The whole app except for the file, edit etc menu on the top also sometimes hung. In the logs, there was also this error:

opt/resolve/libs/libc++.so.1: undefined symbol: __cxa_init_primary_exception

After reinstalling the free 19.0.3-1 package, the problem was solved. Running on integrated AMD GPU.

-- User:Fightcookie 02:56, 30 October 2024 (UTC)

A script for installing DaVinci Resolve using Podman and Distrobox

After having a ton of issues with Resolve after installing the latest updates via Pacman, I had to go chasing through the internet to find a better solution. That finally exhibited in the davincibox script, located https://github.com/zelikos/davincibox

This script installs DaVinci Resolve and a copy of the libraries it needs into a distrobox container. As this resolved my issue (video not showing or playing, locking up), I want to make sure this is available for other users to potentially use.

--BLusk (talk) 02:28, 7 October 2025 (UTC)

A better way for user fonts in Text+

It would be better to advise users to change Fusion paths using the menu option "Fusion > Fusion Settings... > Path Map" Then editing "Fonts:" to add /home//.local/share/fonts; which makes fusion look under the user fonts, making symlinks unnecessary.

P.S: Since i'm new to editing wikis i wanted to get feedback first instead of editing it right away Freax (talk) 17:44, 1 November 2025 (UTC)

DaVinci Resolve Replay Editor Needed Additional Work

I recently got a DaVinci Resolve Replay Editor working with Resolve 21 on Arch Linux, but it required a few Arch-specific fixes that may be worth documenting in the main article.

The initial symptoms were:

• The Replay Editor was visible in `lsusb`.
• DaVinci Control Panels Setup detected it correctly.
• Resolve itself did not recognise it.
• The Jog button stayed unlit.
• `DaVinciPanelDaemon` was not running automatically.

The device identifies as:

1edb:da11 Blackmagic Design DaVinci Resolve Replay Editor

USB udev rule

The packaged rule at:

/usr/lib/udev/rules.d/99-DavinciPanel.rules

only matched vendor ID `096e`. I added:

/etc/udev/rules.d/99-davinci-replay-editor.rules

with:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1edb", ATTRS{idProduct}=="da11", MODE="0666"

Panel API libraries

Resolve logged:

*** InitFairlightPanelInformation[53]: /usr/lib64/libFairlightPanelAPI.so: cannot open shared object file: No such file or directory

The libraries were present under:

/opt/resolve/libs/libDaVinciPanelAPI.so
/opt/resolve/libs/libFairlightPanelAPI.so

On Arch, `/usr/lib64` points to `/usr/lib`, so I added:

sudo ln -s /opt/resolve/libs/libDaVinciPanelAPI.so /usr/lib/libDaVinciPanelAPI.so
sudo ln -s /opt/resolve/libs/libFairlightPanelAPI.so /usr/lib/libFairlightPanelAPI.so

Before this, manually launching `DaVinciPanelDaemon` produced:

Failed to create listener
Unsupported DaVinci Panel API Version (0.0), please update

After adding the symlinks it reported:

Resolve communication is open and waiting..
DaVinci Panel API Version: 1.0

hidraw permissions

The Replay Editor also exposed a `/dev/hidraw*` device with permissions:

crw-------

This prevented Resolve from using the panel even though Control Panels Setup could see it. I added:

/etc/udev/rules.d/99-davinci-replay-editor-hidraw.rules

with:

KERNEL=="hidraw*", ATTRS{idVendor}=="1edb", ATTRS{idProduct}=="da11", MODE="0666"

After reloading udev rules and reconnecting the panel, the hidraw node became writable and the Replay Editor immediately began working. The Jog button illuminated, and the jog wheel, transport controls, and In/Out controls all worked correctly.

I also tested replacing `MODE="0666"` with `TAG+="uaccess"`, but on this system the hidraw node reverted to `crw-------` and the Replay Editor stopped working.

After these changes, `DaVinciPanelDaemon` also started automatically with Resolve.

This was tested on Resolve 21 with Replay Editor firmware 1.6. It may be worth adding a short troubleshooting section to the main DaVinci Resolve article, and possibly updating the packaged udev rule to account for newer Blackmagic vendor IDs.

~~~~ Apex-a (talk) 04:20, 14 September 2026 (UTC)

Nice. I'm not sure which of the packages you used, but these read like issues for packaging (creating symlinks, udev rules). Maybe you can add an AUR comment so your troubleshooting can be used. --Indigo (talk) 16:25, 14 September 2026 (UTC)

Thanks, I have now posted this info to the aur. Hopefully it can be picked up. Apex-a (talk) 02:57, 15 September 2026 (UTC)

Failure to Start / Missing Directories

Right after installing the application, starting it resulted in an immediate termination of the application. Launching it inside a terminal yielded the following:

ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
log4cxx: No appender could be found for logger (BtCommon).
log4cxx: Please initialize the log4cxx system properly.
Failed to create application support directories.

Checking it with strace, this showed that it tried writing to multiple directories within /opt/resolve, which was owned by root instead of me. This was ultimately fixed by running the application once as root via sudo.

Is this the "proper" way to fix it? Probably not. It would be better to manually create the necessary directories. Or alternatively, letting /opt/resolve be owned by your own user. This is likely the second-easiest fix on a single-user installation (single user as in a single physical person using the computer).

I hope this helps.

Full strace code here:

strace -f -e trace=mkdir,mkdirat,access,stat,openat davinci-resolve 2>&1 | grep -iE 'denied|no such|mkdir'

MechMK1 (talk) 01:27, 16 September 2026 (UTC)

Automated AAC sidecars for Studio

The AAC workaround section currently documents remuxing audio with ffmpeg.

I created an open-source script that generates a PCM WAV sidecar and links it  to the original clip through Resolve's scripting API, avoiding a video  re-encode. Would a short, neutral link to this alternative fit in the Studio  workaround section?

https://github.com/jkutterer/resolve-aac-sidecars

  --~~~~

Jkutterer (talk) 15:22, 19 September 2026 (UTC)

Linking it? Sure, just go ahead. Perhaps you or someone packages your scripts for the AUR next. --Indigo (talk) 19:53, 20 September 2026 (UTC)

I've linked your edit into the tip above it, guessing the bullets fit well. You're welcome to pull it out again if not. --Indigo (talk) 18:24, 21 September 2026 (UTC)

Perfect. Thank you. Jkutterer (talk) 08:29, 22 September 2026 (UTC)