On dimanche 13 décembre 2020 13:24:34 CET cimatosa wrote: > Dear DT community, > > > I have been using DT for quite a while now and I'm very happy with rich > features and resulting images. > > However, since my workflow includes preselecting my RAW files using > Geeqie I'm always a bit frustrated when I load my images into DT after > having seen the "rather well pleasing" preview of the RAW data in > Geeqie. I takes quite some effort to get close to the Geeqie results > using DT, so I have not managed yet to create a suitable style that > would work a default / starting point for further processing. > > So here is my question, does anyone know or has experiences on how to > convince DT to give me the same results as Geeqie?
TL;DR: not possible... To elaborate a bit: Geeqie is presented as an image viewer, with some very basic "editing" capabilities, like rotating the image over a multiple of 90°. That means that it doesn't display raw data, but uses the embedded, camera- generated, jpeg included in the raw file for preview purposes (which is usually much smaller than the raw file). So what you are looking at is not "Geeqie results" but "camera results". If you want that, just shoot jpeg. There are a lot of photographers (including professionals) who do just that, especially when they have to deal with a lot of shots and a short deadline. Now, in dt, the basecurve is supposed to mimic the in-camera raw processing. This is never perfect (if only because it's too simple), and won't take into account scene modes or personal settings on the camera that influence its jpg generation. But it's about the closest you can hope to get to the in-camera rendering without a lot of work on your part. And in that case, why stick to the camera rendering? ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
