darktable-org / darktable-org/darktable

AgX is enabled by default for imported JPEG-XL images

Open
#20,238 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
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

If AgX is set as the auto applied workflow, then an imported JPEG-XL image has AgX enabled in its stack. This happens if the bit depth of the JXL image is more than 8. I'm using JXL images with sRGB color profile, just ordinary SDR images, just with a higher bit depth. E.g., imported TIFFs do not have AgX enabled, even if the bit depth of the TIFF is higher than 8. The problem also applies just to AgX, e.g., setting sigmoid as the auto applied workflow does not enable sigmoid for JXLs.

I tried with JPEG-XL images exported both from darktable itself and from Gimp, and the behavior is the same. Tested on Debian 13 with the 5.4.0 appimage from darktable.org, and on win 11 with the 5.4. installer from same.

Steps to reproduce
  1. Set AgX as the auto applied workflow in preferences.
  2. Import a JPEG-XL image with bit depth higher than 8, but with an ordinary standard dynamic range sRGB color profile.
  3. Observe that AgX is enabled in the history stack, when it probably should not be.
Expected behavior

darktable should not enable AgX for JPEG-XL images, the same way as it does not enable sigmoid, or does not enable it for improted TIFFs.

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.4.0-x86_64.AppImage

What OS are you using?

Linux

What is the version of your OS?

Debian 13

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

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

No response

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 file or test is named. Start by locating the JPEG-XL import path and the logic that applies the configured auto workflow, then reproduce the issue with an over-8-bit SDR sRGB JXL and an imported TIFF for comparison. Done means AgX is not enabled for the JXL case while the existing workflow behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.