Aurelien is a really talented developer that has brought some great features to Darktable including Filmic, Tone Equalizer and I believe Color Calibration. I have been impressed with how he has continued to improve both Filmic and Tone Equalizer to make both of these modules more user friendly and easier to understand for non-color scientists. A couple of 'improvements (?)' I would like to see going forward with tone equalizer is to have the mask's histogram on display as I adjust the sliders in the masking tab. At the moment I jump back and forth between the advanced tab and the masking tab to spread the histogram as wide as practical. The other option would be to have the mask's histogram automatically spread across from left to right based upon the brightness zones.
I am a mere user and do not understand the implications of my suggestions for a developer and programmer. It may be too difficult, impossible, undesirable or detrimental to change tone equalizer as I have suggested. In the meantime I am just so grateful to Aurelien for developing these great modules. I have watched Aurelien's videos and I hope I do not misquote him here, but Aurelien seems to feel Tone Equalizer makes the shadow highlights module redundant. On this point I would disagree as the visual result from both of these modules is similar but different. I am even known to use a combination of both to exploit the synergy. On Thu, 18 Feb 2021 at 19:35, <[email protected]> wrote: > Hi, everybody, > > I had some difficulty to understand what the term "mask" means with > the ToneEQ module. Only after watching Aurelien's tutorial > (https://www.youtube.com/watch?v=kzACn3l49HM), in particular the part > starting at 20:13, I grasped the idea (which is actually not hard to > understand) but which does for me not match what a mask is. > For me, a mask is always something masking an effect. For simple pixel > ops like tone effects, for each pixel the output O is O=M*F(I)+(1-M)*I > (where '*' denotes an operation which ensures M*I+(1-M)*I=I). I is > the input value, F the function (e.g. a tone curve) and M is a mask > value. > However, the so-called mask in ToneEQ is part of the function F : > O=Msk*F(Map,I)+(1-Msk)*I where Msk is a usual mask and Map is what's > currently called mask in ToneEQ. Hence, for me, and I think others as > well, the usage of the term mask in the ToneEQ module is confusing. It > is rather a parameter map than a mask as it determines what's > happening to a value but not to which extent (which leads to the > effect that, in addition to the ToneEQ mask, one can apply real masks > to restrict the effect to parts of the image). Now, the term has been > introduced in the manual, but still I'd find it disturbing. Maybe one > could change this over time so to keep the meaning of mask clear, and > call it a parameter map? > > Uwe > still a DT beginner but slowly getting to it. > > > > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > [email protected] > > -- ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
