DaVinci Resolve: Difference between revisions
fix: rename hardware.opengl -> hardware.graphics |
Added a section describing how to use OpenFX Plugins with DaVinci Resolve. It is worth noting that I am not aware of how many OpenFX Plugins are packaged in nixpkgs, as I am using this feature with plugins installed via a flake. |
||
| Line 120: | Line 120: | ||
<code>ROC_ENABLE_PRE_VEGA=1 RUSTICL_ENABLE=amdgpu,amdgpu-pro,radv,radeon,radeonsi DRI_PRIME=1 QT_QPA_PLATFORM=xcb davinci-resolve</code> | <code>ROC_ENABLE_PRE_VEGA=1 RUSTICL_ENABLE=amdgpu,amdgpu-pro,radv,radeon,radeonsi DRI_PRIME=1 QT_QPA_PLATFORM=xcb davinci-resolve</code> | ||
== OpenFX Plugins == | |||
The usual install location <code>/usr/OFX/Plugins</code> is not available on NixOS. Fortunately, DaVinci Resolve supports loading OpenFX plugins from locations specified in <code>OFX_PLUGIN_PATH</code>. This environment variable can be configured comfortably by adding the following code listing to the system configuration:<syntaxhighlight lang="nixos"> | |||
environment.variables = { | |||
OFX_PLUGIN_PATH = lib.concatStringsSep ";" [ | |||
# specify plugin packages here | |||
]; | |||
}; | |||
</syntaxhighlight>Plugins usually contain a directory called <code>$PLUGINNAME.ofx.bundle</code> with a <code>.ofx</code> file somewhere inside of it. Since the coercion of a package to a string outputs its store location and the paths specified in the environment variable are traversed recursively, it is not necessary to specify the precise location of the ofx bundle in the nix store. | |||
== Troubleshooting == | == Troubleshooting == | ||
=== Resolve crashes/fails to start === | === Resolve crashes/fails to start === | ||
If it doesn't launch, and crashes when running <code>davinci-resolve</code>, then try running it as root. | If it doesn't launch, and crashes when running <code>davinci-resolve</code>, then try running it as root. | ||