The Colour (color) Management settings in Digikam correctly allow the editor to permit a number of 'standard' settings. e.g. sRGB or AdobeRGB or ProPhotoRGB. This is correct. However the monitor profile should be set to whatever the Windows System is using (which for keen photographers is likely to be a custom profile set following profiling with a device). The setting for the monitor appears to only allow similar settings to the editor but this is incorrect. The monitor should be set the the Windows system profile whatever that is. STEPS TO REPRODUCE Go to Digikam 7.2.0 settings 'colour management' to view. OBSERVED RESULT Unlikely that immediately observed results would be obvious but this prevents keen photographers from adopting Digikam as a serious editor and likley would lead to it being 'hammered' in any technical review online or in a magazine if I am correct in my affirmation. EXPECTED RESULT The fix would be industry standard consistent colour management and accurate colours between profiled and managed devices. SOFTWARE/OS VERSIONS Windows: Pro 64 latest version as of day reported ADDITIONAL INFORMATION It is not impossible that I am wrong but I think I am correct here and hope I am as I feel Digikam is a fabulous piece of software with (unusually for Linux developers lol) has a great UI. Apologies if I am incorrect and I have wasted time.
At the moment we cannot read the set system color profile under Windows. I am sure that the graphics program Krita cannot do this either. With the porting to Qt6, we plan to also port to Qt's color management system (QColorSpace). However, there is currently no function in the QScreen class in the preliminary documentation of Qt6 to read the color profile from the screen. Maik
Thanks for a prompt response. I am really disappointed to hear this. It is a massive drawback and critical for any image program since if the images cannot be accurately colour represented on screen then it is useless. Since almost all other editors etc and ALL commercial products can do this then how do they achieve this? I believe this to be critical for DigiKam and dearly hope someone somewhere can overcome this. cheers Ian
I should add the colour profile would not be read from a screen (an output device) but from the windows system software and is simply a file so cannot see why this cannot be done?
If you have an *.icc file from your monitor and it is your current profile, you have the option of adding the folder as a search path in the setup tab for profiles, then you should be able to select the monitor profile. Maik
MAik, Scribus has also a CM engine, but i don't know if Windows native profile are used : https://github.com/scribusproject/scribus/tree/master/scribus/colormgmt Gilles
Thanks Maik If I am able to add the windows system profiles folder and I can from that select the correct profile then this indeed should work. There is a danger here for the unsophisticated user as there will often be many profiles for all sorts of devices and even different manufacturer supplied paper profiles. A user many select the wrong one? Perhaps a default set to use the same profile as the windows system uses for the monitor would be better either defaulted (with a reset if someone gets lost?) and others choices (for raesons unknown to me)?
First approch with native code under Windows: https://stackoverflow.com/questions/13533754/code-example-for-wcsgetdefaultcolorprofile In digiKam, native code for windows and MacOS need to be implemented here : https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/dimg/filters/icc/iccsettings.cpp#L307 Gilles Caulier
For MacOS, Applescript can be used : https://stackoverflow.com/questions/60350804/how-to-get-loaded-monitor-color-profile-with-applescript-or-command-line Note, we already use applescript with Qt code in digiKam as for ex to setup screen background image : https://invent.kde.org/graphics/digikam/-/blob/master/core/dplugins/generic/tools/wallpaper/wallpaperplugin_macos.cpp