Re: Gray Gamma 2.2 space and Photoshop2022 (23.1.1)
Re: Gray Gamma 2.2 space and Photoshop2022 (23.1.1)
- Subject: Re: Gray Gamma 2.2 space and Photoshop2022 (23.1.1)
- From: Scott Martin via colorsync-users <email@hidden>
- Date: Sun, 13 Feb 2022 11:09:01 -0600
> On Feb 13, 2022, at 2:34 AM, Peter Miles wrote:
> 1: RGB pixel values stay the same when doing conversions from Gray Gamma 2.2
> <-> Adobe RGB (1998) in Photoshop 2019.
Not necessarily!! The RGB values in the Info palette and Color Picker are
subject to your RGB Working Space and intent in Color Settings.
> 2: My understanding is that the Gray axis of Adobe RGB (1998) and the 'Gray
> axis' of Gamma 2.2 space are identical. Values 0 to 255 encoded Gamma 2.2. So
> the color meaning of RGB values along the gray axis of Adobe RGB (1998), and
> the color meaning for the same 'RGB' value in gray gamma 2.2 space are also
> identical.
Yes, but are you actually seeing AdobeRGB numbers in the Info palette and the
ColorPIcker? I bet you’re not. Again, show us your Color Settings in both
versions of Photoshop.
> So that's a null conversion between them. And that expectation is being meet
> with the behavior of Photoshop 2019. It does not change the RGB values for
> gray, when converting in either direction between Adobe 1998 <-> Gray Gamma
> 2.2. But Photoshop 2022 does (on my install).
Maybe that’s because you have the defaults color settings with sRGB set as the
RGB Working space…
Also, what were your Color Setting when you mad the Grayscale file to begin
with? I suspect you could have made the file with sRGB set as your working
space so the 5,5,5 10,10,10 values were sRGB values - not AdobeRGB Gamma 2.2
values. Again, setting a grayscale file with RGB values is a funny thing to do
and subject to this type of error.
> Silent Changes of RGB values in PS 2022:
>
> This gets more interesting. I created a patches in PS 2019 in Gray Gamma 2.2
> space. The RGB patch values were 0, 5, 10, 15, 20. I then saved it with Gray
> Gamma 2.2 embedded. I opened the very same file in PS 2022. The eye dropper
> in PS 2022 indicates that the RGB values have silently been changed (without
> any pop-up warnings) to 0,1,3, 6,12. Yet the L* meaning of those new numbers
> did not change. (all profile mis-match warnings are on.)
Yup, because your RGB Working Spaces are different between the two apps…. It’s
just calculating different values.
> Any one else getting this sort of behavior with Photoshop 2022?
No they are both behaving identically for me when the Color Settings are
synced.
Please show us your Color Settings in both apps before we take this
conversation further.
Scott Martin
www.on-sight.com
Imaging Science for Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden