Am Donnerstag, 4. Januar 2018, 19:20:52 CET schrieb Matthias Bodenbinder: > Am 04.01.2018 um 19:08 schrieb Matthias Bodenbinder: > > Am 04.01.2018 um 18:59 schrieb François Patte: > >> Bonjour, > >> > >> I just tried to experiment gimp 2.9 (development version): openning a > >> raw file opens darktable and once you have finish to treat your photo in > >> darktable, closing darktable imports the photo in gimp... Ok. > >> > >> But the result I had was awful: the image is to bright, without contrast > >> and the saturation is bad... A part of the treatment done in darktable > >> is to be done again.... > >> > >> Does someone experienced the same problem?
Thank you for reporting! > >> Thank you. > > > > I can confirm. The resulting images in gimp are too bright and not > > saturated enough. They look a.ot different then in darkroom. > > > > I tested with RAW from different cameras. All behave the same. > > > > May be an import bug in gimp. ? > > > > Matthias > > > > __________________________________________________________________________ > > __ darktable user mailing list > > to unsubscribe send a mail to > > [email protected] > It is weird. > > I import CR2 with gimp-2.9.8. gimp starts DT. in DT I export to file which > gives a much too dark(!) image. When I exit DT the image given to gimp is > mucht too bright(!). The problem was that darktable was exporting as sRGB. GIMP then interpreted the file as linear data so the lightness of pixels was off. That was a bug in darktable which should be fixed now. > Also, DT siwtches export color profile to linear-rec-709-RGB. But changing > it to anything other than that, like sRGB, has no influence on the > resulting image in gimp darktable defaults to linear Rec709 when called from GIMP. You could select some other *linear* profile in the export module on lighttable. That just didn't work due to a bug. > Matthias Tobias
signature.asc
Description: This is a digitally signed message part.
