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.
Scenario A:
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.
Scenario B:
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).
It seems to me the state tracking is not working properly, if the monitors cm is not default / srgb.
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.
Scenario A:
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.
Scenario B:
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).
It seems to me the state tracking is not working properly, if the monitors cm is not default / srgb.