The deltaE “upstream” now allows to maintain the “settings” (contrast, saturation, …) on the selected area. Fortunately it is kept. That’s the goal.
That the final colors / contrasts / etc. are changed by the downstream treatments… it’s obvious, but it’s that the user wants it…For example black and white…But now BW does not suppress deltaE…
But, the settings made “upstream” remain… This is the goal, the purpose of having moved this treatment.
For me, everything works properly
Okay, I’m confused. Does this mean that all of my usual Exposure, Highlights and Shadows, Tone Curve and Lab Adjustments are now supposed to be done after LA are completed?
Yes, but this was already the case for the “Lab adjustments”.
But No, you can used “exposure, Highlight, shadows…”, etc…independently of LA…
When you change these process, no incidence on LA…
it is the same for any process upstream of "exposure, highlight…) (demosaicing, white balance, etc.). You are not “obliged” to change these processes to retouch “exposure”.
But with the Rawtherapee pipeline, it’s a choice, either before RGB process or after…As there were a lot of requests for before, which I think is globally preferable
@stuntflyer I think everyone is at cross-purposes here. From a user point of view you can make local and global adjustments when you like as per your normal workflow. The only thing that changes is where the Local Adjustments occur internally in the processing pipeline.
HTH
That’s the point. You have to know at which point in the pipeline local adjustments are applied, because that can have a massive impact on what you think your local adjustment spot (which is a central concept of local adjustments in RT) picks up…
If I remember correctly @Andy_Astbury1 did a couple of Local Adjustment video’s a few months back. Maybe he’s able/wiling to have a look at this and make one of his nice video’s, he did ask the RawTherapee community for suggestions he could do.
Now, process after “LA” are neutralize (provisory) when the user uses one of the functions “Preview deltaE”. Up to now only BW was concerned by this behavior.
So we can see the impact of LA without the action of downstream processes
There are already masks with various possibilities, including the 3 curves L(L), C(C), LC(H), taking into account deltaE, structure and blur mask, Laplacian, etc.
You can also use mask with “Recovery based on luminance”, etc.
But for brush, and also Béziers Curves, polygon, it’s mostly a GUI problem and I don’t know how to do it…If someone can try to deal with this problem it would be nice…
Can someone please tell me what this curve abbreviation stands for, LC(H)? Honestly, I find that certain areas of the program need a more practical and less scientific explanation of its features.
They are like function descriptions. When you have y = f(x) it means the value of y is given by some function that takes x as an input. Our notation is a little different, but you get the gist I hope: for L(L) you adjust lightness based on an input lightness, so an L vs. L curve. For C(C) it is a chromaticity vs. chromaticity curve. For LC(H) it takes two inputs, lightness and chromaticity and you can adjust the hue.
Does that help?
It should also be obvious what the curves do when you try them out.
@stuntflyer
The explanation of @Thanatomanic is excellent. In other words, when the hue (H) of the image changes, the LC(H) curve allows to vary the luminance “L” and chromaticity “C”
In summary you have 3 curves for a mask :
the first, L(L) allows to vary the luminance of the mask “L” according to the luminance of the image “L”
the second, C( C) allows to vary the chromaticity “C” of the mask according to the chromaticity “C” of the image
the third, LC(H) allows the luminance “L” and chromaticity “C” of the mask to vary according to the image hue “H”