No it doesn’t. It may look fine for you, because you’re the only one using your own monitor profile. As your monitor drifts over time, the method on that website pretty much guarantees that you will not be able to keep your colour consistent. That website has been brought up here before and it is BAD ADVICE! One should NEVER use the monitor profile as the working space. The working space should be a predictable, consistent space such as sRGB or AdobeRGB.
Photoshop is colour managed, web browsers are not, which is why they only show you colour through your monitor profile, with no accounting for what that colour actually looks like. Best bet is before you save out your image, convert to sRGB to make the colour look the most consistent on most monitors, but you should first profile your monitor and change your working space to something other than your monitor profile.
Smudge:
The author of your linked post even admits:
"Doug Avery said on 04/09 at 08:15 AM
Jerome, you had a good point in that sRGB really is how were supposed to be doing our color work. I just cant, for the life of me, get it to work correctly!
Based on what were saying, I think viewing in sRGB and then Save-For-Web converting to sRGB should produce visually identical results. One is viewing a skewed version of the colors, the other is saving the colors out through a skewed filter, so it should match up. But theres still some mysterious X factor Im not quite getting that prevents this from actually working correctly
"
I’m at a loss then… so there is no way for Photoshop to save images as you see them in the Photoshop workspace? That seems strange to me. Any other settings, other than what was explained on the above site, changes the colors to very muted and dull colors. I have not had this problem before CS3 and do not have this problem with lightroom.
This is not a browser issue. If I save anything (for web or otherwise) the color is muted in any program I open it in (photoshop, lightroom, firefox, etc)… it’s actually changing the colors…
Smudge –
This has been hashed to death in both the Mac and PC forums in the last year and stems from fundamental misunderstanding of color spaces, monitor spaces and how non color managed programs display files.
You don’t state it, but I’m sure that your seeing a difference only in non color managed applications. In addition you have a monitor that is NOT sRGB in its basic character. When you are viewing the file in Photoshop, both the working space profile and the monitor profile are used in conjunction to give you a proper display. When you view in Windows Explore or any other non color managed program, that application is \assuming the file to actually be in Monitor RGB. Now, if you were using an old CRT monitor – which were all basically sRGB monitors, you would see almost no change – the way it’s been for years, but since you have a new wide gamut LCD screen, what you’re seeing is the difference between sRGB and your specific Monitor RGB. In effect you are assigning the wrong profile to your files when viewing them in the non color managed apps. That’s exactly why when you set Ps to Monitor RGB as a working space, everything now matches – but will only do so on your screen, never anywhere else.
I posted a few posts on Viget earlier this year explaining this to them but they didn’t want to hear it, instead happy to go about their business with the newfound "discovery" and not having the slightest understanding of why their problems seemed to have been solved. This is really basic stuff when you get right down to it, but a lot of people like to make is seem obtuse.
First of all…thanks for all of your help everyone!
But I guess I’m still missing something. If I would only see the effects in non color-managed apps, then why do I see it in PS (a color-managed app).
And I guess I still don’t know what to do to correct this… what am I supposed to set my monitors profile to? If it is set to sRGB, the same problem occurs. And, again, this doesn’t happen in Lightroom, which is a color managed application, correct? Anything exported from LR looks fantastic… but this is useless for web design. And is this something that has changed from previous versions of Ps? I didn’t have this problem with CS or CS2.
Thanks again folks…
Michael
First of all, you need to hardware calibrate your screen especially if it’s an LCD – y’know – 6500K Gamma 2.2, 110-120 cd/m2 luminence. The software you use for monitor calibration will load the monitor profile it makes into your system where Ps will pick it up and use that in conjunction with your working space to display correctly.
"If I would only see the effects in non color-managed apps, then why do I see it in PS (a color-managed app)."
If you have properly calibrated your screen and have a good and valid monitor profile that Ps is using, then what you’re seeing in Ps is correct, even if you think it isn’t. If LR and Ps are not in sync visually then you need to make sure that they are both using the same monitor profile. If they are they will display the same.
You still need to convert your web graphics to sRGB and realize that when you look at them in a non color managed app AND you have a wider than sRGB monitor, there is going to be a difference. Until your other apps start being able to use both a monitor profile and a working space profile, that’s just the way it’s going to be. It’s not Photoshop’s fault here. Complain to Microsoft or whoever wrote your non color managed apps or start using Safari or Firefox with CM enabled, and start embedding your working space in your files.
If you want to see what your images will look like in a non-colour managed browser, (after you have setup your colour settings properly, calibrated, with a proper RGB working space), you can go into View-Proof Setup-Custom, select your current monitor profile as the "device to simulate" with "preserve RGB numbers" checked on. This will make photoshop simulate what the colours will look like on your monitor in your non-colour managed apps. Then you can press ctrl-y to toggle that view between simulating your monitor and the actual RGB working space you are using.
