>>4299875Agree.
The workflow for processing a RAW should be as follows.
Disable transgender shit like "RAW Denoise", "RAW Sharpen", "Sharpen", "Local Contrast", "___ Curve", "Clarity", "Dehaze", "Saturation", "Vibrance", or anything else that's standard kit for an Adobe troon.
If your photo doesn't look good processed in Darktable with nothing more than the following modules and settings used, your photo was boring.
>input color profileStandard/embedded color matrix
>exposureAdjust EV value to get image brightness to desired level, ETTR in post, basically.
>orientationRotate 90/180/270
>rotate and perspectiveIf you fucked up and have an uneven horizon, you can fix it with this but it isn't lossless. Don't rotate unless necessary.
>lens correctionIf your lens has offensive levels of distortion or problems in other areas that detract from the visual appeal of the image, enable these. These are lossy but worth it for big flaws.
>demosaicfor B&W, use passthrough
for color, PPG or AMaZE work but demosaicing is a cope so don't pay too much attention. If Moire is showing up, MOIRE IS CREATED BY DEMOSAICING, so switch the options until it is minimized (depends on scene, no one size fits all here)
>highlight reconstructionThis actually isn't a copium editfag thing like some might think, the raw photosite exposure values hold information regarding highlight details that get clipped as part of amplifying color channels as part of white balance. For this, "Reconstruct in lch" or "clip highlights" is the most accurate non-post-process fag option, but sometimes "inpaint opposed" can look decent
>white balanceThis one is self explanatory.
If you have ANYTHING else enabled you're post-processing your shit, and entering Rockwell territory.
>"but without curve edits m-m-muh M-MUH IMAGE LOOKS FLAT!!"That's a (You) problem, not all scenes have contrasty highlights vs shadows, change your lighting (adjust scene or wait for sun/weather/cloud coverage to change) to fix this.
