After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 593498 - Color balance: Range selector has virtually no effect
Color balance: Range selector has virtually no effect
Status: RESOLVED DUPLICATE of bug 541859
Product: GIMP
Classification: Other
Component: General
2.6.7
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-08-29 16:18 UTC by Roger.Duncan59
Modified: 2009-08-29 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Test image for Bug 593498. (459 bytes, image/jpeg)
2009-08-29 16:50 UTC, Roger.Duncan59
Details

Description Roger.Duncan59 2009-08-29 16:18:32 UTC
In the color balance tool it is possible to select for which range (Shadows, Midtone, Highlights) the adjustment should be effective. 
I found that the range selection has nearly no effect - the adjustment always affects the complete image no matter which range has been selected. The modified image looks almost identical when "shadows" or "highlights" had been selected. With the "midtone" setting the only difference seems to be that the effect of the adjustment sliders is slightly weaker. 
This problem is absolutely reproducible (at least for the Windows version) and has been confirmed by other users as well.
Comment 1 Martin Nordholts 2009-08-29 16:19:46 UTC
Hi! What are the exact step-by-steps on how to reproduce?
Comment 2 Roger.Duncan59 2009-08-29 16:50:13 UTC
Created attachment 141988 [details]
Test image for Bug 593498.

This image allows to duplicate the bug 541859.
Comment 3 Roger.Duncan59 2009-08-29 17:06:36 UTC
1. Open the attached image (or any other image which contains dark, midtone and highlight areas).
2. Open Color - color balance.
3. Select the range "shadows".
4. Move one of the color adjust sliders, e.g. the first one all the way to "red".
5. See that in the image not only the shadows, but also the midtone and highlights become red. Save the resulting image for comparison.
6. Move the color adjust slider back to neutral position.
7. Select the range "highlights".
8. Repeat step 4.
9. See that again not only the highlights, but also the midtone and shadows become red. Save the resulting image for comparison.
10. Compare the images from step 5 and step 10. The difference, if any, is marginal.

The normal behavior should be that in step 5 the midtones should change less than the shadows, and the highlights shouldn't be affected by the slider.
In step 10 only the dark areas shouldn't be affected by the slider.

The problem occurs with any color adjustment (all 3 sliders, also for smaller adjustments).

In the meantime I found that this bug has been reported 1 year ago as bug 541859.
Comment 4 Martin Nordholts 2009-08-29 17:07:54 UTC
Thanks for the step-by-step, but if it's a duplicate we'll have to close it as such.

*** This bug has been marked as a duplicate of bug 541859 ***
Comment 5 Roger.Duncan59 2009-08-29 17:16:48 UTC
Ok that is clear, so does this mean that will I find all future activities on this bug under #541859?
It seems that there have been no activities in the thread of #541859 for a long time - I wonder what the reason could be.
Comment 6 Martin Nordholts 2009-08-29 17:18:29 UTC
Yes, updates will happen in the other bug report.

The reason nothing has happened is because no one found the time and/or interest to do anything about it. There are more important things to work on you know.
Comment 7 Roger.Duncan59 2009-08-29 17:47:29 UTC
Sorry for asking silly questions. I am a new GIMP user and don't know what the developers are currently working on and what the priorities are. I just stumbled over this bug which appeared very obvious to me. Since the color adjustments are not something very special but something that most photographers will use I wondered that nobody should have noticed this problem. When finding the duplicate, I saw that it had been reported a long time ago and the thread seemed to have fallen asleep a little bit.