Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support color management protocols #8715

Merged
merged 15 commits into from
Jan 7, 2025
Merged

Support color management protocols #8715

merged 15 commits into from
Jan 7, 2025

Conversation

UjinT34
Copy link
Contributor

@UjinT34 UjinT34 commented Dec 14, 2024

Describe your PR, what does it fix/add?

Add support for color management protocols xx-color-management-v4 and frog-color-management-v1. Will only store and pass color management properties. The actual CM should be implemented by someone else with means to verify that it works as expected. Passing hdr metadata without processing should be enough for fullscreen gaming.

experimental:wide_color_gamut sets the colorspace to BT2020_RGB. Might not be needed.
experimental:xx_color_management_v4 enables both protocols. Requires restart.
experimental:hdr forces hdr in desktop mode. Will look weird without proper CM.

Works only with correctly parsed EDID CTA-861 block. Will not work with hdr data from DisplayID blocks.

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)

Mostly copied code from other protocols. Might mess with pointers, have some redundant stuff and miss some bits.
Tested only the frog protocol. Most of the clients support both or frog only and will choose frog by default.

Is it ready for merging, or does it need work?

Ready. Requires hyprwm/aquamarine#112

  • xx-color-management-v4
  • frog-color-management-v1
  • send hdr metadata

@vaxerski
Copy link
Member

ref #4933

@vaxerski
Copy link
Member

I'd also mark this as draft

@UjinT34
Copy link
Contributor Author

UjinT34 commented Dec 15, 2024

Frog CM can be tested. Most of the gaming stuff https://wiki.archlinux.org/title/KDE#HDR should work the same. I use https://github.com/Zamundaaa/VK_hdr_layer

Will only work with successfully parsed EDID and fullscreen applications.

@vaxerski
Copy link
Member

idek how to test it or how to spot the difference. Only piece of equipment I have with hdr is my laptop

@UjinT34
Copy link
Contributor Author

UjinT34 commented Dec 15, 2024

AQ_TRACE=1 HYPRLAND_TRACE=1 and believe what logs say %)
Without the support hdr setting in games is not available. With incorrect support enabling hdr will result in obviously wrong colors (undersaturated/oversaturated/too dim/too bright). The tricky part is to spot slightly wrong colors. I guess some colorimetry equipment might be needed.
Laptop might not work hyprwm/aquamarine#116. Mine doesn't.

@vaxerski
Copy link
Member

well then I can't test. My monitors are old, garbage TN panels. No HDR here.

@abihf
Copy link

abihf commented Dec 16, 2024

Nice work @UjinT34

I tried mpv and Silent Hill 2, they seem work. But I need to manually set experimental:hdr=true . Also my second monitor isn't back to sdr after I disable the option.

I will try to compare the color with KDE later.

EDIT: I was wrong, I don't need to enable desktop hdr.

@TKasperczyk
Copy link

TKasperczyk commented Dec 18, 2024

I confirmed it's working in MPV using the following demo: https://4kmedia.org/lg-new-york-hdr-uhd-4k-demo/

Log samples:

[TRACE] ColorManagement supportsBT2020 true, supportsPQ true
[TRACE] ColorManagement primaries 0.677734375,0.3134765625 0.283203125,0.6484375 0.1484375,0.068359375 0.3125,0.3291015625
[TRACE] ColorManagement max avg 417.7095, min 0.12436535, max 417.7095, brightness 0.5
[LOG] [AQ] drm: Modesetting DP-2 with [email protected]
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 5c85274f8e20
[TRACE] [AQ] Connector blob id 115: clock 592000, 2560x1440, vrefresh 144, name: 2560x1440
[ERR] [AQ] atomic drm: setting hdr min 622, max 209, avg 209, content 209, primaries 33887,15674 14160,32422 7422,3418 33887,15625

I tested the video simultaneously in Hyprland and i3, switching between them to compare on the same monitor (AG322QC4). With hyprshade disabled, there was a subtle but noticeable difference - the colors were more vivid on Hyprland. To verify, I relaunched it from the main branch and performed the same comparison. This time, I observed no difference compared to i3, confirming that the changes made to aquamarine and hyprland were successful. Well done @UjinT34 !
Enabling experimental:hdr caused color distortion, as expected, so I kept it disabled.
GPU: GTX1080 with nvidia-dkms 565.77-2.

Regarding the last log entry in the sample, was AQ_LOG_ERROR used for debugging purposes? Relevant code part

@UjinT34 UjinT34 changed the title WIP Support color management protocols Support color management protocols Dec 18, 2024
@UjinT34
Copy link
Contributor Author

UjinT34 commented Dec 18, 2024

Regarding the last log entry in the sample, was AQ_LOG_ERROR used for debugging purposes? Relevant code part

Fixed it

@hanatos
Copy link
Contributor

hanatos commented Dec 21, 2024

I guess some colorimetry equipment might be needed.

i have access to an (ex-) xRite i1 DisplayPro colorimeter. is there anything in particular you'd want me to test? displaycal offers profile verification using a firefox window. would ff be colour managed here? i think not.. otherwise i could verify.

@UjinT34
Copy link
Contributor Author

UjinT34 commented Jan 7, 2025

hyprwm/hyprland-wiki#932

@vaxerski
Copy link
Member

vaxerski commented Jan 7, 2025

we ball

@vaxerski vaxerski merged commit 830350a into hyprwm:main Jan 7, 2025
11 checks passed
@izmyname
Copy link
Contributor

izmyname commented Jan 7, 2025

That's impressive. AFAIK, only kwin supported HDR, until now

@iddm
Copy link
Contributor

iddm commented Jan 8, 2025

I am curious about this: do we need support from Firefox/Chromium/etc to enable us to view YouTube (or any other streaming content) in HDR?

@knoxode
Copy link

knoxode commented Jan 8, 2025

I am curious about this: do we need support from Firefox/Chromium/etc to enable us to view YouTube (or any other streaming content) in HDR?

As far as I understand the wayland client needs to support HDR, so in the case of linux, yes Firefox needs to support the underlying protocol, before you can "just use" HDR on youtube in Firefox, atleast (I don't use chrome).

@ninetailedtori
Copy link
Contributor

So dynamic HDR should be supported by Hyprland as of this merge? Or is this just the color management protocols that got fixed up? Static HDR is still crispy fried oversaturation for me, just tryna get on the same page with regards to this PR as I'm a little new here to hyprland :)

@knoxode
Copy link

knoxode commented Jan 9, 2025

So dynamic HDR should be supported by Hyprland as of this merge? Or is this just the color management protocols that got fixed up? Static HDR is still crispy fried oversaturation for me, just tryna get on the same page with regards to this PR as I'm a little new here to hyprland :)

I'm not really a 'developer' so take my words with a grain of salt but to reiterate - if the client supports it then it will work.

Just based on the naming scheme alone, I would hazard a guess that this supports the CM protocols, nothing more, nothing less.

Further implementations beyond CM protocol support surely require more code to be written - either in hyprland, or in the wayland client.

@UjinT34
Copy link
Contributor Author

UjinT34 commented Jan 9, 2025

It supports CM protocols and passes hdr metadata as is. Should be enough for HDR10 which is static. Afaik HDR10+ (dynamic) isn't supported by the linux kernel.
If by dynamic you mean auto switch on and off than it will work for hdr mode unless you force in on with experimental:hdr. experimental:wide_color_gamut doesn't have any automation.

@caffeine01
Copy link

caffeine01 commented Jan 9, 2025

YO i was literally just thinking "i wonder if there is any progress on hyprland hdr", i see that this has been merged, click, DAMN

@caffeine01
Copy link

yo wtf why these colours look goofy asf

@caffeine01
Copy link

caffeine01 commented Jan 9, 2025

everything is incredibly oversaturated with experimental:hdr set to true, ebdbb2 looks almost neon highlighter yellow, tbf probably a monitor issue as its a fucking LG Ultragear scam hdr monitor
EDIT:
nvm, some of it was down to wlsunset, but still the contrast is fucked, the outside of text is like pixelated and shit

@ninetailedtori
Copy link
Contributor

It supports CM protocols and passes hdr metadata as is. Should be enough for HDR10 which is static. Afaik HDR10+ (dynamic) isn't supported by the linux kernel.

If by dynamic you mean auto switch on and off than it will work for hdr mode unless you force in on with experimental:hdr. experimental:wide_color_gamut doesn't have any automation.

Forcing it on is still quite crispy, it seems. In terms of passing metadata onto other applications, I'll test with some games and video apps in a bit 🫡

@UjinT34
Copy link
Contributor Author

UjinT34 commented Jan 10, 2025

Forcing it on is still quite crispy, it seems. In terms of passing metadata onto other applications, I'll test with some games and video apps in a bit 🫡

There is no tone mapping if you force it on. It's for testing for now. Will be usable with some CM.

@ninetailedtori
Copy link
Contributor

The wiki settings for steam, ENABLE_HDR_WSI=1 DXVK_HDR=1 DISPLAY= %command%, using steam and I'm fairly sure wayland-enabled steam, just does not work. I'll try another launcher, like direct wine, and see.

@ninetailedtori
Copy link
Contributor

ninetailedtori commented Jan 10, 2025

Testing with Shadow of the Tomb Raider and Wine 9.22: it may be an issue with NVIDIA cards, but I lose several things: being able to use >60fps, as well as DLSS entirely, in the initial settings menu. Upon activating HDR then attempting to launch, the entire game crashes.

@caffeine01
Copy link

Forcing it on is still quite crispy, it seems. In terms of passing metadata onto other applications, I'll test with some games and video apps in a bit 🫡

There is no tone mapping if you force it on. It's for testing for now. Will be usable with some CM.

how big of a task is this because i might want to contribute

@iddm
Copy link
Contributor

iddm commented Jan 10, 2025

I am also a bit out of the scope of the knowledge required here in terms of how it is related to the desktop, but. Will or should the desktop (the windows) be rendered also in the HDR mode (in other words, can/should we be able to enable the HDR mode for the desktop itself)? Does it even make sense? It is done in windows, so I don't know what we should have in Linux. Another thing, as a positive answer to the first question, is we should somehow set the luminosity limits for the UI of the desktop elements rendered then?

@caffeine01
Copy link

caffeine01 commented Jan 10, 2025

I am also a bit out of the scope of the knowledge required here in terms of how it is related to the desktop, but. Will or should the desktop (the windows) be rendered also in the HDR mode (in other words, can/should we be able to enable the HDR mode for the desktop itself)? Does it even make sense? It is done in windows, so I don't know what we should have in Linux. Another thing, as a positive answer to the first question, is we should somehow set the luminosity limits for the UI of the desktop elements rendered then?

This is what they (and i) was talking about earlier, the option experimental:hdr forces HDR to be applied to the entire compositor (hyprland, all windows, etc).
At the moment though, the HDR implementation is still very fresh and needs a lot of work because there is no proper colour management for SDR->HDR, so setting experimental:hdr at the moment will make everything look very crispy (don't do it it hurts to look at).
If you enable experimental:xx_color_management_v4 and experimental:wide_color_gamut (although experimental:wide_color_gamut may not be needed), then hyprland will be able to properly handle and pass HDR metadata to the display which is enough for HDR10 to work in say HDR encoded videos from MPV or msedge.
Currently, though, this implementation is quite lacking compared to say Windows or KDE's implementation, but it's a start and it's looking quite hopeful! Eventually you will be able to just 'enable HDR' in hyprland and have everything work 'normally'.
(this is what i have gathered from paying attention to the comments in this pull)

@caffeine01
Copy link

Also, this might be worth following to fellow firefox users browsing this thread

https://phabricator.services.mozilla.com/D233252

@ninetailedtori
Copy link
Contributor

Yeah, I'd love to work on some of the tone mapping for base SDR content, I'm not too sure how much work it'll be. Still unsure if I can get the HDR content working in any game right now though, having a ton of issues.

@JoMaZu787
Copy link

JoMaZu787 commented Jan 12, 2025

Hey, I just tried this with the xx_color_management_v4 config variable, but the colors seem undersaturated unless I do hdr = true, which makes them oversaturated as expected

EDIT: the colors are actually just a lot brighter, but still undersaturated.

@zakk4223
Copy link
Contributor

On KDE, If I launch Path of Exile 2 with gamescope --hdr-enabled -f -- %command% I can select HDR in game. (as long as HDR is enabled in KDE display settings).

On Hyprland, even with xx_color_management variable enabled I cannot select HDR in-game. I also tried with wide_gamut and hdr enabled with no change. Is there some additional magic KDE is doing here?

@UjinT34
Copy link
Contributor Author

UjinT34 commented Jan 13, 2025

KDE has a builtin layer similar to https://github.com/Zamundaaa/VK_hdr_layer. On HL it should be installed manually.
Gamescope should have its own builtin layer. Maybe DXVK_HDR=1 is missing. With correct env vars hdr setting should be available even without any protocol or hw support.

@zakk4223
Copy link
Contributor

Gamescope injects DXVK_HDR automatically:

https://github.com/ValveSoftware/gamescope/blob/f873ec7868fe84d2850e91148bcbd6d6b19a7443/src/Backends/WaylandBackend.cpp#L1513

Inspecting the process on Kwin I can see DXVK_HDR=1 is set. On Hyprland it is not. (forcing it doesn't help either).

I'll keep messing with my hyprland config, maybe there's some settings I have breaking it

@BeauTaapken
Copy link

BeauTaapken commented Jan 13, 2025

i just gave it a try. A few things i've notices:

1: if i don't turn on experimental:wide_color_gamut, my hdr content looks really washed out. I need to turn it on (meaning i'm also forced into YCbCr)
2: At first, enabling wide_color_gamut, made my hdr screen run at 60Hz, instead of the 165Hz it's set to
3: When i turned off hdr for my only hdr capable screen, hyprland crashes
4: when enabling wide_color_gamut, one of my screens doesn't update anymore (a rotated one, maybe it's something to do with that?). I fixed it by turning the monitor off and on again

after enabling wide_color_gamut, restarting my system has fixed the issue of my screen only running at 60hz and the issue where the YCbCr colors looked weird.

edit:
Small update, just noticed that enabling wide_color_gamut results in my framerate dropping from 165fps to less then 1 in a matter of minutes, so won't be using hdr for now

@caffeine01
Copy link

caffeine01 commented Jan 14, 2025

i just gave it a try. A few things i've notices:

1: if i don't turn on experimental:wide_color_gamut, my hdr content looks really washed out. I need to turn it on (meaning i'm also forced into YCbCr) 2: At first, enabling wide_color_gamut, made my hdr screen run at 60Hz, instead of the 165Hz it's set to 3: When i turned off hdr for my only hdr capable screen, hyprland crashes 4: when enabling wide_color_gamut, one of my screens doesn't update anymore (a rotated one, maybe it's something to do with that?). I fixed it by turning the monitor off and on again

after enabling wide_color_gamut, restarting my system has fixed the issue of my screen only running at 60hz and the issue where the YCbCr colors looked weird.

maybe related? hyprwm/aquamarine#127

edit: Small update, just noticed that enabling wide_color_gamut results in my framerate dropping from 165fps to less then 1 in a matter of minutes, so won't be using hdr for now

I'm not experiencing framerate drops with with experimental:wide_color_gamut, prob a good idea to provide further info like a hyprland debug log for example.

@UjinT34
Copy link
Contributor Author

UjinT34 commented Jan 14, 2025

#9064 if someone is willing to jump into this rabbit hole

@ninetailedtori
Copy link
Contributor

I can't tell the frame rate drops yet, I haven't actually managed to get anything to run with HDR yet natively. I'm going to test with media players instead of games now though. And yea, I'll probably hop on the colour translation protocol coding 🫡

@mven
Copy link

mven commented Jan 16, 2025

I've been able to test a few things using an RTX 3090 plugged into an HDR monitor.

My system's graphics info
➜ inxi --graphics
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3090] driver: nvidia v: 565.77
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael driver: amdgpu
    v: kernel
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: Hyprland v: 0.46.0-115-ga6b26371 driver: X:
    loaded: modesetting,nvidia dri: radeonsi gpu: nvidia,nvidia-nvswitch
    resolution: 3440x1440~175Hz
  API: EGL v: 1.5 drivers: nvidia
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 renderer: NVIDIA GeForce
    RTX 3090/PCIe/SSE2
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info,wlr-randr x11: xdpyinfo, xprop, xrandr
	
Here are a few observations:

experimental variables require hard reload

Changing the experimental variables require an exit and relaunch of Hyprland for it to "take hold". Simply changing the variables to true changes my monitor status to show that it's in HDR mode, but vulkaninfo doesn't validate this.

➜ ENABLE_HDR_WSI=1 vulkaninfo | grep -i hdr
[HDR Layer] wayland compositor is lacking support for color management protocols..

After hard reloading (exiting Hyprland/loading back in), I can run vulkaninfo again and it properly shows support and my monitor shows HDR is on.

➜ ENABLE_HDR_WSI=1 vulkaninfo | grep -i hdr
[HDR Layer] Created HDR surface
[HDR Layer] Enabling format: 64 colorspace: 1000104008
[HDR Layer] Enabling format: 58 colorspace: 1000104008
[HDR Layer] Enabling format: 97 colorspace: 1000104002
[HDR Layer] Enabling format: 97 colorspace: 1000104005
VK_LAYER_hdr_wsi (WSI HDR Layer (x86_64)) Vulkan version 1.3.221, layer version 1:
			VK_EXT_hdr_metadata : extension revision 3
			colorSpace = COLOR_SPACE_HDR10_ST2084_EXT
			colorSpace = COLOR_SPACE_HDR10_ST2084_EXT
	VK_EXT_hdr_metadata                           : extension revision 3
	textureCompressionASTC_HDR                         = false

Note: hyprctl reload does not work to resolve this issue. I have to exit and load back in to be set.

HDR video test

After configuration was set (exit/relaunch Hyprland), I attempted to play a video with an HDR profile with mpv, I got a similar printout to what vulkaninfo gave me:

➜ ENABLE_HDR_WSI=1 mpv --vo=gpu-next --target-colorspace-hint --gpu-api=vulkan --gpu-context=waylandvk hdr-video.mp4
● Video  --vid=1  (hevc 3440x1440 60.0019 fps) [default]
● Audio  --aid=1  (aac 2ch 48000 Hz 192 kbps) [default]
File tags:
 Date: 2024
[HDR Layer] Created HDR surface
[HDR Layer] Enabling format: 64 colorspace: 1000104008
[HDR Layer] Enabling format: 58 colorspace: 1000104008
[HDR Layer] Enabling format: 97 colorspace: 1000104002
[HDR Layer] Enabling format: 97 colorspace: 1000104005
[HDR Layer] Enabling format: 64 colorspace: 1000104008
[HDR Layer] Enabling format: 58 colorspace: 1000104008
[HDR Layer] Enabling format: 97 colorspace: 1000104002
[HDR Layer] Enabling format: 97 colorspace: 1000104005
AO: [pipewire] 48000Hz stereo 2ch floatp
VO: [gpu-next] 3440x1440 yuv420p10
[HDR Layer] Creating swapchain for id: 7 - format: VK_FORMAT_A2R10G10B10_UNORM_PACK32 - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
[HDR Layer] Creating swapchain for id: 7 - format: VK_FORMAT_A2B10G10R10_UNORM_PACK32 - colorspace: VK_COLOR_SPACE_HDR10_ST2084_EXT
[HDR Layer] VkHdrMetadataEXT: mastering luminance min 0.000001 nits, max 10000.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxContentLightLevel 0.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxFrameAverageLightLevel 0.000000 nits
[HDR Layer] Creating swapchain for id: 7 - format: VK_FORMAT_A2B10G10R10_UNORM_PACK32 - colorspace: VK_COLOR_SPACE_HDR10_ST2084_EXT
[HDR Layer] VkHdrMetadataEXT: mastering luminance min 0.000001 nits, max 10000.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxContentLightLevel 0.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxFrameAverageLightLevel 0.000000 nits
AV: 00:00:02 / 00:00:19 (15%) A-V:  0.000[HDR Layer] Creating swapchain for id: 7 - format: VK_FORMAT_A2B10G10R10_UNORM_PACK32 - colorspace: VK_COLOR_SPACE_HDR10_ST2084_EXT
[HDR Layer] VkHdrMetadataEXT: mastering luminance min 0.000001 nits, max 10000.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxContentLightLevel 0.000000 nits
[HDR Layer] VkHdrMetadataEXT: maxFrameAverageLightLevel 0.000000 nits
...

The resulting video looks amazing and to be playing in HDR color space, despite the windows around it looking like they have a reduced color palette and oversaturation as observed by others.

HDR game test

I tried out a few games through Steam (gamescope) and umu-launcher, but bear in mind that I'm not too experienced or familiar with all the utilities/launchers/layers. These commands are what I've come across through my journey to get HDR working on games I want to play.

Using Gamescope / Steam Big Picture Mode

I've had success running Steam in fullscreen/big picture mode nested in Gamescope. Steam's UI has some color issues, but I've tested Cyberpunk 2077, Witcher 3, and Resident Evil. All of them allow me to turn on HDR in their respective display settings and the graphics look like HDR. Here's the command I used to test this out.

ENABLE_HDR_WSI=1 gamescope --fullscreen -w 3440 -h 1440 --hdr-enabled --hdr-debug-force-output --hdr-sdr-content-nits 600 --steam -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 steam -bigpicture

Source of command: https://zamundaaa.github.io/wayland/2023/12/18/update-on-hdr-and-colormanagement-in-plasma.html

Using Steam launch options for individual games

The following command worked to enable HDR in Resident Evil 4. This is the only game I tested, but I assume this'll work on other games with HDR as an option. I have the --mangoapp flag present, so you might need to install mangohud or just remove the flag if you don't want to do that.

ENABLE_HDR_WSI=1 gamescope --fullscreen -w 3440 -h 1440 --hdr-enabled --hdr-debug-force-output --hdr-sdr-content-nits 600 --mangoapp -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 %command%

FPS issue with gamescope

I noticed that Gamescope was limiting my FPS to around 60, but found a few threads that pointed to VSync being the culprit. I turned that off in the game I was testing and my frames increased past 60.

umu-launcher

Instead of using Steam and Gamescope, I was also able to get HDR working with Witcher 3 and Cyberpunk 2077 with the command below. I used umu-launcher in combination with protonge. and leveraged asdf to install protonge. The PROTONPATH is essentially where asdf installed proton lib. Their launchers were definitely suffering from color issues, but when the games loaded and HDR settings turned on, everything in-game looked great.

ENABLE_HDR_WSI=1 DXVK_HDR=1 WINEPREFIX=~/.wine GAMEID=0 PROTONPATH=~/.asdf/installs/protonge/GE-Proton9-22 umu-run The\ Witcher\ 3/REDprelauncher.exe

Note: In Cyberpunk 2077, I had to set HDR10 PQ in HDR option since the HDR10 scRGB option had way too much contrast. Informative post about the differences.

Issues in umu

I didn't experience any FPS issues using umu-launcher so I didn't need to disable anything. Though, there were some games that refused to load with umu-launcher like Resident Evil 4. It complained that Steam needed to be running. I'm not sure why I got that message since Steam was running at the time, but if I were to take a guess, it might be that I need to run Steam under the same Wine prefix. 🤷

Anyway, that's it for now, but I'm hoping to do more testing later. Hopefully this helps some folks out to try out HDR in videos/gaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.