Need help with Proof Colors in CS2

[Anders Nielsen]

Hello everybody.

I have a problem when editing my images in CS2 and hopefully I can get some advice in this forum.

When I am editing my images in photoshop there is a big difference between the result I see in CS2 and the result shown on my webpage. I have uploadet an screenshot of my problem at http://www.pbase.com/image/121521363 the image on the left is shown in CS2 and the image on the right is from my homepage.

I edit my images in AdobeRGB and thereafter converts it to sRGB. When I turn on proof color in CS2 the images look the same in CS2 and on the web - however I have been told allways to leave proof color off. I use Digital Photo Professional (DPR) to convert my image from RAW to TIFF and then edit it in CS2. If proof color is on in CS2 the colours are very different from the original RAW-image and the converted TIFF shown in DPR.

I can't figure out what to do - should proof colors be set to on or off and why? My monitor is calibrateted and the monitor profile is used in color matching settings in DPR.

I hope someone can help me because it is very frustrating when I am allways getting different results.

Thanks in advance
Anders

[Roger Clark]

Anders,
I have a similar problem and it started showing up sometime late last year, even though I have made no changes to my configurations (been traveling and not working on the computer). I have not had time to troubleshoot the problem due to the travel. I'm wondering if something has been added/changed due to a windows update recently. I'm using CS4 and another issue I'm having is that settings change as I go into different tools in photoshop. For example, I'll turn on proof colors and do some work then notice proof colors has been turn off.

Question, what proof setup are you using? What default color space?

One thing that can cause confusion is what is your default color profile? For example, if you do your main work in adobe RGB but have the default profile sRGB, photoshop will change to sRGB on some operations but not notify you you it has done so, and it doesn't appear that it actually converted the profile but just assigned the default one so now you have the wrong colors.

Roger

[Anders Nielsen]

From Roger: Question, what proof setup are you using? What default color space?
Answer: When I edit my images I have proof colors turned off and my working space is AdobeRGB - I don't know if this is what you asked for but otherwise I don't know how to see it?

Where can I see my defalut color profile?

Thank you for your reply.

Anders

[Roger Clark]

From Roger: Question, what proof setup are you using? What default color space?
Answer: When I edit my images I have proof colors turned off and my working space is AdobeRGB - I don't know if this is what you asked for but otherwise I don't know how to see it?

Where can I see my defalut color profile?

Thank you for your reply.

Anders

Anders,
Open photoshop and do not open an image. Go to "edit" then "color settings." The color space in the "working space" is your default settings. I have found that if you work in adobe RGB and the default is sRGB, then after some editing tools, the color settings on your image will be changed to the defauls (e.g. should stay in adobe RGB but gets changed to sRGB).

Also note on that same "edit" then "color settings" menu the other settings and policies. This web page will help explain them and what the settings should be:
http://www.earthboundlight.com/photo...-settings.html

And another one:
http://visualarts.mit.edu/downloads/...r_settings.pdf

Google "photoshop color settings" for many more.

Roger

[Anders Nielsen]

Thank you for your help - the links are very interesting. I did try google before asking here but I didn't find any solution - just people with the same problem.

I still have the problem however.

My default colorspace is AdobeRGB so I don't think my problem is with CS2 changing from AdobeRGB to sRGB. How ever I still have the problem - I suspect that it has something to do with my calibrationprofile not showing correct (but I'm not sure at all!) an other option could be that the problem arise when I convert the images in Digital Photo Professional (my color space here is AdobeRGB too).

I think my main struggle is if proof colors should be turned on with AdobeRGB or my monitor calibration profile as the proof condition or if it should be left off when editing the image - as far as I could read from the first link it is used when you are printing so I am wondering why it affects the outcome when it is matched with my calibration profile?

Anders

[Roger Clark]

I think my main struggle is if proof colors should be turned on with AdobeRGB or my monitor calibration profile as the proof condition or if it should be left off when editing the image - as far as I could read from the first link it is used when you are printing so I am wondering why it affects the outcome when it is matched with my calibration profile?

Anders,

In theory, on a calibrated monitor, when one chooses proof setup of "monitor RGB" and then one selects proof colors, you should see no change. On my laptop this is the case. On my desktop, it is not the case: the colors change. This may be due to two active packages trying to manage colors. For example, if you have adobe
gamma running and other monitor calibration software, they will collide to give strange results. I have checked for two system running on my desktop and do not see any, so I'm still searching for the problem.

Roger

[Anders Nielsen]

Roger, that sounds exactly like the problem I have. I have removed Adobe Gamma but the colorchange is still there. Hopefully someone else knows what's wrong.

Thank you for your response on this issue - it's nice to know I'm not the only one.

Anders

[Roger Clark]

I just went through all the processes running on my desktop and can find none that might be colliding, EXCEPT there is the spyder3 stuff running with the NVidia drivers for my video card nvsvc32.exe. I am wondering if they are colliding?

Roger

[Anders Nielsen]

I use a spyder3 to calibrate my monitor too. Most likely it has nothing to say but I just can't help wondering if it could be an issue related to the spyder-calibrationprofile (I am a novice in calibration so it is just a thought).

Anders