Package Details: davinci-resolve 18.6.6-4

Git Clone URL: https://aur.archlinux.org/davinci-resolve.git (read-only, click to copy)
Package Base: davinci-resolve
Description: Professional A/V post-production software suite from Blackmagic Design
Upstream URL: https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion
Keywords: blackmagic davinci editor resolve video
Licenses: Commercial
Conflicts: davinci-resolve-beta, davinci-resolve-studio, davinci-resolve-studio-beta
Submitter: jonathon
Maintainer: satriani
Last Packager: satriani
Votes: 135
Popularity: 3.57
First Submitted: 2017-04-19 20:57 (UTC)
Last Updated: 2024-06-19 20:45 (UTC)

Dependencies (24)

Required by (0)

Sources (1)

Pinned Comments

satriani commented on 2021-05-15 14:15 (UTC) (edited on 2021-05-15 14:16 (UTC) by satriani)

Issues and bugs, please report on the official forum here: https://forum.blackmagicdesign.com/viewforum.php?f=21&sid=239f0d5c49abe5d6a635b69638192e9a Thank you!

Visit DaVinci Resolve - ArchWiki before installing: https://wiki.archlinux.org/title/DaVinci_Resolve

ATTENTION: Please don't flag this package as out-of-date before beta version has been released as stable!

This is a current stable Package!

The current free beta is available here: https://aur.archlinux.org/packages/davinci-resolve-beta/

And for current studio beta here: https://aur.archlinux.org/packages/davinci-resolve-studio-beta/

Thanks.

Latest Comments

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 52 Next › Last »

bartus commented on 2019-03-05 14:20 (UTC)

There is a problem with chroot build introduced in #7cf524bc commit. Basically, you can't use logname as there is no user present (null output, warning on stderr: logname: no login name). If you need to change file permissions, please do it in postinstall script.

Ashark commented on 2019-02-10 18:33 (UTC)

@Harpy1991 opencl-driver is already in the dependencies list.

Harpy1991 commented on 2019-02-10 18:30 (UTC)

i had to install opencl for it to work. it did not install automaticaly. but even the official read me that comes with it does not mentions you need it. i had to check the debug files.

you might as well do us the favor of add opencl to the dependencies to install this here. it was the opencl for my nvidia drivers, and its dependencies

codibit commented on 2019-02-04 09:04 (UTC)

The way I see the StartupWMClass thing, it is defined within the specification (https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html) and might be useful for some use cases, while not producing negative effects for other ones. I added it to the studio version, as when run from the provided .desktop application link it is working properly. Let's not forget that there are many window managers and desktop environments.

Ashark commented on 2019-02-04 07:41 (UTC)

@deezid adding StartupWMClass=resolve does nothing in kde and gnome, it does not resolve a problem of wrong file pinning and icon duplication. To avoid duplication and pixilated icon, just drag a desktop file from /usr/share/applications (not from other place) to latte-dock. Do not pin an icon that appeared in latte-dock after starting application. See this: https://youtu.be/kPg5A3m3p1A

deezid commented on 2019-02-03 22:50 (UTC)

@psifidotos: That's exactly what I meant. In Gnome I can't even add the starter to the dock until I add this line to the .desktop file.

psifidotos commented on 2019-02-01 13:56 (UTC)

I think that @deezid is referring to that issue/fix : https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-my-launcher-and-its-window-are-not-associated-correctly-or-my-launcher-is-using-a-low-resolution-icon

I am the Latte developer and I do not know if that is the case but based on your https://www.youtube.com/watch?v=rS_ZXiPxZEY video I would guess that it is.

Ashark commented on 2019-02-01 04:02 (UTC) (edited on 2019-02-04 11:15 (UTC) by Ashark)

@deezid I still do not got the reason what problem does adding of StartupWMClass=resolve to the desktop file solves. See: https://youtu.be/rS_ZXiPxZEY

@satriani Thanks for adding tested configurations to pinned comment. Also, lets check dependency list finally. They were made even for version 12, I suspect they could be not required for now. Can you help?

satriani commented on 2019-01-27 18:44 (UTC)

@jose1711 Did you report this issue in the BM forum? I think this looks like a driver problem. Try to uninstall the program completely and install it again.

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 52 Next › Last »