darktable icon indicating copy to clipboard operation
darktable copied to clipboard

Published 20 hours ago • verified publisher icon darktable-org

Crop interfering with final image colors in unintended ways.

Open Erquint opened this issue 7 months ago • 1 comments

Consulting other ieeus

Seems distinct from #18193.

Specs

  • Windows 10.
  • Darktable 5.0.1.

Introduction

Let me begin with a visual demonstration, but keep in mind that the only changes made between screenshots are:

  • High quality processing toggle.
  • Crop toggle.
  • Crop order.

Demonstration

Screenshot 1 We see some greenish discoloration by the viewport fringes, but that must be because of the low quality preview algorithm, so we should be fine. Let's enable the crop… Screenshot 2 The fringe discoloration gotten worse. Okay, time to enable high quality preview rendering just to be sure… Screenshot 3 Yes, of course, that fixed it. Oh, what's that..? The crop module is ordered improperly. Let's move it where it belongs… Screenshot 4 And we have fringe discoloration back. With the high quality processing enabled.

This is not a preview bug!

Exporting the result to a file carries over the fringe discoloration.
Enabling high quality resampling in export settings does not prevent it.
Reverting to the state illustrated in the third screenshot, where the preview is clean, and then exporting — still produces a discolored file. There seems to be no way for me to be left with a clean image as intended.

Files for reproducing the bug

IMG_20250408_092739_1.zip Including the exported JPEG.

Erquint avatar Apr 08 '25 10:04 Erquint

  1. please use the Issue template to provide all the information. Eg. Self compiled?

  2. why are you moving the crop so late in the pipe?

gi-man avatar Apr 08 '25 16:04 gi-man

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Jun 09 '25 00:06 github-actions[bot]

It would be wrong to close an unsolved issue, impatient tincan.

Erquint avatar Aug 19 '25 22:08 Erquint

Since you edited the original post, no notification was sent of a follow up. Can you test with the current dt version?

gi-man avatar Aug 20 '25 00:08 gi-man

Does the issue still exist in 5.2.1?

wpferguson avatar Aug 20 '25 17:08 wpferguson

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Oct 20 '25 00:10 github-actions[bot]

Closing as crucial info has not been provided.

jenshannoschwalm avatar Nov 02 '25 18:11 jenshannoschwalm