darktable-org / darktable-org/darktable

negadoctor - custom working profile not selectable - frontier

Open
#20,274 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: invalid 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

Darktable docs for negadoctor mention this:

The working profile parameter in darktable’s input color profile module should be set to either linear Rec2020 RGB, or to an ICC profile representing the actual color space of your film emulsion. Some examples of such ICC profiles may be found in the following forum posts:

https://discuss.pixls.us/t/any-interest-in-a-film-negative-feature-in-rt/12569/177
https://discuss.pixls.us/t/input-color-profile-to-use-for-negatives/20271/13

Going to the second link, I've found an .icm profile for a frontier printer, Fuji_Frontier5-sRGB_CA-DPII_v3a.icm

The docs clearly state that these profiles can be set as a working profile, but this doesnt seem to work, I've downloaded the profile, put it in the /share/darktable/color/out folder (i also tried the /in folder) , but darktable does not let me pick them. Am I doing something wrong, or are the docs outdated?

Steps to reproduce
  1. Go to https://discuss.pixls.us/t/input-color-profile-to-use-for-negatives/20271/13
  2. Download the frontier icm profile (Fuji_Frontier5-sRGB_CA-DPII_v3a.icm)
  3. Copy it into the /share/darktable/color/out folder
  4. Restart darktable
  5. Open darkroom tab
  6. Select "input color profile" module and select a working profile
  7. Notice that the frontier icm profile doesnt show up
Expected behavior

Darktable should let me select the frontier icm profile as a working profile in the input color profile module

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.4.0

What OS are you using?

Windows

What is the version of your OS?

Windows 11 Pro

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

Start with darktable’s input color profile module and reproduce the issue on Windows 11 using Fuji_Frontier5-sRGB_CA-DPII_v3a.icm in share/darktable/color/out, as described. Compare the documented working-profile behavior with the profiles the module displays; the issue is done when the Frontier profile can be selected or the documentation accurately explains the limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
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.