Package Details: davinci-resolve-studio 16.2.5-1

Git Clone URL: (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:
Keywords: blackmagic davinci editor resolve studio video
Licenses: Commercial
Conflicts: davinci-resolve, davinci-resolve-beta, davinci-resolve-studio
Provides: davinci-resolve
Submitter: codibit
Maintainer: deezid (satriani)
Last Packager: satriani
Votes: 11
Popularity: 0.76
First Submitted: 2018-01-21 18:37
Last Updated: 2020-08-05 14:51

Pinned Comments

satriani commented on 2019-10-21 09:54

With this new version, you no longer need to download the ZIP file from the Blackmagic Design website. The script does it automatically.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

codibit commented on 2019-07-08 08:06

Well, please do let me know if you get any fix working for that, I do not have a license code, so I can't test that out (I use a dongle) plus I am unable to use Resolve in archlinux in my main device due to it being powered by an AMD graphics card.

paperbenni commented on 2019-07-05 13:57

Ok, so I found out more about the issue of not being able to activate resolve on arch. If you already have 2 installations (doesn't matter if they still exist), activating a third one should automatically deactivate the other 2 and get the third one working. Now turns out arch is able to activate but not deactivate resolve from the setup window (you can deactivate an activated install). I asked support for deactivating my installations and it worked. Using a windows machine (eww) or a supported distro for deactivating occupied instances should work. Maybe it doesn't accept the arch user agent (which is just a generic Linux one i think), but this problem won't get fixed by bmd. Maybe we could spoof some stuff in the installer, or leave a reminder to manually deactivate your installations before uninstalling or upgrading them.

alnippy commented on 2019-06-15 19:12

I am having the exact same issue as paperbenni. I have tried resolve studio 15 and 16, multiple versions. I am able to activate under windows with no issues. I have contacted tech support and they simply said Arch is not supported. I had studio 15 activated months ago under arch but after a re-install I have been unable to activate. I have tried as sudo and with no firewall. Has anyone figured this out?

codibit commented on 2019-05-27 06:27

To @mikehash, you flagged as out of date with the comment ´lib32-libpng12 is not available anymore on AUR. vlib32-libpng14 and lib32-libpng15 are available´ but the package is still available in the official repos (not aur), please check

paperbenni commented on 2019-05-01 17:09

"There was an error when attempting to perform the activation. Please contact Blackmagic Design support for assistance. I tried running as sudo. The license key is correct and it was able to clear out other activations. Occurs with and without sudo, both in dr 15 and 16. What causes this? I'm not behind any firewall or vpn.

codibit commented on 2019-04-22 20:55

I updated the PKGBUILD to be (almost) exactly the same as the davinci-resolve package by @satriani.

I propose another way of declaring some variables so that the maintenance of the package is simpler (avoid having to search and replace everywhere where the package .zip archive or .run installer are called.

`if [ ${pkgname} == "davinci-resolve-studio" ]; then

Variables for STUDIO edition
pkgdesc='Professional A/V post-production software suite from Blackmagic Design. Studio edition, requires license key or license dongle.'
conflicts=('davinci-resolve-beta' 'davinci-resolve' 'davinci-resolve-studio-beta')


Variables for FREE edition
pkgdesc='Professional A/V post-production software suite from Blackmagic Design'
conflicts=('davinci-resolve-beta' 'davinci-resolve-studio' 'davinci-resolve-studio-beta')


As the packages are released at the same time, both the sha256sums can be added to their corresponding places, and only the pkgname needs to be changed from davinci-resolve to davinci-resolve-studio.

@satriani, please let me know if you like the proposal :) I also see you added a davinci-resolve-studio-beta package, but it seems to have some mistakes (in the archive name). Please consider this changes to avoid things like that.

Also, I'd like to add you as a mantainer to this version as well, if you'd like to be.

P.S. I seem to be unable to properly add the CODE syntax to this comment :/

deezid commented on 2019-02-12 11:44

fast update! Was about to work on the pkgbuild today :D

satriani commented on 2019-02-07 10:14

@codibit, for example: The prepare function is unusable because the archive file is already extracted before. We also do not need xorriso anymore, this is done perfectly with bsdtar. Just take a look at my PKGBUILD here:

codibit commented on 2019-02-07 09:07

@satriani, thanks for the heads up, which bugs do you mean?

satriani commented on 2019-02-06 22:10

@codibit, since the last update of my package almost everything has changed. Maybe your package works as it is, but it contains some useless bugs and does not correspond to the original. I recommend you to change your package based on mine.