What OS are you using?
Did you set the color profile for your monitor in the color settings of your OS, and which profile did you select?
Since you are saying that your monitor is working in sRGB, you did not calibrate it, right?
Windows 7 64 bit ...
Yes, I did not calibrate my display,
Windows uses sRGB as a default space.
Windows uses sRGB as a default space.
Is it actually set to be the profile in your monitor's properties pane? Look in the properties as oftentimes the operating system actually assigns a profile that came from a driver. Also, what the out-of-monitor gamut shows you is not whether the color in the original file is out of gamut but whether the color after conversion to the target is out of gamut. So in this case you don't expect it to become purple.
Hi Jao ... can you please explain more what you mean by "whether the color after conversion to the target is out of gamut."?
It shows you (or is supposed to) whether the color that is displayed is out of gamut. Some profile conversions can have significant color changes. For example when you use perceptual rendering intent the color can change, or when the color is out of gamut in the destination profile, it can bring it into the gamut of the display profile. Here is an example.
As you can see in the sRGB proof it shows nothing out of the display gamut, while in the adobeRGB proof it shows quite a bit (blue and purple). This happens because the sRGB conversion brought the colors inside my display's gamut. adobeRGB is wider than my display in places and some colors can still be out of gamut on my display profile.
So ... maybe wrong ... the monitor gamut warning is not comparing the colors in the file with the display color space directly. I was previously thinking that monitor gamut warning is independent from the selected destination profile.
But, as you show, it is related with the selected destination profile in soft proofing.
Let me summarize what I understood now ... the colors in the file are first converted to the selected destination profile and then the monitor gamut warning is showing those converted colors which are outside my display color space.
That is ... if I choose AdobeRGB as the destination profile in soft proofing ... the color values in my file are first converted to AdobeRGB and if the AdobeRGB values of my colors are outside the sRGB (let's say it is my display profile), the monitor gamut warning paint blue. Right?
Sent from my iPhone
Thank you so much for clarifying it for me.
I don't have much time for playing with Lr in these days ... so I could not check it.
Today I can look at it more closely, but the result is negative.
Are you using Lightroom CC?
Unfortunately, monitor gamut warning is not working on my PC ... Lightroom CC, Windows 7 - 64.
Even with fully saturated images, I can not get any OOG warning for my monitor.
I have not seen any issues with the LR 6/CC Soft Proof gamut warning on my Windows 7 system.
There is a known problem related to the Soft Proof RGB values that show in the Histogram, which I reported here:
Destination gamut warning is ok, but I can not get any warning for the monitor ... even with the most saturated images.
Ok now ... I've just closed GPU usage from the preferences window.
And now my monitor gamut warning is working.
Alper Tonga wrote:
As far as I know, monitor gamut warning (blue) shows the colors that are inside the file but outside the display color space (the profile of my computer display) ... and the destination gamut warning (red) shows the colors that are inside the file but outside the destination color space (the printer profile selected).
If the information given above is correct ... let me ask the following question.
It's not correct, hasn't been for some time in both LR and (depending on the OOG) Photoshop. You can load an image in say sRGB, ask to soft proof to sRGB and load the overlay yet see OOG colors. That shouldn't happen. GPU in LR6 has messed up a lot of areas as well, I'm also seeing issues with numbers being different on the same image in LR5 versus LR6. So there's plenty of bugs that haven't been squashed.
Thank you Andrew for further clarification.