Bug 267361 - When using the luminosity curve in the image editor on an initial import from NEF, all changes are irreversible and cumulative.
Summary: When using the luminosity curve in the image editor on an initial import from...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Editor-Curves (show other bugs)
Version: 1.8.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 05:54 UTC by mjjohnson.geo
Modified: 2017-08-07 08:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mjjohnson.geo 2011-03-01 05:54:21 UTC
Version:           1.8.0 (using KDE 4.6.0) 
OS:                Linux

When I single-click on a RAW file (NEF format) in digiKam and it opens up in the image editor, I have a problem while changing the luminosity curve. Namely, if I make an adjustment, and then move the curve back to its starting position (either manually or by hitting reset), the change persists: it doesn't get undone/reversed in the preview. If I then tweak the curve again, the new changes get added onto the new changes. (This isn't just the preview, either: the resulting image after I hit "import" also shows the cumulative adjustments.) The only way to get back to the original state that I've found is to close the image editor and start over. As a result, the luminosity curve feature is completely unusable. This is new to 1.8.0; the luminosity curve worked as expected in 1.7.0.

Reproducible: Always

Steps to Reproduce:
Open Digikam 1.8.0. Go to an album and single-click on a NEF image to open it in the image editor. Make a noticeable change to the luminosity curve (in the "post processing" tab). Notice how the preview changes. Now change the curve back, and notice that the preview doesn't get reverted. Make the change again, and notice how it adds to the previous change, rather than being made afresh. (Repeat the last several steps as desired to see the effect building up.)

Actual Results:  
I had an image with hugely exaggerated curve adjustments.

Expected Results:  
It should have only performed the adjustments matching the curve shown in the luminosity curve window, instead of adding all the adjustments I ever did (and had later undone/modified).
Comment 1 mjjohnson.geo 2011-03-01 07:23:09 UTC
Actually, I just found that it's possible to "reset" the preview to be correct (that is, to match the actual curve shown) if I go back to the "raw decoding" tab and change something, and then hit "update". But the bug persists if I make any further changes to the curve; this is, at best, a very clumsy workaround.
Comment 2 caulier.gilles 2011-03-01 07:59:58 UTC
Fixed in 1.9.0 and 2.0.0

Gilles Caulier
Comment 3 caulier.gilles 2011-03-01 08:01:10 UTC
http://sourceforge.net/projects/digikam/files/digikam/1.9.0/

Gilles Caulier