I calibrated my mac and have a color profile stored on it.
My impression was that this profile was used by the GPU as part of a lookup table for all video sent to the screen, but perhaps I am mistaken here.
Are you saying that if color management is turned off in PM it will cause PM to bypass this calibration color profile and write directly to the screen?
Yes, that is correct.
Kirk,
I just did an experiment to test this and it does not seem to be behaving as you described.
What I did was to look at a photo preview in PM who's colorspace is sRGB, then I toggle the PM color management on/off using the "C" key. I observe a big difference in color saturation.
Then I open the Apple system preferences and switch the display profile back and forth between two different profiles. In each case I clearly observe the image colors changing whether or not PM color management is on or off.
So doesn't this mean that the image from PM is still having my display calibration profile applied to it even when PM color management is off? I thought you said it was being bypassed.
What profile are you assigning to your monitor? Which two profiles?
-Kirk
The monitor profiles I am talking about were obtained by hardware calibration with an EyeOne colorimeter. They can be named anything I like. The default names are something like Monitor_4_24_09-1 and Monitor_4_21_09-1 where the name is comprised of the date created.
I also tried the other profiles listed like the default imac profile that came from Apple (Which has a 1.8 gamma btw). The Profiles I usually use are calibrated to have 2.2 gamma and 6500K target white.
My point is that any monitor profile change in the Apple Display Preferences panel causes the displayed picture to change, whether PM has color management on or off.
So it appears that toggling PM color management has no impact on whether or not the color sync monitor profile gets used. It is always used.
OK, I just wanted to make sure you weren't switching between some other profiles like sRGB or Adobe RGB (1998). Do you have Photoshop? If so, do your images look correct when color managed in Photoshop?
-Kirk
I don't have Photoshop on this computer. I could add it if necessary to get to the bottom of this.
Another thing I noticed.
I was experimenting with the "extract embedded JPEGs" feature of PM. One of my favorites btw.
During the extraction process there is a pop up option that askes if I want to embed the ICC profile. As we discussed yesterday this is referring to the colorspace of the JPEG rather than the display profile.
I wanted to see what difference it made if I chose this option.
I ingested a NEF file into PM and noticed from the info viewer (and it's variables whose names I forget now) that PM says its profile was Nikon sRGB (embedded). It must be that NX embedded the nikon sRGB profile in the JPEG preview I assume. I did not mess with the colorspace option at all in NX on this one. Changed nothing but exposure from the camera NEF and resaved.
Now I extracted the JPEG from this RAW file with the option "embed ICC profile" selected. (Call this file1.jpg)
Then I extracted the JPEG from this file again without the "embed ICC profile" option selected (Call this file2.jpg)
I them loaded file1.jpg and file2.jpg into PM to see what profiles they each had.
file1.jpg was still Nikon sRGB (embedded), but file2.jpg was declared "undefined".
Interesting. I thought you said the colorspace profile was conveyed in the EXIF data and that the embedding step was unnecessary. Maybe I am confused.
Anyway, If I don't choose embed the file appears to be in an undefined colorspace in PM. Interestingly, if I toggle PM color management now while observing these two jpgs, the color on file1.jpg changes (as always) while the color on file2.jpg remains the same.
My conclusion (so far) from all this experimenting is that toggling color management on/off only tells PM whether or not to pay attention to the embedded color profile in the JPEG, and that if it is set to "off" it uses the same colorspace as it applies to "undefined" photos. And, this space, whatever it is, is definitely not sRGB. Probably it is just sending the digital RBG pixel values directly to the video processor with no conversion.
Let me ask you this. If you look at sRGB images in PM do they always look more saturated with color management "off" than "on"? I notice the reverse is true for aRGB, that is, more saturated with color management "on" than "off", but this made sense to me since the Adobe gamut is larger, and I assumed color management "off" was causing them to be viewed in sRGB space, which naturally would make them less saturated, but I've demonstrated this is not the default space for CM "off".