https://bugs.kde.org/show_bug.cgi?id=437429
M <manuel.snudl.zeid...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #17 from M <manuel.snudl.zeid...@gmail.com> ---
So I think I need to reopen this report. I'm trying the newest Nightly
e2a04dd823 on Windows and the same display issue is still present.
There are now more general issues with floating-point colors, I put that in a
new bug report since I don't know how much it relates to this report.
https://bugs.kde.org/show_bug.cgi?id=444439
Picking a color from an HDR palette also seems to be extra broken on 32-bit
float documents, if it uses a gamut other than sRGB-g10. Whether OCIO is
activated or not, the picked color is a tone-mapped version of the original
color value. When picking the painted colors from the canvas they never go
above 1.0, and it's immediately visible that they're not HDR with ACES or
Filmic active. This problem doesn't occur with 16-bit float.
Strangely, the Specific Color Selector also displays the same wrong tone-mapped
values after selecting a color patch from the palette if it's set to 32-bit
float and a different gamut from sRGB-g10, but not for 16-bit.
Lastly, very minor UI complaint: The new version info text on the bottom of the
LUT docker is quite long, at least on Windows, and increases its minimum width.
So if the LUT docker is in a column with other dockers I can't shrink that as
much as I previously could. That's all.
--
You are receiving this mail because:
You are watching all bug changes.
