Project

General

Profile

Bug #11191

cached(?) custom input color profile renders noise

Added by Hartmut Knaack almost 3 years ago. Updated almost 3 years ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
10/01/2016
Due date:
% Done:

20%

Estimated time:
Affected Version:
git master branch
System:
openSUSE
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I have placed a custom ICC profile for my camera in ~/.config/darktable/color/in/ and selecting it in Darktable works fine. When Darktable gets closed, while an image with such custom ICC profile is still selected/edited (Lighttable/Dark Room), it causes the following problem on next start of Darktable: images with that exact color profile assigned are rendered as color noise (see attached picture Darktable-post.png).

Work-around: open/select an image with embedded color matrix (like sRGB of JPG) before exiting Darktable.

Darktable-pre.png (1.21 MB) Darktable-pre.png initial state with custom color profile assigned Hartmut Knaack, 10/01/2016 11:19 PM
Darktable-post.png (1.72 MB) Darktable-post.png after restart of Darktable Hartmut Knaack, 10/01/2016 11:20 PM
SX160IS_x.icc (1.09 MB) SX160IS_x.icc Hartmut Knaack, 10/04/2016 01:07 PM
IMG_0403.DNG (23.6 MB) IMG_0403.DNG Hartmut Knaack, 10/04/2016 01:19 PM

History

#1 Updated by Tobias Ellinghaus almost 3 years ago

Please upload the profile.

#2 Updated by Hartmut Knaack almost 3 years ago

There you go, also the sample DNG image.
For testing purpose, I also had copies of the same ICC file with different file names in ~/.config/darktable/color/in (all with the same checksum). So, when one of them resulted in such "noise", I could get proper results using a copy of that ICC file.
This also showed, that every image with that particular ICC file selected (which was last used before Darktable was closed, previously), would just render as noise. Images with other ICC files selected were rendered fine, switching to any other ICC file rendered fine.
It looks to me, that Darktable either tries to "cache" the decoded ICC file when closing and has problems to properly read it back later, or there can be problems loading the file on application start (race conditions?).

#3 Updated by Tobias Ellinghaus almost 3 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

Hmm, here everything works fine using that DNG and profile. I suppose it's unrelated to the actual profile used as there is nothing darktable caches wrt. profiles.

Also available in: Atom PDF

Go to top