Hi, I don't know if this is how it's supposed to behave, but I suspect it is not: switching 'preserve chroma' to 'RGB power norm' drastically altered the curve. Switching back to any of the other settings (including to 'no') restored the original curve; selecting 'RGB power norm' altered it again. After a few switches, darktable froze with 100% CPU. No error in the console. After killing and restarting, I'm unable to reproduce this.
Self-built darktable a88be9282b0 using build.sh, NVidia OpenCL on a GTX 650, Ubuntu 19.04. Wiped library.db and data.db. Files are here: https://drive.google.com/drive/folders/1qmx5JkL11L9ZAwEykHXcfaYPIkF8FTFc?usp=sharing 1. I imported and opened a raw file -> 2019-06-02_12-24-37_DSC_0002.NEF 2. Turned on filmic RGB. -> filmicRGB-defaults.png 3. Pressed auto tune levels -> filmicRGB-auto_tune_levels.png 4. Switched to the 'look' tab, and switched 'preserve chroma' to 'RGB power norm'. The curve got distorted. -> filmicRGB-auto_tune_RGB-power-norm.png Thanks, Kofa ps. Thanks for quickly fixing the somewhat misleading names of the presets; I promise I'll continue to read the fine manual once it is available; until then, I read your Pixls.us posts and watch your Youtube videos as they become available. ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
