If the image I bring into PS from Lightroom was exported with the the aRGB profile and my working space is aRGB, am I wrong in converting to sRGB when I save the image for the web? I thought you only assigned a profile to untagged images when you know or are making assumptions about the meaning of the underlying color numbers.
I’ve been doing some more testing and so far these have been my findings. I’d be curious to know if I am approaching this correctly.
-
When I work on my high gamut display and convert to sRGB I see a pretty large shift in colors. What I have been doing is to open the aRGB image, make a duplicate in PS, and then convert it to sRGB. I then softproof to MonitorRGB and then adjust the colors of the duplicate sRGB image to match the colors of the original aRGB image, or as close as possible, then save it out for the web.
-
Although it completely defeats the purpose of color management, I’ve found if I untag my aRGB image or leave the aRGB profile intact, when I view it in a non-color managed application it looks perfect on my high gamut display, as the gamut is pretty close to aRGB. However, it also looks just as good on my macbook pro display. I do understand that leaving aRGB assigned is ignored by non-color managed applications, my point is simply the images seem to look better on all of my displays when not color mananged.
Have I missed anything or is my knowledge flawed somehow? I thought when an image is coverted, the rendering intent will either clip or remap out of gamut colors to the target color space. It seems however the higher gamut display is reading color differently and somehow doing its own conversion.
Cheers,
Jeff