I was investigating something else, and I saw something not working... I'm under the distinct impression that the Histogram panel should automatically update after every operation. Having the Histogram panel displayed full-time on the screen, it should always be up to date.
However, when I Dodge or Burn or even paint color on an image, the Histogram is not updating.
If I select one of the History states I've just created, it updates.
Consider this simple sequence of operations:
I'm able to reproduce this failure in Photoshop CS5 as well, BUT NOT IN CS4 (it updates in Photoshop CS4 after every painting operation), so clearly it's not a new bug, though somehow I've managed not to notice it in my years of using Photoshop CS5.
Is it broken like this for everyone in Photoshop CS5 and 6?
Could this be some twisted attempt to try to optimize painting performance? If so, why isn't there an option to allow a user to request it to update on every operation on a fast computer with cores out the wazoo?
Thanks for the verification, conroy.
Yes, the double click works for me too, and there's a refresh icon, but these are not acceptable workarounds.
For completeness, I'm running Photoshop CS6 13.0.1 on Windows 7 x64 Ultimate, SP1, everything updated. The problem occurs in all GPU modes and even with the GPU disabled.
Oh yes, I agree that workarounds are unacceptable and was only adding to the info in the thread. I don't even get a refresh icon as a warning that the histogram is not current when painting or D&Bing.
Just making sure ADOBE knows that the workaround isn't the fix.
And I can confirm in return that the little triangular warning symbol isn't tracking either here.
I'm now left to wonder how many times I've glanced over at the Histogram after a Dodge operation and felt falsely confident that I hadn't blown anything out.
I can confirm the behavior you report in both CS6 and CS4 Windows versions.
I guess I got use to hitting the refresh icon and never thought the histogram was failing to update automatically when it should.
In Photoshop CS4 there's no combination of display modes or settings I've been able to find to stop it working properly.
Just the opposite in the two newer versions.
I'm highly intrigued that others see the problem in Photoshop CS4 and I don't. That gives me hope that maybe the problem can be worked around in Photoshop CS6, though I don't yet have a clue how that might happen. I'm going to scout around to see if I ever tweaked the registry entries for Ps CS4... At this point I don't recall...
Just poking around in Photoshop CS6 to see what, if anything would make the Histogram display update...
This bug is easy to reproduce, is shown to be a problem across multiple versions and multiple OSs, and in at least one case (Photoshop CS4 x64 on Windows 7 x64 here) it can be shown to work properly, so the code is probably not far off being right. Seems to me this should be the kind of thing a junior engineer could find and fix so someone, say, at Chris Cox's level could have it done before 5 today...
" Wow, that's interesting, guys, because my copy of Photoshop CS4 (64 bit) is actually behaving properly. "
I was being precise in my comment, though perhaps not clear. I found exactly what you did : A problem in CS6 no problem in CS4.
...and in the case of my report, it was plain user error to say the bug is in CS4 too. Sorry, my bad.
What happened was that I neglected to hit the input toggle switch on my second monitor, which is where I keep my palettes (now "panels"), after testing for the bug in CS6, so that I was indeed working in CS4 on my main monitor afterwards but looking at the totally static CS6 Histogram on my second monitor.
So, the bug is only in CS6.
24 hours after reporting an obvious, reproducible regression bug, plenty of corroboration, and no acknowledgement from Adobe so far.
But I am confident someone at Adobe cares enough to not allow their flagship product to turn to complete mush.
Have you reported it via the Feedback site?
Another day without Photoshop CS6 functionality working properly has passed, and we still don't have the knowledge that Adobe has logged it as a bug.
Maybe I should stop providing Adobe thousands of dollars worth of free customer support out of the goodness of my heart until it's acknowledged.
C'mon, people, how hard is it to say "thanks, we're looking into it"?
Sorry for putting you on the spot, but you've been on the forum over the past two days.
If you don't have the staff to keep up, that's not your users' fault. Users keep sending Adobe a lot of money.
Europe, Middle East and Africa