Hi Pascal, > We've recently discovered that Darktable's (a photography application) > internal sRGB profile seems to encode a D50 whitepoint even though we > are passing a D65 whitepoint. The current theory is that this changed > when we migrated from lcms1 to lcms2.
Yes, as Kai-Uwe says, this is the expected behavior for a V4 CMM, and that is what lcms2 is. Please note most if not all modern CMMs behaves in such way, for example all Adobe products. The difference is only in the absolute colorimetric intent. It is fully described in this paper from ICC: http://color.org/ICC_white_paper_6_v2_and_v4_display_profile_differences.pdf If anyway, you prefer the old behavior despite that would made your application inconsistent, you could use cmsSetAdaptationState(0) at the init time. > Also, we noticed lcms2 seems to default to ICCv4: Yes, v4 is from 2001 (11 years right now!) Actually most vendors are using modern versions. > Is there any way we could stick with ICCv2 (for greater compatibility)? Well, lcms2 can read and use v2 profiles, no problem on that. If you want to save profiles as v2, this is as easy as calling cmsSetProfileVersion(hICC, 3.4) before saving the profile. On depending on the version number the tags are saved by using different structures. But again, Kai-Uwe is right. Check the applications you want to be compatible. Photoshop for example, which is regarded as the industry standard works in the V4 way. Best regards Marti ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
