https://bugs.kde.org/show_bug.cgi?id=508780

--- Comment #2 from Real Name Here <[email protected]> ---
(In reply to David Edmundson from comment #1)
> Mediumly trivial.
> 
> Out of curiosity, what's your use case for changing at runtime?

I switch to HDR for the few videos and games which support it. Otherwise, I use
SDR for accurate colours that aren't oversaturated, unlocks more monitor
options, and allows use of an ICC profile. Kscreen-docotr's "Wide Color Gamut"
setting only seems to have any effect in SDR as well. 

Disabled settings seems to be a fairly common issue with HDR monitors for PCs.
My display disables gamma, colour temperature, contrast, brightness, and etc.
when switched to HDR mode. Here are some examples of three large brands who
configured their firmware to lock display settings while HDR is enabled: 

LG
https://www.reddit.com/r/Monitors/comments/1ij3sxf/i_just_bought_this_monitor_but_these_options_are/mbaxnf1/

ASUS
https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-settings-locked-in-hdr-mode-help/td-p/1003728

Acer
https://community.acer.com/en/discussion/646047/acer-predator-xb323u-gxbmiiphzx-32-settings-locked-in-srgb-and-hdr-plus-heat-in-hdr

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to