davinci-resolve and davinci-resolve-studio: fix panel support and add missing applications

[httpdev]

This commit fixes #366384, #364991, #364646, and possibly (untested) #168789.

It also adds several applications that are bundled with Resolve but were not supported yet:

• DaVinci Control Panels Setup
• DaVinci Remote Monitor
• Blackmagic RAW Player
• Blackmagic RAW Speed Test
• External Python scripting

This required some refactoring, so I am submitting this PR for discussion and expect that it would require some changes before accepting.

Changes:

• Adds a number of missing dependencies required by the new applications.
• The binary libraries required for the panels to work are now unpacked from share/panels/dvpanel-framework-linux-x86_64.tgz into lib so that they can be found from within the FHS environment.
• The FHS environment formerly directly executed bin/resolve via runScript (discarding command line arguments). This did not allow to run the other supplied applications in the same FHS, therefore it now functions as a wrapper that can be called with the command+arguments to run. For debugging, the package also has a bin/davinci-resolve-*-fhs command, which starts a shell in the FHS environment.
• The main package is now created using symlinkJoin to have better control of which files are linked where. The main package only includes the application links in bin/, udev rules in etc/udev/rules.d/, and desktop items in share/applications/.
• The udev rules now follow the same naming and priority as when installing Resolve on Non-NixOS. These files were formerly only mapped from the unpacked archive (99-*.rules), but in the Resolve install script they are actually modified and a new file is added for the dongle, which results in 75-davincipanel.rules, 75-davincikb.rules, and 75-sdx.rules (new).
• Desktop items for the new applications are added and the main desktop item now has mimeTypes set.
• MIME types XML and icons are installed into the XDG directory structure
• A longDescription is added to hint to the fact that the package needs to be added to services.udev.packages in order for the panels to work, which was not documented, and includes comments about scripting.

I have tested using a DaVinci Resolve Micro Panel and DaVinci Resolve Speed Editor, which work including updating the firmware using the Control Panels Setup application. I do not have access to panels with a display, so I am not sure if they require the supplied daemon, which would require additional setup.

External scripting works with DaVinci Resolve Studio. Icons are correctly displayed on GNOME, Resolve project files (.drp) are correctly opened by Resolve, and RAW file (.braw) open the RAW player (see the three clips that can be downloaded on this page for testing).

I have tested the automatic update script and it still works as far as I can tell.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[jshcmpbll]

This all seems sane and we greatly appreciate the work @httpdev

I'll have to do some testing when I have time but I'm glad there is someone with the physical davinci panels and knows nix. That vent diagram is quite small haha

[amarshall]

Thanks for your contribution. Please read the contributing guide, in particular the section on commit conventions. The commits here need to be renamed to match convention, as well as be atomic and semantic. The PR is a bit difficult to review as-is, as there are a lot of redundant commits, and not all commits are explained by their commit message, so it’s challenging to understand why some things are being changed.

I added some inline comments but stopped quickly as it was, as above, challenging to follow along.

TL;DR: Please reorganize so commits are smaller, discrete changes that are independently useful, rather than having commits make many unrelated changes. Also avoid having commits that only fix issues with earlier ones—instead amend-in the changes. There’s a lot of detail in the PR description—instead much of that should be in the discrete commit messages so it’s easy to follow and link the why to the what.

[httpdev]

Thanks for your contribution. Please read the contributing guide, in particular the section on commit conventions. The commits here need to be renamed to match convention, as well as be atomic and semantic. The PR is a bit difficult to review as-is, as there are a lot of redundant commits, and not all commits are explained by their commit message, so it’s challenging to understand why some things are being changed.

I added some inline comments but stopped quickly as it was, as above, challenging to follow along.

TL;DR: Please reorganize so commits are smaller, discrete changes that are independently useful, rather than having commits make many unrelated changes. Also avoid having commits that only fix issues with earlier ones—instead amend-in the changes. There’s a lot of detail in the PR description—instead much of that should be in the discrete commit messages so it’s easy to follow and link the why to the what.

Thanks for the review. I understand, this is my first contribution to nixpkgs, so I'm not used to the conventions.

I'm not sure how to split into independent commits. There are basically two parts: supporting the other utilities, and fixing the panel udev issues. Supporting the other utilities requires separating out the FHS environment into a separate derivation, which needs some reorganization. Supporting the panel setup tool without fixing the panel udev issues doesn't make sense, and fixing the udev issues and then reorganizing them anyway in the next commit also doesn't seem useful.

[httpdev]

Hello, I have restructured the pull request. When requesting further changes, I kindly ask to consider that debugging the hardware issues and missing dependencies alone was more than 30 hours of work.

[httpdev]

Nevermind, I have found some more time to work on this. It was a bit tricky because the binary distribution is a mess - it consists of several binaries which each come with their own (incompatible) .so libraries. This required a slight modification to the wrapper so they can each live in their own happy space.

The RAW player is now working and all MIME types are correctly added with their icons. I have also added a command davinci-resolve-studio-python which runs Python inside the FHS environment and allows external scripting. An example is in the longDescription.

I have edited the top comment to reflect the changes.