| Git Clone URL: | https://aur.archlinux.org/davinci-resolve-studio.git (read-only, click to copy) |
|---|---|
| Package Base: | davinci-resolve-studio |
| Description: | Professional A/V post-production software suite from Blackmagic Design. Studio edition, requires license key or license dongle. |
| Upstream URL: | https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion |
| Keywords: | blackmagic davinci editor resolve studio video |
| Licenses: | LicenseRef-Commercial |
| Conflicts: | davinci-resolve, davinci-resolve-beta, davinci-resolve-studio-beta |
| Submitter: | codibit |
| Maintainer: | Muflone |
| Last Packager: | Muflone |
| Votes: | 49 |
| Popularity: | 2.26 |
| First Submitted: | 2018-01-21 18:37 (UTC) |
| Last Updated: | 2025-09-13 23:43 (UTC) |
A recent full system upgrade stopped DaVinci Resolve Studio from opening previously saved projects. I use an AMD GPU and when I compiled and installed opencl-amd Davinci Resolve Studio was once again able to load previously saved projects.
Could you add this aur package as one of the optional opencl drivers on the web site incase others are having the same problem.
@adlerweb I definitely did when I was trying last night. Tried again this evening and had the following results. First attempt failed with the "Your account does not have a DaVinci Resolve Studio License attached". So I went back and cleared the device from the cloud portal and tried again. This time was successful. Feeling pretty silly now. Thank you for your help.
@apex-a: Did you set the required permissions as documented before trying to assign a license?
I can't verify my cloud license. First attempt to verify returns an "Unable to communicate with the Blackmagic Cloud servers" error, second attempt returns "Your account does not have a DaVinci Resolve Studio License attached". Checking my account shows that a license has been assigned to my computer. So at least something happened. Is this likely an Arch issue? Or a Blackmagic issue?
Davinci refuses to download any extra since it expects RHEL's ca-bundles.crt path. Can you add a symlink between Arch's ca-certificates.crt and RHEL's ca-bundles.crt in the PKGBUILD?
I believe this line would solve the issue:
install -d -m 0755 "${pkgdir}/etc/pki/tls/certs"
ln -s /etc/ssl/certs/ca-certificates.crt \
"${pkgdir}/etc/pki/tls/certs/ca-bundle.crt"
Upgrading to mesa 1:25.2.0-1 seems to break resolve, "Failed to create OpenCL context, Unknown CL error. (-1000)" in logs and blank screen instead of video/pictures. Downgrading to mesa 1:25.1.7-1 is a temporary fix that worked for me
https://www.blackmagicdesign.com/support/ has a large archive of all of their downloadable products.Sorry for my false claim that version 20.0.1 did not exist.
@rev.cressy: Can't confirm - it is still listed in their download center. https://www.blackmagicdesign.com/de/support/download/4cda8043eecf4c00a40a781dffed2bc9/Linux
By the way DaVinci_Resolve_Studio_20.0.1_Linux.zip is no longer available on Black Magic's web site.
@Bink I see. Thanks for explaining.
Pinned Comments
vawaver commented on 2025-06-01 05:52 (UTC)
Since DaVinci Resolve Studio cannot be installed directly via AUR helpers like
paruoryay, I suggest adding and pinning a clear step-by-step guide for beginners explaining how to build and install the package from the local installer.The instructions should also include how to obtain the required .zip file from the official Blackmagic Design website:
Such a guide would be helpful for users new to Arch-based systems who legally own a DRS license but are unfamiliar with manual package building.
Muflone commented on 2025-01-26 02:15 (UTC)
IMPORTANT!
Since version 19.1.3-2 this package will not download automatically the source file from the upstream site.
To build this package you will need to manually download the file from https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion and place it in the same directory with the PKGBUILD.
This would reduce the mess in this package, making it more readable and clear. Also bypassing the required information from the upstream URL is not allowed in an automated way.