Talk:DaVinci Resolve - Revision history

Stencill: /* AMD GPU issue */

2025-10-21T12:07:26Z

AMD GPU issue

← Older revision		Revision as of 12:07, 21 October 2025
Line 63:		Line 63:

	``` [[User:Stencill\|Stencill]] ([[User talk:Stencill\|talk]]) 11:44, 21 October 2025 (UTC)		``` [[User:Stencill\|Stencill]] ([[User talk:Stencill\|talk]]) 11:44, 21 October 2025 (UTC)

			EDIT: It does not crash anymore like so but poses other issues such as not showing the clips and thumbnails.

Stencill: /* AMD GPU issue */ new section

2025-10-21T11:44:52Z

AMD GPU issue: new section

← Older revision		Revision as of 11:44, 21 October 2025
Line 43:		Line 43:

	Another solution is setting it with home.file but this felt more nix like using home-manager's available options		Another solution is setting it with home.file but this felt more nix like using home-manager's available options

			== AMD GPU issue ==

			the proposed amd gpu configuration resulted in crashing after running davinci-resolve. The previous discussion already mentioned probably the same issue. I could fix it with another approach though:

			```

			hardware = {

			graphics = {

			enable = true;

			};

			amdgpu.opencl.enable = true;

			};

			``` [[User:Stencill\|Stencill]] ([[User talk:Stencill\|talk]]) 11:44, 21 October 2025 (UTC)

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */

2025-09-19T21:23:11Z

Hotkeys not working while using the Global Menu widget on KDE

← Older revision		Revision as of 21:23, 19 September 2025
Line 42:		Line 42:
	</syntaxhighlight>		</syntaxhighlight>

	Another solution is setting it with home.file but this felt more nix like using home-manager's available		Another solution is setting it with home.file but this felt more nix like using home-manager's available options

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */

2025-09-19T21:04:49Z

Hotkeys not working while using the Global Menu widget on KDE

← Older revision		Revision as of 21:04, 19 September 2025
Line 34:		Line 34:
	type = "Application";		type = "Application";
	categories = [		categories = [
	"AudioVideo"		"AudioVideo"
	"AudioVideoEditing"		"AudioVideoEditing"
	"Video"		"Video"
	"Graphics"		"Graphics"
	];		];
	};		};

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */

2025-09-19T21:04:09Z

Hotkeys not working while using the Global Menu widget on KDE

← Older revision		Revision as of 21:04, 19 September 2025
Line 22:		Line 22:
	comment = "Professional video editing, color, effects and audio post-processing";		comment = "Professional video editing, color, effects and audio post-processing";
	exec =		exec =
	let		let
	script = pkgs.writeShellScriptBin "resolve-wrapper" ''		script = pkgs.writeShellScriptBin "resolve-wrapper" ''
	#!/bin/sh		#!/bin/sh
	qdbus org.kde.kded6 /kded org.kde.kded6.unloadModule appmenu		qdbus org.kde.kded6 /kded org.kde.kded6.unloadModule appmenu
	exec ${pkgs.davinci-resolve}/bin/davinci-resolve "$@"		exec ${pkgs.davinci-resolve}/bin/davinci-resolve "$@"
	qdbus org.kde.kded6 /kded org.kde.kded6.loadModule appmenu		qdbus org.kde.kded6 /kded org.kde.kded6.loadModule appmenu
	'';		'';
	in		in
	"${script}/bin/resolve-wrapper %U";		"${script}/bin/resolve-wrapper %U";
	icon = "davinci-resolve";		icon = "davinci-resolve";
	type = "Application";		type = "Application";

Sophimoo at 20:46, 19 September 2025

2025-09-19T20:46:17Z

← Older revision		Revision as of 20:46, 19 September 2025
Line 11:		Line 11:
	</syntaxhighlight>		</syntaxhighlight>
	I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P		I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P

			== Hotkeys not working while using the Global Menu widget on KDE ==

	When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.		When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */

2025-09-19T20:45:07Z

Hotkeys not working while using the Global Menu widget on KDE

← Older revision		Revision as of 20:45, 19 September 2025
Line 11:		Line 11:
	</syntaxhighlight>		</syntaxhighlight>
	I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P		I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P

	~~== Hotkeys not working while using the Global Menu widget on KDE ==~~

	When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.		When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.
Line 42:		Line 40:
	</syntaxhighlight>		</syntaxhighlight>

	Another solution is setting it with home.file but this felt more nix like using home-manager's available ~~options[[User:Sophimoo\|Sophimoo]] ([[User talk:Sophimoo\|talk]]) 20:42, 19 September 2025 (UTC)~~		Another solution is setting it with home.file but this felt more nix like using home-manager's available

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */

2025-09-19T20:44:10Z

Hotkeys not working while using the Global Menu widget on KDE

@@ Line 16: / Line 16: @@
 When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.
-```
+<syntaxhighlight lang="nix">
-   xdg.desktopEntries.davinci-resolve = {
+Another solution is setting it with home.file but this felt more nix like using home-manager's available options[[User:Sophimoo|Sophimoo]] ([[User talk:Sophimoo|talk]]) 20:42, 19 September 2025 (UTC)

Sophimoo: /* Hotkeys not working while using the Global Menu widget on KDE */ new section

2025-09-19T20:42:42Z

Hotkeys not working while using the Global Menu widget on KDE: new section

← Older revision		Revision as of 20:42, 19 September 2025
Line 11:		Line 11:
	</syntaxhighlight>		</syntaxhighlight>
	I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P		I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P

			== Hotkeys not working while using the Global Menu widget on KDE ==

			When using the global menu widget on kde, all hotkeys/inputs will be ignored while davinci resolve is the active window. Using the following home-manager xdg.desktop entry will fix this.

			```

			xdg.desktopEntries.davinci-resolve = {

			name = "Davinci Resolve";

			genericName = "Video Editor";

			comment = "Professional video editing, color, effects and audio post-processing";

			exec =

			let

			script = pkgs.writeShellScriptBin "resolve-wrapper" <nowiki>''</nowiki>

			#!/bin/sh

			qdbus6 org.kde.kded6 /kded org.kde.kded6.unloadModule appmenu

			exec ${pkgs.davinci-resolve}/bin/davinci-resolve "$@"

			qdbus6 org.kde.kded6 /kded org.kde.kded6.loadModule appmenu

			<nowiki>''</nowiki>;

			in

			"${script}/bin/resolve-wrapper %U";

			icon = "davinci-resolve";

			type = "Application";

			categories = [

			"AudioVideo"

			"AudioVideoEditing"

			"Video"

			"Graphics"

			];

			};

			```

			Another solution is setting it with home.file but this felt more nix like using home-manager's available options [[User:Sophimoo\|Sophimoo]] ([[User talk:Sophimoo\|talk]]) 20:42, 19 September 2025 (UTC)

Samueldr: fixed deprecated syntax

2024-04-05T01:34:09Z

fixed deprecated syntax

← Older revision		Revision as of 01:34, 5 April 2024
Line 1:		Line 1:
	== AMD GPU not discovered ==		== AMD GPU not discovered ==
	I had to fix it with the following additions to configuration.nix		I had to fix it with the following additions to configuration.nix
	<~~source~~ lang="nix">		<syntaxhighlight lang="nix">
	hardware.opengl = {		hardware.opengl = {
	enable = true;		enable = true;
Line 9:		Line 9:
	];		];
	};		};
	</~~source~~>		</syntaxhighlight>
	I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P		I'm not sure of the formal way nor the deeper workings of such drivers but the fix should be provided in the Wiki somehow in order to save people from the pain that I just went through :P