darktable-org / darktable-org/darktable
washed out colors after returning tiff from GIMP
Nobody has claimed this yet.
- 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
-
Used script "external editors"
-
Exported tiff/adobergb to "collection"
after opening in darkroom it has input "embeded color profile" -
tiff opened end edited in GIMP and overwrited
-
After returning to dt appears strange colors. afetr opening in darkroom it has input color profile - sRGB
-
After changing to AdobeRGB - colors are ok
-
After changing to sRGB - colors are little different than AdobeRGB but not so as in point 4
Steps to reproduce
Described above
Expected behavior
No response
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
I dont know
darktable version
5.0.1 AppImage
What OS are you using?
Linux
What is the version of your OS?
Kubuntu 24.04
Describe your system
Just after exporting to collection
Embedded color profile
After returning from GIMP
sRGB
AdobeRGB
sRGB, but totally different look
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
nvidia, 550
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported external-editors workflow with a TIFF exported as AdobeRGB, edited and overwritten in GIMP, then returned to darktable. Compare the embedded profile and displayed colors before and after the round trip, using the screenshots and version details in the issue; the issue names no source files or tests, so done requires narrowing the cause and defining the expected profile handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100