Config handling of monitor cm,auto and cm,wide bugged in combination with render:cm_auto_hdr #12958
Unanswered
ruabmbua
asked this question in
Bugs - Config
Replies: 1 comment
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I recently noticed, that in combination with bitdepth,10 I can also set cm,wide or cm,auto to actually make use of wide colors for my monitors.
I noticed, when changing the cm value from the default srgb that the automatic hdr enable for full-screen applications is now broken.
When cm is set to the default of srgb, hyprland automatically seamlessly activates hdr when a app goes full-screen, and after it leaves full-screen its deactivated again.
When cm is not set to default (I only checked auto and wide), hdr is automatically enabled on the monitor if I full-screen my app. But after the app exits full-screen hdr is not reset on the monitor. In addition colors on the monitor for normal windows look really wrong (of course, I have no proper sdr->hdr mapping configured).
Could it be that the cm_auto_hdr mechanisms exit condition is broken if the monitors cm is not the default?
Thanks for any help / input.
All reactions