It is certainly not the embedded JPG. When I save the JPGs
simultaneously to the RAWs from the camera I see that the JPGs do differ
significantly from the Geeqie image. This is why I was asking, since I
expect that Geeqie does some basic processing of the RAW data, which I
would find very convenient as a starting point in DT.
Ok, I will try to figure out what Geeqie is doing behind the scenes.
On 13.12.20 14:17, Martin Straeten wrote:
Do have an idea, what geeqie is doing with the raw file? Simply displaying the
embedded jpg?
In lighttable dt displays the embedded jpg by default - until you process it -
then everything is based on the raw data.
To achieve exactly the same result as the embedded jpg darktable must include
the whole im camera processing stuff the camera manufacturers keeps as their
secret.
So don’t expect darktable being convinced ;)
Am 13.12.2020 um 13:25 schrieb cimatosa <[email protected]>:
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?
Cheers, Richard
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
