Funny I tried to induce that and I couldn’t see it…maybe because I normally use rec2020 for my histogram profile…but I thought I changed it…
Thank you for the very helpful explanation. I will continue to have fun with it. I thought that the overall impact of popping above the 100% line was not bad at all, and that the primaries feature helps (speaking to the “smooth” preset mostly here) and seems to delay the onset of the color hard limiting visually even if it’s happening to some degree in reality. I’m happy to find what I’m seeing is intentional, and i just need to use it properly.
Even though the thread is a bit older, as a Debian user, the changes are quite recent. Therefore, I have two questions:
Even though this thread is a bit older, as a Debian user, the changes are quite recent. Therefore, I have two questions:
Will the “smooth”-preset eventually become the default? The reasoning here and in the manual gives the impression that this preset is actually preferable in all cases, which raises the question of when the default settings still make sense.
Isn’t that guaranteed if sRGB is defined during export? And wouldn’t it make sense to set the working profile to sRGB in the case of a pure sRGB workflow?
Hey there!
Will the “smooth”-preset eventually become the default? The reasoning here and in the manual gives the impression that this preset is actually preferable in all cases, which raises the question of when the default settings still make sense.
The initial implementation and the “smooth” preset was a bit like a “soft launch” for the interested people to try out. I think at this point it may be worthwhile to think about the defaults - perhaps this preset could even make a sensible default.
I’m keeping an eye on the AgX module development and the user preferences and feedback there. As this kind of modification of the primaries is going to be always a bit opinionated, one should aim for settings that fit the most people as a reasonable starting point.
I’m not promising anything yet, but maybe for the next release cycle it would make sense to figure out new defaults for sigmoid? I can at least try.
If you set sRGB as the export profile, the out-of-bounds values are just clipped to [0, 1] at output, which results in broken gradients. There is currently no “graceful” handling of those at the output. You might be interested in following this work by @kofa , aiming to tackle this issue.
As for sRGB as the working primaries, I have actually done this sometimes, but this works only in limited occasions - specifically when there are no high-purity triplets in the sensor captured raw data (think blue LEDs etc)
I also think smooth, or something similar, would make a great default.
Hi Sakari, (@flannelhead)
First - a heartfelt thank-you for all that you do for darktable. ![]()
Second - I agree that smooth would be a best default.
Third - I just edited over 1100 vacation photos using Sigmoid. I often found that blue rotation and red attenuation were not to my taste with the smooth preset. I often found myself rotating blue in the opposite direction (skies were too teal), and increasing red attenuation (red-orange oversaturated). So I doubt there is any universal “best case for everyone.”
And to @kofa, I very much look forward to the full release of AgX, I have been following your threads with great interest (and great respect as well).
Cheers from Phoenix