Exempt DaVinci Resolve from default window opacity - #6382
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Hyprland window-rule config so DaVinci Resolve windows aren’t affected by the global default-opacity tag, preventing unintended translucency that can distort color-critical grading.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Changes:
- Extend the existing DaVinci Resolve window rule to remove the
default-opacitytag. - Force Resolve windows to remain fully opaque via
opacity = "1 1". - Expand the inline comment to explain why Resolve is exempted.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
28allday
added a commit
to 28allday/DaVinci-Resolve-Omarchy
that referenced
this pull request
Jul 29, 2026
Rebased onto the Omarchy 4 update (4857667), which the branch these commits came from predated. Kept both sides: - the O4 fixes stay (per-package pacman installs, gtk2 dropped, wrapper unsets QT_STYLE_OVERRIDE/QT_QPA_PLATFORMTHEME) - the full-opacity block stays alongside the new rules, noted as redundant on Omarchy >= basecamp/omarchy#6382 but still needed on older 4.x builds README renumbered accordingly and the "002 not fully verified" note dropped, since both fixes are now verified end-to-end. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default-opacity tag (0.985 focused / 0.96 unfocused) currently applies to DaVinci Resolve, so the viewer and scopes render slightly translucent over the wallpaper. For a colour-grading app that visibly shifts what you're looking at, in the same way it would for video playback — which is why the browser video/PiP, qemu, and RetroArch rules already opt out.
This adds the same opt-out to the existing Resolve rule (
tag = "-default-opacity", opacity = "1 1"), mirroringretroarch.lua.Running 4.0.0.alpha (r1373) with Resolve 21 under XWayland here; verified locally with an equivalent user-level opacity override (loads clean, no interaction with the float/stay_focused handling).