[Digikam-devel] [Bug 125733] New: Enabling 'Always apply ICM profiles' can lead to suprising results

[fj.cruz at supercable.es]

---- Duncan Hill <kdebugs at nacnud.force9.co.uk> escribió: 
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>          
> http://bugs.kde.org/show_bug.cgi?id=125733         
>            Summary: Enabling 'Always apply ICM profiles' can lead to
>                     suprising results
>            Product: digikam
>            Version: unspecified
>           Platform: unspecified
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: wishlist
>           Priority: NOR
>          Component: general
>         AssignedTo: digikam-devel kde org
>         ReportedBy: kdebugs nacnud force9 co uk
> 
> 
> Version:           0.9 SVN (using KDE KDE 3.5.2)
> Compiler:          gcc 4.0.2 prerelease 
> OS:                Linux
> 
> If the ICM option is configured to always apply the ICC profile to an image when the editor is opened, the result can be quite a suprise to the unsuspecting user.
> 
> Open a RAW file with sRGB for Workspace and Monitor, and the camera profile for Input.
> Save the file as PNG or JPG.
> Close the RAW.
> Open the PNG/JPG.
> Notice that the profile has been doubly-applied, so the picture is 'ruined'.
> 
> Arguably, setting the option to 'Ask whether to apply profile' is the way around this.  However, when I'm working on 1000 RAW images, having to click that extra button each time is slightly annoying.  Perhaps digiKam should embed the profile data that was applied when a save is done, and detect that there is already a profile in place.
> _______________________________________________

We know about this issue and are working to embed profiles in pictures. In any case, this is the way other graphic apps work.

Paco Cruz