- Tue Aug 17, 2010 5:07 pm
#328961
I'm not sure it's supposed to work this way - so let me explain and maybe you guys can help me out...
I have a wood map that I have open in photoshop viewed under the Adobe98 color space. (RGB 8-bit).
I also have a render of the wood in Maxwell, lit by two 6500K lights. The map of the wood is basically has 0 sheen so I can test the color.
When rendered and shown (in Maxwell) in the Adobe98 color space, the wood loses some red compared to the file open in photoshop. When I switch the Maxwell render to the sRGB color space, it matches up perfectly. When I bring the sRGB render into photoshop, and either leave "as is" or convert to Adobe 98, it matches up perfectly there too.
My thoughts are that the Maxwell image saved out as Adobe98 should come in perfectly, and that sRGB should come in to photoshop as not-matching. But the opposite is true. Can anybody explain why this is the case?
Thank you,
Ian
I have a wood map that I have open in photoshop viewed under the Adobe98 color space. (RGB 8-bit).
I also have a render of the wood in Maxwell, lit by two 6500K lights. The map of the wood is basically has 0 sheen so I can test the color.
When rendered and shown (in Maxwell) in the Adobe98 color space, the wood loses some red compared to the file open in photoshop. When I switch the Maxwell render to the sRGB color space, it matches up perfectly. When I bring the sRGB render into photoshop, and either leave "as is" or convert to Adobe 98, it matches up perfectly there too.
My thoughts are that the Maxwell image saved out as Adobe98 should come in perfectly, and that sRGB should come in to photoshop as not-matching. But the opposite is true. Can anybody explain why this is the case?
Thank you,
Ian