Am 10.02.2013 14:00, schrieb Tobias Ellinghaus: > Am Sonntag, 10. Februar 2013, 11:03:46 schrub S. Witt: If you are > using git master you can now start darktable with "-d control" to > see where darktable gets its profile from. cool... That's, what I was looking for :) It tells me, the profile is taken from _ICC_PROFILE and the size information matches exactly the size of the profile file. When I remove the property with xprop, the profile is retrieved from colord. Hence dt obviously loads the profile correctly and my problem seems to be located on the system side.
Currently I suspect it has something to do with inconsistencies, occurring after a suspend to ram... probably due to the nvidia driver!? It appears that the LUT data, loaded by the X server, are corrupted after waking up from suspend to ram--unfortunately not obviously visible. I just noticed it now, because I wanted to load a completely different monitor profile with GCM for testing and nothing changed. Using dispwin on the command line didn't change anything either. After restarting the X server, profiles could be loaded again correctly and DT's output is consistent again. So don't trust your colors after a suspend to ram ;-) > Ok, let me shed some light on how we load display profiles since > that seems to confuse a few people: Thanks for the details! Regards Sören ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
