Project

General

Profile

Bug #11763

Exported image looks different than darkroom

Added by Pedro Pimenta almost 2 years ago. Updated 6 months ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
Lighttable
Target version:
-
Start date:
10/08/2017
Due date:
% Done:

10%

Estimated time:
Affected Version:
2.2.5
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

It does not matter the export settings (this is happening even with 1:1 copy), the output is completely different from the input

20170927_0006.CR2.xmp (15.5 KB) 20170927_0006.CR2.xmp Pedro Pimenta, 10/08/2017 09:14 AM
20170927_0006.CR2.pp3 (9.91 KB) 20170927_0006.CR2.pp3 Pedro Pimenta, 10/08/2017 09:14 AM
20170927_0006.CR2 (25.4 MB) 20170927_0006.CR2 Pedro Pimenta, 10/08/2017 09:18 AM
2018-01-31 20_45_42-darktable.png (907 KB) 2018-01-31 20_45_42-darktable.png Screenshot of the Darkroom Arne Hamann, 01/31/2018 05:53 PM
P1310216.png (14.6 MB) P1310216.png The exported result Arne Hamann, 01/31/2018 05:59 PM
Screenshot darktroom.png (1.24 MB) Screenshot darktroom.png screenshot of image in darkroom Marcus Bungert, 06/17/2018 11:27 AM
exported.png (22.8 MB) exported.png exported as .png Marcus Bungert, 06/17/2018 11:29 AM
exported.xmp (14.8 KB) exported.xmp corresponding .xmp file Marcus Bungert, 06/17/2018 11:31 AM
haze-removal.png (1.85 MB) haze-removal.png only haze removal used after import Marcus Bungert, 06/17/2018 12:11 PM

History

#1 Updated by Tobias Ellinghaus almost 2 years ago

I sure hope that the output looks different than the input, you are using a bunch of modules after all.

#2 Updated by Pedro Pimenta almost 2 years ago

Tobias Ellinghaus wrote:

I sure hope that the output looks different than the input, you are using a bunch of modules after all.

Im sorry, i've not expressed myself clear. The thing is that the exported result is very different from the final output in the editing pipeline, and I dont know why. Im struggling to export this specific photograph in a long time.

#3 Updated by Žilvinas Žaltiena almost 2 years ago

Pedro Pimenta wrote:

Tobias Ellinghaus wrote:

I sure hope that the output looks different than the input, you are using a bunch of modules after all.

Im sorry, i've not expressed myself clear. The thing is that the exported result is very different from the final output in the editing pipeline, and I dont know why. Im struggling to export this specific photograph in a long time.

Are you saying you are seeing very different image in darkroom and while viewing the exported one? Can you describe the difference. I have tried exporting it and observed only slight color shift (probably because of noise and how downscaling works in the viewer).

#4 Updated by Pedro Pimenta almost 2 years ago

Žilvinas Žaltiena wrote:

Pedro Pimenta wrote:

Tobias Ellinghaus wrote:

I sure hope that the output looks different than the input, you are using a bunch of modules after all.

Im sorry, i've not expressed myself clear. The thing is that the exported result is very different from the final output in the editing pipeline, and I dont know why. Im struggling to export this specific photograph in a long time.

Are you saying you are seeing very different image in darkroom and while viewing the exported one? Can you describe the difference. I have tried exporting it and observed only slight color shift (probably because of noise and how downscaling works in the viewer).

the contrast, local adjustments, hue, brightness... Everything seems way different than usual.

Take a look: https://imgur.com/a/oR3MA

#5 Updated by Tobias Ellinghaus almost 2 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete
  • Subject changed from This specific photograph crashes the export module to Exported image looks different than darkroom

Just a wild guess: Either your image viewer that you are using to look at the exported image isn't color managed, or darktable is using a wrong display profile.
As a first step you could import the exported image into darktable. Does that now look like what the original raw looked like in darkroom?

#6 Updated by Pedro Pimenta almost 2 years ago

Tobias Ellinghaus wrote:

Just a wild guess: Either your image viewer that you are using to look at the exported image isn't color managed, or darktable is using a wrong display profile.
As a first step you could import the exported image into darktable. Does that now look like what the original raw looked like in darkroom?

No, it looks the same as the jpeg as im seeing it in my image viewer.

#7 Updated by Tobias Ellinghaus almost 2 years ago

  • % Done changed from 20 to 10
  • Status changed from Incomplete to Confirmed

I think I can confirm your findings. However, even zomming in darkroom mode changes colors already. My guess is that the extreme noise is tricking us in some zoom levels into seeing other colors than there are. Or something else. I didn't dig deeper into this. Maybe you can try to find the one module that is causing the color shift?

#8 Updated by Pedro Pimenta almost 2 years ago

Tobias Ellinghaus wrote:

I think I can confirm your findings. However, even zomming in darkroom mode changes colors already. My guess is that the extreme noise is tricking us in some zoom levels into seeing other colors than there are. Or something else. I didn't dig deeper into this. Maybe you can try to find the one module that is causing the color shift?

I've made some testing but came to nothing conclusive. With only exposure, white balance and sharpness adjustments I could export it right, but after noise reduction things start to not work anymore. But i've tried to edit it without the noise reducion modules, and still could not get good results. It seems that any major changes, like a Levels adjustment, leads to bad exported results.

#9 Updated by Arne Hamann over 1 year ago

Hi,
I think I got the same Problem, in the attachment is a screenshot of the darkroom and the export result. If it is Helpfull I could upload the raw too.
It doesn't matter in which format I export.
I also created a stile with exactly the settings like I did bevor and exportet with the new style but it doesn't work too.
Screenshot Darkroom:
Export:

#10 Updated by Anonymous over 1 year ago

Spam removed

#11 Updated by Marcus Bungert about 1 year ago

Pedro Pimenta wrote:

It does not matter the export settings (this is happening even with 1:1 copy), the output is completely different from the input

I do have the same problem with darktable 2.4.4. After exporting with sRGB, AdobeRGS, as jpeg 80%/100%, .tif uncompressed or png, the image looks completly different to that what I can see in darkroom. Also the exported image is very "noisy". Please find attached the darkroom screenshot, the example export, and the corresponding .xmp file.

Yes, I used a lot of modules... maybe one module is the reason for that?

#12 Updated by Marcus Bungert about 1 year ago

I used haze removel with same values above. It doesn't make any sense to the image but it shows the difference to the exported png file (on the rights side). The values: strength 0,71, distance 0,184

#13 Updated by Roman J 12 months ago

Marcus Bungert wrote:

I used haze removel with same values above. It doesn't make any sense to the image but it shows the difference to the exported png file (on the rights side). The values: strength 0,71, distance 0,184

I confirm that module 'Haze Removal' affect to export differences at version 2.4.4 for me as well.
Looks like as module broke pipeline processing and impact/mesh to Color space/profile.

#14 Updated by Randy Thomae 11 months ago

I think I have the same problem. My exported file is overexposed by .25E and desaturated, for starters.... It looks completely different from my edit, with calibrated monitor, correct display profiles, etc. I have sold work that I cant produce because I cant create a file for my print lab.

However, I noticed the histograms are quite different so I experimented and found that the histogram changes on every raw image exported to TIFF.
I can isolate it to the minimum modules possible, might be in the input color profile module when using standard color matrix:

Open raw image. Turn off every active module (base curve, highlight recom, orientation, sharpen, white balance)
Export as 16bit tiff.
View both files in darktable - the histogram of the TIFF shrinks from the raw.

If you open the unedited Tiff in darktable and export as TIFF - no change. However, I edited the tiff and exported, and the image shifts, although much less than the raw file to tiff did, but it goes out of gamut so its not printable. It seems like something is going on with the color conversions. There should be no conversion in the AdobeRGB to AdobeRGB TIFF export with absolute colorimetric, right? This should be easy to reproduce, can someone verify that their darktable is not doing this?

This is a Sony A6000 .arw file if it helps.

#15 Updated by Stefan Dieke 10 months ago

Darktable offers a lot of powerful features, which I learned to love and will miss dearly in other programs. But all these features are becoming irrelevant, as does color calibrated hardware, when the export produces something different. But the priority for this bug is 'low'!?! Makes me wonder, what has high priority.

Sorry for the rant.

#16 Updated by Chris H 8 months ago

I can confirm that Haze Removal is the problem here. I tried to export one of my JPEGs with haze removal enabled and they came out very much over-exposed and over-saturated as described by Randy. As soon as I disabled haze removal, everything was just fine.

This is on Darktable 2.6.0, Ubuntu Linux.

#17 Updated by kaushik meta 6 months ago

Hey All,

I am new to editing and started using Darktable few days ago. But i noticed that I am also getting the same issue for some images. The edited images in Darkroom take may be a few seconds to take on the new module changes. But if I again go to history and click on a module one after another the changes are not reflected. But the image to top left shows the corrected one. I dont know if this is expected . As mentioned above, the image has high noise and colors look bland. What i noticed is that these issues happen with RAW images and not with jpg. In case of jpg what ever changes i make it stays and exports same.

#18 Updated by Robert Krun 6 months ago

My father and I experienced the same issue with both a Surface Pro and Windows 10 64 bit. He is using Canon Raw files and I am using Sony ARW, so it might be somewhere else. I thought it might occur by graphics card because there are two inside, but nothing helped yet. It worked in the past but now it does not for the last 4 versions approximately.

Also available in: Atom PDF

Go to top