Photoshop CS6 is interpreting saved Brightness/Contrast action steps differently than CS5.
The following two screen grabs were captured after double-clicking the exact same saved step in a saved action that removes banding noise.
Note that Photoshop CS5 has interpreted the step as having the [ ] Use Legacy value selected, while CS6 has not.
This could be at the root of why some folks are reporting actions compatibility issues.
Allowing this failure to remain in the release is going to mean I'm going to have customer issues with my commercial actions, many of which I have not had to change for 6 major version releases now.
It needs to be addressed!
Other folks are getting acknowledgement and feedback from Adobe personnel, ''I have logged a bug'', etc. Could I please ask for the same courtesy?
I can supply you with an action you can use to test with if you'd like. Matter of fact, here's one. Run it on Photoshop CS5 and CS6 to see a major difference in results.
Good catch on that one, and thanks for pointing it out.
It is having to do with the way we handle the Use Legacy command and the way CS5 created actions. CS5's action recorder didn't log the "Use Legacy" as being on, since it was already "on" by default, and since no "change" was made, there wasn't a command logged showing the "no change" of Use Legacy.
In CS6, the Use Legacy default has changed, and since the action isn't specifying a direction either way with the Use Legacy command, the Brightness and Contrast action is moving ahead with Use Legacy defaults (set to OFF in CS6).
We're investigating this further for future solutions.
In the meantime, a workaround for this type of action is to be re-recorded or at least this ONE adjustment step needs to be re-recorded
I've already crafted a replacement step using Curves, which I'm holding in my back pocket and which will be compatible across the board, but I'll still need to make a release for Photoshop CS6 compatibility if you don't change the way Photoshop CS6 plays older actions to make it more compatible.
Thanks very much for putting your efforts into this!
I may be asking a lot, but can anyone at Adobe tell me whether this is likely to be corrected by the time Photoshop CS6 actually releases?
If not I need to prepare some releases of my software.
To give you the heads-up on this.
The fix for this is unfortunately not able to make it in the final release.
That's not to say it won't be fixed for future (it will be), but for release this one will be around.