darktable-org / darktable-org/darktable

Darktable preview differs from its own snapshot

Open
#20,230 25 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: medium reproduce: confirmed scope: color management understood: clear
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

In the attached screenshot on the right is an image as I see it while editing it in darktable, and on the left is a snapshot of the latest history state of the same image taken just before making that screenshot.

As you can see, the image while editing is significantly darker and has higher contrast than its own current snapshot, even though the two should (conceptually) be identical. When I export the image and look at it in geequie or GIMP, or view it in lighttable as a preview thumbnail, then I also see a brighter-than-desired version matching the snapshot shown on the left.

Steps to reproduce

I do not know how to reproduce this, and it has not happened to me for other images in the past.

Expected behavior

The snapshot comparison, lighttable preview, and exported image should match the appearance of the darktable editing preview much more closely.

Logfile | Screenshot | Screencast

Image

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

5.4.0

What OS are you using?

Linux

What is the version of your OS?

Arch Linux

Describe your system

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce RTX 3070, NVIDIA 590.48.01

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

The issue persists regardless of whether I use high quality processing or not, use the system or sRGB display profile, or disable OpenCL in the settings.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified. Begin by reproducing the discrepancy in darktable 5.4.0 on Linux with the supplied image and compare the editing preview against snapshot, lighttable, and exported output; done means these views match consistently or the cause is isolated.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.