[SOLVED] Changing the preferences of Darktable

By default Darktable does not show any pictures correct as GIMP do. How can Darktable be modified to show the same image colors and brightness as GIMP? I am using Linux.

Thank you.

Hi and welcome.

This topic has been discussed at length multiple times. You can search the forum to find more.

Darktable shows you a minimally processes image. You need to edit it to get it to look how you want it.

If you’ve never read the manual, it is highly recommended: darktable 4.6 user manual - process

What is your reference for what “correct” means?

Welcome to the forum. I am trying to understand your scenario. GIMP cannot display RAW file images so are you comparing how a JPG looks in GIMP to how the same JPG looks in DT?

This is the same jpg open on the same screen at the same time. GIMP is on the left and DT obviously on the right. They are close in rendition but I concede there seems a slight difference in contrast. The choice of display profile in DT affects what I see greatly so I presume the display profile in GIMP is slightly different to DT’s. But who is to say which is right and which is wrong? Only tiny difference at best anyway.

1 Like

Thanks for the reply, but colors is not the same as the RAW file formats. I am talking about the hex values of the RGB color model that is send to the monitor from the graphics-card. I can’t see this issue being discussed in your link. I found a solution that work that I describe below. But I suspect that many of the previous questions was answered incorrectly, as I have found the issue on 4 different computers with different hardware. And they gave 4 different results in terms of the incorrectness of the RGB space Darktable use.

I, am talking about the sRGB color space that is send by the graphics-card to the monitor. Sadly I rarely use the alpha channel at anything but 100%, so I incorrectly reffed to it as brightness. Given the definition of Alpha this mistake is probably common, still I apologize for any confusion.

Sorry, your question does not make any sense to me.

1 Like

There are NO brightness or contrast in sRGB space, only intensity values for red, green and blue(ignore alpha). Brightness and contrast only effect the way that a display device show the data send to it by the graphics-card. But I talk about is the color RGB date that is send to the monitor from the graphics-card, which can be acquired using a screenshot.
So if what you show in your picture is a PNG screenshot intercepted from the graphics-card. Then you also have a monitor that is given incorrect RGB information about what it should display. A color model is a quite precise mathematical model, and it should normally not be possible to directly see any errors in it.
I tried to test this issue today using a PNG color chart made in GIMP. I opened the PNG file in Darktable and saw that now the colors where correct. Apparently opening a PNG file seem to trigger a correct choice of color space in Darktable. So it seems that the solution is to start up Darktable by opening a PNG file to set the correct color space before opening RAWs and JPEGs.

This is how the screenshot looked before (Left: Darktable, Right: GIMP):

I used this PNG of B&W+the colors from a 12 color-wheel:

And this is how it looks after having started up using the PNG file (Left: Darktable, Right: GIMP):

So Dartable can show the correct colors when forced by opening with a PNG file(I doubt that there is anything special about my specific choice of a PNG file). This is a bizarre issue and I have seen it in 4 variations on 4 different PC.

I still don’t know how this will effect Darktables ability to work with GIMP, when opening RAW file in GIMP. But clearly this bug should be fixed.
Anyway thanks for the replies

You likely have some misconfiguration on your machines. If you’d like help troubleshooting, we can proceed.

I still don’t understand what the problem is.

If you open a raw file with darktable, don’t expect to see the embedded jpeg file, the image is very likely darker and “flatter”. Other raw editors may make more of an effort to show something closer to the embedded jpeg.

It might be helpful to tell us what kind of (raw) file you open with the GIMP, and what plugin you use, native GIMP can’t open raw files…

If you give darktable a png file, it should indeed display the same in darktable as in the GIMP on opening, but not raw files…

Wrt. sRGB: that’s a color space, so there are indeed no contrast and brightness there. You do change brightness and contrast of your image when editing.

No, other programs are effected like Darktable. So the problem clearly stem from darktable, and NOT a misconfiguration on any of my machines. And it is the color model preference that is set wrong in Darktable. In GIMP this model can be set under preferences. I can’t find the similar option in Dartable. But apparently starting up with a using a PNG fixes the issue.
Anyway if you don’t understand the problem and the nature of how RGB space works. Then it is very unlikely that you can change any configuration that fixes the problem.

That’s rather a strong claim to make here. Many here know very well how sRGB works, and frankly, their understanding is better than what you show here (but that might be a language issue)

You’re right, the problem may lie between the keyboard and the chair.
More seriously, it could be a problem with the input colour profile
https://docs.darktable.org/usermanual/development/en/module-reference/processing-modules/input-color-profile/
Or the screen
profil

That’s some serious memory-digging and data interception system you are running there. Care to tell me how to do that?

OK. I think it is safe to say we have never seen any report like this. I doubt it is a bug, but it should be investigated. Opening one image in darktable, then opening another should not ‘force’ anything to be carried over; no ‘initialization’ should be required.

  1. What version of darktable?

  2. Wayland or Xorg?

  3. Was your first screenshot also taken in the darkroom, or in the lighttable (the left side, which is dark and has high contrast)?

  4. Do you have a display profile installed?

  5. Is the same profile used in Gimp and other software?

  6. What is the output of darktable-cmstest?

    kofa@eagle:~/darktable-master/bin$ ./darktable-cmstest
    darktable-cmstest version 4.7.0+353~g139f720a6d
    this executable was built with colord support enabled
    darktable itself was built with colord support enabled
    
    primary CRTC is at CRTC 0
    CRTC for screen 0 CRTC 1 has no mode or no output, skipping
    CRTC for screen 0 CRTC 2 has no mode or no output, skipping
    CRTC for screen 0 CRTC 3 has no mode or no output, skipping
    
    DP-2    the X atom and colord returned the same profile
            X atom: _ICC_PROFILE (968116 bytes)
                    description: U2720Q #1 2023-09-13 12-10 D5000 2.2 M-S XYZLUT+MTX
            colord: "/var/lib/colord/icc/U2720Q #1 2023-09-13 12-10 D5000 2.2 M-S XYZLUT+MTX.icc"
                    description: U2720Q #1 2023-09-13 12-10 D5000 2.2 M-S XYZLUT+MTX
    
    Your system seems to be correctly configured
    kofa@eagle:~/darktable-master/bin$ 
    
  7. Is your Pjuske image a JPG? Is its native colour space sRGB (RGB color 8-bit gamma integer in Gimp’s title)? Can you share it here, with the XMP sidecar you use when opening it in darktable for the first time, when it gives wrong colours?

  8. When you open the image in darktable, what does your input color profile module say?

  9. Do you have any soft proofing or similar tool activated?
    image

  10. Is your darktable display profile set to system display profile, or overridden? (Right click on the ‘gamut horseshoe’ icon to display the pop-up.)

For what it’s worth, here is what a JPG image looks like in a freshly opened darktable (in the darkroom view) and Gimp on my machine:

1 Like

Of course it’s not. Raw file is not an image, it’s mostly green mess. All depends on your interpretation.

1 Like

That’s rather a strong claim to make here.
Well I am not making a claim he seem to be. I am not to blame for others words. If they wish to clarify then they are welcome…

Wrt. sRGB: that’s a color space, so there are indeed no contrast and brightness there. You do change brightness and contrast of your image when editing
I newer claimed that the color space contains operator like brightness and contrast! The RGB space is purely data.

You’re right, the problem may lie between the keyboard and the chair.
Well again I am not the one that say that there is something that I don’t understand and then offers to fix it. And offering to help me fix a Linux distro, which is made by many very codependent constructions, seem very risky. I have in the past tried to edit modules. And it was impossible as their codependency really was hidden to a non programmer. And this option was removed later exactly because of this.

More seriously, it could be a problem with the input colour profile
Sadly no, I have already checked this. I suspect that this option is designed to add a printer icc profile. Anyway I did not mention it, but then I have check so much that I could write a novel about it.

I wont be able to reply more before tomorrow.
Good night.

That dark and contrasty cat image looks like as if a gamma profile were forced on a linear image. Here is a (linear) raw file using its default (linear) camera input space:


If I force linear Rec709 on it, the colours break, but overall tonality remains OK-ish:

However, if I force Rec709 with ‘gamma’, the image becomes dark and contrasty, and saturation increases:

I think something similar happened to your cat photo, but we’ll only know if you provide more info (e.g. by answering the questions, sharing files).

2 Likes

Please be more careful with the formatting, it’s very hard to track what’s something you quote, and what is your answer.

input color profile has nothing to do with printing: it describes the input image.

I have trouble making sense of this:

And offering to help me fix a Linux distro, which is made by many very codependent constructions, seem very risky. I have in the past tried to edit modules. And it was impossible as their codependency really was hidden to a non programmer. And this option was removed later exactly because of this.

No one wanted to ‘fix a Linux distro’. And what modules are you talking about? Linux kernel modules or darktable modules?

What do you mean by the following?

I have in the past tried to edit modules

And by this?

this option was removed

1 Like