Package Details: davinci-resolve-studio 15.3.1-2

Git Clone URL: https://aur.archlinux.org/davinci-resolve-studio.git (read-only)
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: Commercial
Conflicts: davinci-resolve, davinci-resolve-beta, davinci-resolve-studio-beta
Provides: davinci-resolve
Submitter: codibit
Maintainer: codibit (deezid, satriani)
Last Packager: codibit
Votes: 4
Popularity: 0.133915
First Submitted: 2018-01-21 18:37
Last Updated: 2019-04-22 20:49

Latest Comments

1 2 3 4 Next › Last »

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.'
_archive_name=DaVinci_Resolve_Studio_${pkgver}_Linux
sha256sums=('0c81412ee915d06bd744c750a44a04ef614a6c0518a1677ef146f0b1817070ca')
conflicts=('davinci-resolve-beta' 'davinci-resolve' 'davinci-resolve-studio-beta')

else

Variables for FREE edition
pkgdesc='Professional A/V post-production software suite from Blackmagic Design'
_archive_name=DaVinci_Resolve_${pkgver}_Linux
sha256sums=('6ac9a8b06c848567e9add85e086cb9d7ac4a4bb51da9805cb688c9461392aa9f')
conflicts=('davinci-resolve-beta' 'davinci-resolve-studio' 'davinci-resolve-studio-beta')

fi`

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: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=davinci-resolve

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.

codibit commented on 2019-02-05 07:16

@deezid, I just added you as a comaintainer. I think the fresh install issue could be a permission thing or something like that. Are you using a license key or a dongle? It didn't happen in my case, with a Dongle. Maybe we have a regression after all the changes for the new package version, as there was something like that happening before.

deezid commented on 2019-02-04 12:03

Hey, sorry to hear that. Hopefully everything is ok.

About the package. I can offer help updating the PKGBUILD (incremental updates at least which don't require too many changes) and since I'm active in several Davinci Resolve groups and forums I'll know when there's an update. There's no other source for notifications that I know of.

Btw. the .destkop file works. Pinning works with no duplicated icons. :)

Another thing I have noticed is that the computer has to be rebooted after installing or updating Davinci Resolve (Studio). Otherwise it'll only run as root or sudo. Do you have any idea what kind of problem is causing it? EDIT: It's only after a fresh install. After an update I don't have to reboot. Just tried it lol

If it can't be fixed there should be at least some kind of information somewhere I think.

codibit commented on 2019-02-04 08:39

hi, i'm just back from a family emergency :/ I updated the package to the latest version and added StartupWMClass=resolve to the .desktop file as suggested by @deezid. I think I can still update the package myself, but will consider adding comantainers in the future, thanks @deezid. Does anyone know where can we get notifications about new resolve versions? I usually get notifications from the comments here :)

deezid commented on 2019-02-03 22:49

Do you need help updating? Would offer helping with maintaining since I'm using this program 24/7.