https://bugs.kde.org/show_bug.cgi?id=499934
--- Comment #20 from mith3...@gmail.com --- (In reply to Zamundaaa from comments #7, #14, #18) > HDR screens are terrible and their self-reported values can't be trusted. > The vast majority of TVs can't even go above 200 nits, they can't "follow the > EOTF" without making the image terrible. How about we don't make assumptions about user hardware? If self-reported values can't be trusted, why does KWin perform tonemapping based on the max luminance reported by the monitor's EDID? Heck, why even support HDR at all if this is the case? > The fact that you have to configure brightness settings per game in 2025 is > ridiculous! > Adding a window action or something to change the brightness of an individual > window could be reasonable, so you could increase or decrease the brightness > of a game or movie without affecting the rest. Is per-application brightness control ridiculous or reasonable? Please clarify. > All content, HDR or not, will be adjusted to match, and there's nothing more > to it than that. That's the issue. Comments on this thread and others clearly and consistently indicate that we do not want this behavior. You're correct in that a non-reference display in a non-reference viewing environment should be adjusted accordingly. Since we can't expect every display to have an ambient light sensor and do this automatically, it's fair to give users the option to make this adjustment according to preference. That said, I do not believe it is at all reasonable to expect that users will have the same preference for both SDR and HDR content. If the only solution you're willing to consider is adjusting this setting per-window via rule, then fine, I can live with that. But this needs to the remedied. -- You are receiving this mail because: You are watching all bug changes.
