Testing new Local Lab:
RawTherapee_newlocallab_5.3-257-g4b2563af_WinVista_64.zip
From:
https://drive.google.com/drive/folders/0B2q9OrgyDEfPS2FpdDAtMVI1RG8
and it is running fine here! 
I just read a little of the translation (thanks @sguyader 
) and this sentence made me think:
…each RT-spot can be viewed as an object with a number of fields (about 70 as of today), made of sliders, curves, control points, etc…;
So are we going in a direction where in the end everything except globally working tools like cropping, distortion correction…would be part of the RT-spots??
Just thinking out loud.
1 Like
Clearly no!
1 Like
I did my best in the translation to stay as close as possible to Jacques original words. This the case for the above-mentioned sentence, but don’t feel qualified to reword it (I don’t understand all the technical background). So, if parts of the documentation can be made clearer, feel free to make suggestions.
To confirm what Ingo says, no.
On the other hand, if it is necessary, and if there is a consensus, we can add some functions to existing modules, for example in Denoise, but I think that there is almost everything needed. This is significantly more than what CNX2 offered before.
@jdc Jacques, it looks like there’s a limit to the RT-spot size (1500 each side). I think it can be too small in some cases. I don’t know if the size is set to be proportional to the image size, or if it’s constant: what if we use a 100 or 150 Mpixels file?
Another suggestion: when I set a spot in inverse mode to create some sort of vignetting, some artifacts can be visible (look at the edges of the tree in the 4th picture here.
Maybe a “scope” slider would be be useful also in inverse mode in such cases ?
Hello, is there a development for Linux?
Yours sincerely.
Hello Sébastien
For the first point, “limit to 1500 each side”, I think it is easy to increase this limit without too much problem…to verify by testing. I will increase this value from 50%, and become 2250.
For the second point, it’s almost nonsense to want to consider a reference outside the work area (at least with the current algorithm). I tried something with “Blur” and “symmetric” mode, but it’s only partially satisfying. I will examine again. 
I just push a change with:
a) I have increased the zone limit from 1500 to 2250. Check if there is no interference.
b) suppress a bug (leads to crash) when using “Exposure” and “Color and light” with hue values of saturation
c) some changes to the code to prepare others improvements.
1 Like
Testing new Local Lab:
RawTherapee_newlocallab_5.3-382-g8dd112aa_WinVista_64.zip
From:
https://drive.google.com/drive/folders/0B2q9OrgyDEfPS2FpdDAtMVI1RG8
and it is running fine here!
Testing new Local Lab:
RawTherapee_newlocallab_5.3-383-gd13b485e_WinVista_64.zip
From:
https://drive.google.com/drive/folders/0B2q9OrgyDEfPS2FpdDAtMVI1RG8
and it is running fine here!
Any RT Local Lab version with this bug fixed?
I was asked - 6 days ago - not to make any changes while waiting for the “merge” of the “procparams-cleanup” branch
@jdc Jacques, I think you can still merge with dev from time to time, that’s not a change in locallab per se…
Thank you @agriggio
I just
-
fixed some bugs in internal function iplocallab.cc
-
improve inverse mode in Color and Light as asked by Sébastien @sguyader
These 2 improvments have no incidences on procparams.cc , paramsedited.cc,… -
merge with dev
jacques
RawTherapee_newlocallab_5.3-399-g2a2a008a_WinVista_64.zip
uploaded at
https://drive.google.com/open?id=0B2q9OrgyDEfPS2FpdDAtMVI1RG8
2 Likes
I push a change, in “newlocallab”.
Now you have in “color and light” a slider “warm - cool”. Ii uses “Ciecam Cat02”
Jacques
3 Likes
Here’s a mac build… it can crash if the warm - cool tool runs into over exposed image areas, for example at the extreme setting towards the red-dotted end. Otherwise it’s an excellent local effect!
https://filebin.net/4qpy4ins1rt0pikr/RawTherapee_OSX_10.9_64_5.3-467-g766291f2.zip
Thank you for testing and for the build
What do you expect by crash? Is it a crash of RT (segmentation fault, etc.) ? Or is it the occurrence of artifacts? Can you give a link with the raw and so on. Thank you
If this is the second case, it is more than likely that under certain circumstances, the CIECAM algorithm generates artifacts, see on this subject the many examples on this forum and in the “issues”
They are mainly due to the gamut of Ciecam which is very small.
Have you tried to use and “excluding spot”, while changing “Scope value” (Excluding) ?
jacques