Just calibrated my monitor. Now I have colorspace issues.

Dick, getting back to your original calibration.... I would not have chosen the EyeOne Display2 for calibrating the wide gamut HP monitor. I would have gone with the Spyder3 Elite v.4 or the X-Rite Colormunki.

Yes, NEC has a specially tuned Display2 sensor as part of its Spectraview II system. But when used with a non-NEC monitor, it behaves as a standard Display2 puck. But you don't have an NEC Spectraview monitor and you are using a standard X-Rite puck, so this side note is moot and irrelevant.

There does seem to be much confusion here. Profiles are being thrown around like darts at a dartboard.

Okay lets assume the monitor calibration equipment is in good working order and is spot on when reading the color patches and the provided software generates a solid "monitor" profile. The software places this profile where it is store with others and it is set as the default profile for that monitor. When using a color managed app all you do is make sure is is using the correct monitor profile, the one you just made. That is it. Do not apply this profile to images as it is not meant for images. Now when you open an image in the color managed app what you see is the accurate color, if within range of the monitor.

Color space! 99+% of the time sRGB Will be the final output space. We may work on images in the aRGB or pro photo space but when we finish and convert to sRGB the rendering intent used only changes the out of gamut colors to fit the space, hopefully in a pleasing way to the destination space. If you embed a working color space into an image that image should look very close to the same on all color managed devices/apps. To be on the safe side of things I try to rember to embed sRGB into all images that are web bound because todays software is changing and the image will always look okay on non calibrated equipment, maybe not correct but okay.

What is a "custom" ICC profile? Only a set of corrections for ***1*** device or paper/ink set...

I'm sorry I am not the best to try to explain things but I felt sort of compelled to try. Slow down a tad and don't try to make more of color management than what it is. Once the light goes on it's really quite simple.

To me this all sounds like what happens to everybody that starts to manage their color. They simply have to get over the old over saturation and too bright of a monitor work flow.

90% of monitors are too bright to produce proper color. It makes it easy to see sure, but not to reproduce a color properly. Most people also turn up the saturation on thier monitors, if the factory has not done it already..... because it is pretty.... but not accurate. After years of this then all of a sudden you try to calibrate and manage the colors ... you will hate what you see for a while. But in fact it is accurate. You may not want to keep it there, and edit accordingly, and there is nothing wrong with that. But at least you are starting at a known point.

Way too many variables.
Also, a consise description of what's happening where would help. Please be specific: The devil is in the details...

Dick Emery wrote in post #11748074
No. It's washed out on the HP wide gamut and looks correct on the Dell.

Both images in LR / Photoshop?
That doesn't fit with your next statement:

Dick Emery wrote in post #11748074
If I open up the sRGB JPG file in Photoshop it looks correct and pretty much exactly the same on both monitors.

This is how it should be.

If LR behaves different from PS, I'd say your display profile isn't good.

Dick Emery wrote in post #11748074
I know this because I have to switch colour profiles for each monitor in PS's color settings option under the Edit menu.

Ehm, No, you don't. The image should have an embedded working space (sRGB, AdobeRGB or ProPhotoRGB). Don't mess around with your monitor profile.
http://www.getcolorman​aged.com …nagement/pscolo​rsettings/

Dick Emery wrote in post #11748074
If I select soft proofing and select monitor RGB it does not change. If I select Internet sRGB however it looks washed out again.

If you go view > proof setup > monitor RGB and the image doesn't change, you either assigned or converted the image to your monitors profile (which you shouldn't) or something else is wrong.
Any image that's in a wider gamut color space then sRGB is supposed to look washed out if you proof for "Windows": In effect, you are assigning sRGB to it.

Dick Emery wrote in post #11748074
I was under the assumption that Photoshop is applying color management and using the display profiles when opening JPG files right?

Right. Nothing you need to do, except have your color settings right.

Dick Emery wrote in post #11748074
If I edit a photo in Photoshop by right clicking in Lightroom it asks me if I want to color manage the photo. If I select no then it looks vibrant.

Sounds right.

Dick Emery wrote in post #11748074
If I choose one of the other options about using embedded or color managed it looks washed out.

Yep.

Dick Emery wrote in post #11748074
Damned confusing. I don't know what is correct anymore lol.

Again: http://www.getcolorman​aged.com …nagement/pscolo​rsettings/

Dick Emery wrote in post #11748074
I think it's probably correct. It's probably just not applying the profile to the JPG since if I open the RAW in Photoshop it does the same thing and asks if I want to use the embedded profile.

You have your working space set to something else then what you set in LR / ACR.

Dick Emery wrote in post #11748074
It also pulls in the .xmp preset settings with it.

Unrelated to the issue at hand. (And I'm not sure what you mean)

Dick Emery wrote in post #11748074
I am guessing that it is something to do with the wide gamut calibration whereby the profile when used in color managed applications aggressively compensates for the wide gamut.

Assuming your profile is correct, I'm still thinking that everything works as it should.

Dick Emery wrote in post #11748074
I read that NEC's wide gamut display aimed at pro's has a specially tweaked version of the i1. Whether that is in the software or in the puck itself I do not know. To my eyes things look fine after calibration on the display itself (if somewhat more saturated than the Dell).

Sounds like it should.

Dick Emery wrote in post #11748074
It's just when color management kicks in using the calibrated profile it's like it sucks too much colour out of things. I may have to rely on the Dell instead as I am beginning to thing that is more accurate oddly enough. Images on the Dell are ricker even though the monitor is not as saturated as the wide gamut HP.

Sounds right. (assuming you are talking about the more saturated colors: Colors that fit inside the Dell's gamut should display the same on both screens.

Dick Emery wrote in post #11748074
BTW I have 3 displays hooked up to compare with. The third display is an HDTV which is also calibrated on the PC outout (single ISFCC profiled HDMI on the plasma HDTV). Dragging Lightroom between the Dell and the HDTV shows no change to any photos colour/hue/levels etc other than the displays themselves having a slight variation.

Good.

Dick Emery wrote in post #11748074
Dragging to the HP and Lightroom changes the photos from a warm orangey hue to a more yellow hue. You actually see Lightroom make the change as if I drag only half way across it's got that same orangey hue on the HP until it's fully dragged across and becomes aware of what display it is now on. The other panels are sRGB of course whilsth the HP being wide gamut is in the Adobe RGB gamut.

Are these "warm orangey" tones within sRGB gamut? Does the entire image change, or just the extreme colors?

It's hard to say what is going on. Basically the image looks correct on the non-wide gamut displays even when color managed. But on the HP it looks washed out with color management and 'correct' like on the other two displays when not color managed. As I said opening the JPG file in PS shows it in that warm non-washed color gamut. If it's using color management in PS against the monitor profile and displaying the sRGB JPG in the monitor's profile why is it looking OK? Surely it should desat if it's using the monitor profile? Which brings me back to Lightroom being the culprit or the profile itself being incorrect based on a wide gamut calibration. I could not afford the colormunki and I heard about issues with the Spyder3 not always having spot on calibration itself (variable pucks). I heard the i1 was better with being less likely to be out of wack but also read they could have issues with wide gamut displays. Perhaps this is what I have hit.

The fact that using when the Dell profile on the HP lightroom shows no desat would seem to indicate this.

Dick Emery wrote in post #11754489
It's hard to say what is going on. Basically the image looks correct on the non-wide gamut displays even when color managed. But on the HP it looks washed out with color management and 'correct' like on the other two displays when not color managed.

This says the custom profile made for the HP is faulty. An sRGB tagged image should look the same on all 3 monitors while opened in a color managed app and in the sRGB working color space.

MrAl wrote in post #11754995
This says the custom profile made for the HP is faulty. An sRGB tagged image should look the same on all 3 monitors while opened in a color managed app and in the sRGB working color space.

You would think this would be the case. I went and downloaded 3 different profiles made for this monitor from TFTCentral. One was calibrated on a Blue Eye Pro. One a i1 Display and one a Spyder3 Elite which was suggested would deal better with a wide gamut display. I loaded each in turn then opened Lightroom to compare the results. Each image varied in hue but the saturation was very similar to what I have been getting. So it must be correct for this display?

Anyhow I am going to strip out all color profiles and start from scratch now as it's got a little confusing and I don't know where I am with my calibrations now. I already cleared out the diaplsy drivers and reinstalled those so the profiles are next.

BTW when I used XNView with color profiles enabled (I tried mine and the TFTCentral profiles) the JPG remained pretty much the same. Going to have to reboot and verify that though just in case all this profile swapping has messed up things.

Light room would not be my first choice for testing sRGB tagged images because it uses Pro Photo color space. This may or may not be okay, I am not an expert but I do try to use logic when trying to track down problems. Once all 3 displays are properly calibrated I would open Photo Shop and set the working color space to sRGB and then compair a known good test image tagged sRGB. That image should look the same on all 3 or any other calibrated display for that matter. I think you have made a good choice starting from sctarch and build a solid foundation to work from. Good luck.

Dick, if you can borrow a Spyder3 puck, download the free trial of ColorEyes Display2 or BasicColor software.

I think I cracked it. I think it might be a bug in the latest Nvidia driver. I've had to roll back to an earlier version as the latest version has a broken control panel (Only shows options to change stereoscopic display settings). I used a different viewer too (Faststone) as XNView seems to have some inconstencies in it's color management. It looks the same on all 3 displays when displaying the JPG color managed. As it should!

I also discovered a bug in the latest Photoshop CS5. If you move it onto another display OR just open it on another display (After closing it on another display it should just open on the same display it was on). It treats the other displays like it's still on the primary display. This can be verified by opening the color settings option on the edit menu. It still shows the primary display profile when set to Monitor RGB. If I change the primary display in Windows display settings and open reopen PS it now shows the profile of the other display. I believe this to be a bug or missing feature in PS (or it could be an issue with UltraMon). Can anyone else verify?

I believe Lightroom has a similar issue in that if I move it to another display or open it on another display if it's not marked as primary then Lightroom just outputs in sRGB colorspace ignoring the monitor profile it is currently displaying on. This would account for the color shifts between displays.

Anyhow I tried my current profile for the HP and some older profiles and Lightroom now correctly shows the right saturation level and hue for Adobe RGB. It's slightly less saturation and a yellower hue than sRGB in the JPG file (Obviously) but is now 100% as it should be.

Phew!

But can someone else confirm the issue whereby PS only displays the primary display profile when set to Monitor RGB under color settings on the edit menu when open on a secondary or tirtiary display? For people that work on multiple calibrated displays on the same PC this is a bit of an issue. Same goes for Lightroom although to a lesser extent.

If you do not experience this issue then I can only assume it's an issue either with my Nvidia drivers and/or UltraMon which I use to manage my displays.

EDIT: This appears to be a known issue from Googling. No fix/workaround though I can find other than setting the secondary or tirtiary display to primary.

See this.
http://www.luminous-landscape.com/forum/in​dex.php?topic=47129.0

I don't know anything about UltraMon but I believe that you are supposed to turn off the Nvidia background monitoring/managing activity.

Just a note. Faststone color manegment does not appear to work. Redid the calibration which was needed on both the Dell and HP and set XNView to color manage with the HP profile. The JPG when color managed matches the image in Lightroom 'exactly'. I am guessing sRGB should only look oversaturated when not color managed and when color managed SHOULD look the same as the source in Lightroom?

Anyhow they match. Faststone with color management on or off makes no difference the the JPG remains saturated (bugged) so am uninstalling that.

Dick Emery wrote in post #11759888
I think I cracked it. I think it might be a bug in the latest Nvidia driver. I've had to roll back to an earlier version as the latest version has a broken control panel (Only shows options to change stereoscopic display settings). I used a different viewer too (Faststone) as XNView seems to have some inconstencies in it's color management. It looks the same on all 3 displays when displaying the JPG color managed. As it should!

Great!

I'll have a look at the rest of your post later

Dick Emery wrote in post #11760705
Just a note. Faststone color manegment does not appear to work. Redid the calibration which was needed on both the Dell and HP and set XNView to color manage with the HP profile. The JPG when color managed matches the image in Lightroom 'exactly'. I am guessing sRGB should only look oversaturated when not color managed and when color managed SHOULD look the same as the source in Lightroom?

Anyhow they match. Faststone with color management on or off makes no difference the the JPG remains saturated (bugged) so am uninstalling that.

v2 or v4 profiles?
Firefox for example won't work with v4. profiles. Maybe Faststone suffers the same issue?

From what I recall reading, V4 profiles are problematic. I continue to use V2