What is problematic is pedagogy, because each image is different, and the tastes of each are different. One will prefer a natural image - one that the photographer has seen - another prefer an artificial image with reinforced chroma, accented contrasts, visible perspectives.
For all agorithms that are not “natural” (Retinex, Tone-mapping, and some parts of Wavelet), this problem will arise.
I will add to Rawpedia, at the end of the current sections Retinex, a summary of recommendations and an “average” frame.
Jdc
yeah! really really really well done! u have to think about doing this for everything,
is clear short and detailed exactly what needed…
from that example start to dig into this tool and re-read the section up of the example understanding the technical explanation is much more easy.
i’m playing a bit following the steps, then i would try to move them to my photos, as fast as i get a decent result for me i would post it, (too many things too few time…sigh).
Thanks to all, Afre HIRAM shreedhar Morgan_Hardwood james agriggio and off course to you Jdc, for the patience the kindness and this come out a really nice thread.
This is my try at the image: Uploading…
I did a little of everything, noise reduction, white balance, vibrance, retinex, contrast, lightness, dark level, exposition compensation, saturation, light compression, shadow compression. _DSC4138.jpg.out.pp3 (9.8 KB)
I added the color component to “Retinex at the beginning of the process” (with the same principle as in Retinex in Wavelet and with a slider “chroma”).
For this you must use the branch “newwaveletgtk3”.
The “Chroma” slider acts as a percentage of “strength” (luminance component).
Attention, the processing times are doubled (if the chroma slider is> 0) and the memory requirements are increased.
u have to think about doing this for everything,