- This topic has 62 replies, 7 voices, and was last updated 1 year, 3 months ago by
.
-
Posts
-
I’ve found a hacky workaround for the Photoshop bug:
When creating the sRGB 2.2 Gamma profile for Embedding, adjust one of the primaries a miniscule amount that is not noticable. (ie. from 0,64 to 0,641). As long as the primaries don’t exactly match sRGB, the profile will work as intended and override the Standard sRGB Working Space.
This is consistent with my guess that Photoshop discards the profile because it believes they are identical. I’ve tested this using the Custom RGB tool in Photoshop so far.
What was the PS bug again?
I just want to say you are an angel, thank you for continuing to ask the questions you did in the clear, concise, and calm way that you did. Vincent’s answers were similarly not understandable for me, but you managed to get this whole thing clarified. Now things are displaying properly in photoshop, thank you! Although, I do have to say, after doing the custom 2.2gamma sRGB profile as proof colors, photoshop’s blacks are slightly darker than chrome’s blacks. not entirely sure why..
This display shows 90% of DCI-P3, while you use wrong correction for near-sRGB panels. Here I attach .ti3 measurement file for BenQ PD2705Q that has similar gamut, select it in correction building window, also set near 160cdm lightness and build a personal correction for your display/colorimeter. Your test shows that all is OK, but significantly wrong gamut may result in wrong color lightness and saturation. Also check Photoshop defaults for image profiles, check for sRGB profile in test image (left bottom corner in Ps, switch from size to profile). I don’t think that there are signal limitation problems (16-235 for TVs instead of 0-255), but also check it in driver settings. Use DP connection with nVidia cards.
Thank you.
