Version: (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages When opening the image without color profile (more specifically no profile recognized by Digikam) in editor, the colors are displayed wrongly. This seem as a result of fact, that Working space profile is somehow applied to these images. This would get mostly unnoticed in case wokring space is set to sRGB (as the most images without profile are sRGB in fact). Though when some wide gamut space like ProPhotoRGB is used as working space, then it becomes apparent. Wide gamut spaces are actually good for postprocessing. It doesn't make change if I select Convert, Apply or Do Nothing in missing profile dialog, the image is always displayed wrongly in same fashion - oversaturated and shifted colors. It's happening to RAW images too. Here I'm bit confused with Digikam behavior. If I don't specify input profiles the behavior is same as for the JPEGs and TIFFs. If I specify input profile, then in case I press Convert the result colors are still wrong but in different fashion. Apply profile and Do Nothing still do the same as in case the input profile was not here. With RAW's (DNGs) I'm even more intrigued when the color management is turned of. Editor apparently don't apply the DCRaw color matrices to image. This makes all raw decoding in Digikam virtually useless as just only very few user will ever be able to produce their own profiles or get valid and compatible input profiles elsewhere. Color matrices in DCRaw are actually pretty good... So is profile included in DNGs. But this is maybe different issue. Hope you can understand. Regards M.
The first part of this bug is solved. Choosing to convert to working space (wide gamut) does not change the image appearance (with color managed view enabled, of course). I have also clarified some of the options regarding RAW loading. All changes will be available with 1.0-beta4. Please test and report any further problems.