color zones (set to zero but turned on) contrast equalizer (with Sharpen preset, “mix” set to 50%, saved as “Sharpen 50%” profile. It’s sometimes recommended to have two instances of denoise(profiled) (one for color, one for light) to achieve the same, but denoise(n-l-m) is faster and more accurate than two instances of profiled denoise Althrough this denoise is computationally demanding, for me it’s best way to save some “grainy” sharpness without “color sand”. denoise(non-local-means) Luma set to 10%, chroma set to 100%. basic adjustments (with exposure set to +1ev, but it’s my specific, connected with ETTR shooting) input color profile (just leave it, as it’s necessary and default) haze removal (set to zero but turned on) tone equalizer (set to zero but turned on) crop and rotate (set to centered 3:2 as I shoot with 4:3 sensor but having 3:2 ratio in mind) chromatic aberrations (in 99% done with system lenses, no need to adjust in lens corerction module) raw black/white point (default and necessary, just leave untouched for 99% cases) But you can “develop” your own set that fits into two groups - default and favourite.Īfter reading mentioned Aurelien’s article, I have “developed” my own set of default loaded modules: There is one biggest disadvantage of DT’s UI - modules are hard coded into groups in “not too intuitive” way - intuitive rather for coder than photographer. I wish people wouldn’t be so scared and dare to experiment with modules much more. The modular structure of darktable is the ideal playground for this. Just to reassure you: Since you don’t mix dangerous chemicals, but only harmless modules, you don’t have to worry that when you make a mistake, the whole neighborhood needs to be evacuated.Īnd B&W Processing with darktable - module choice & ordering - #9 by s7habo For some reason, I sometimes find it works better before filmic, and sometimes really not, while it always works ok after filmic (where it is by default in the 3.0 pipe).Ĭheck out youtube channel and take his advice: Local contrast is a local operation that rely on an hard-set definition of grey and white. These should better go after filmic, where the pipe is dislay-referred. These modules rely on a fixed assumption about the values of grey and white. have a display-referred GUI (in the 0-100% range). As such, they should go before filmic (where they are by default in the 3.0 pipe order). Sharpening, contrast equalizer, high-pass and low-pass filters work in Lab but perform local operations, so they don’t rely on any definition of grey or white. All the Lab modules can still be used in conjunction with filmic, even though they are not optimal. Remember filmic is your conversion from scene pipeline to display pipeline. (from ) What if I like to use the display-referred Lab tools ? Read the filmic FAQ ( darktable's filmic FAQ). If a given module does not work (pushed too far, or it just can’t do what you tried to use it for), you’ll see it clearly. The darktable developers have done their best to put modules where they usually work best, but you can rearrange them. Don’t worry about what’s LAB and what’s not.
0 Comments
Leave a Reply. |