On Thu, 5 Nov 2020 at 09:49, Remco Viëtor <[email protected]> wrote: <snip> > Raw development is good if you do *not* like the look your camera produces, or > when you have images the camera software can't handle (images with high > dynamic range come to mind, or images with a lot of "led blue", like some > theatre settings...). But raw development has to be learned...
Yes, indeed: you should work in the way that gets you the results you want so as to achieve your purposes in taking the photographs. And if you can achieve those purposes successfully 'in camera' and with the camera's jpegs, that's great. (This is quite common among wedding photographers, who need to keep the costly overhead of post-processing time to a minimum.) But, as you say, if you can't get, or don't like, the results from your camera even after a bit of minimal processing, and the picture matters enough, then edit the RAW file. (Of course, if you enjoy processing RAWs simply because you enjoy post-processing, then these considerations don't apply.) I always shoot RAW + JPG, to give myself the flexibility to choose if necessary. But, for my purposes, I rarely need to edit RAW files: a bit of tweaking of the jpegs in dt is enough when necessary. And dt is very useful for this, as long as you remember to place Input Color Profile early in the pipe, as Aurélian Pierre does with the jpeg he's editing in this video at 14:22: https://www.youtube.com/watch?v=kzACn3l49HM (This is easy to do now we can change the module order in dt, and apply that module order to a set of pictures using a module order preset.) So, yes, do what works for you. ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
