On 10.4.20 11:27, Harold le Clément wrote:
- Is this a real issue or is this a bad usage of darktable? I.e. shall we never have RGB values higher that 1.0 in the pipe?
As a user I would expect to keep the dynamic range throughout the pipe for as long as possible. If a module clips it would actually help if this was indicated in the UI. Maybe with a little warning sign icon or the like, on the module.
- In the case this should ideally be fixed, I see three possibilities, are there others? 1. Use another hue/saturation/lightness estimator: HSV (although value is really different than lightness) or LCh (probably a lot more computationally intensive), ...
Yes, I would second looking into the cylindrical models, LCh/HCL/CIELab/CIELuv, as better alternatives (https://arxiv.org/abs/1903.06490).
Just my two c. As I said, I'm just a user of DT. .mm ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
