I have been struggling with the following for a long time, asked many people, posted many queries, yet never received a good answer. I just discovered this forum and hope that someone here can help.
I made a profile for my monitor using the EyeOne Display 2 device. My understanding is that this profile is used to modify my video card’s lookup table at boot time. It is system-wide and applies to all images displayed by all applications, color-managed (Lightroom, Photoshop) or not (most browsers, IrfanView).
I understand further that color-managed applications consider the source profile, the profile that is included in an image, if one is available. That makes sense.
However, I observe that color-managed applications are also considering the monitor profile. That is, the color displayed on my monitor by a color-managed applications changes as I change the monitor profile. I’m doing this change after boot time such that the LUT is not changed, only the monitor profile considered by the application.
Why is this? Why would a color-managed application look at the monitor profile when that profile has already been applied to the image in the form of a LUT correction? It looks like double profiling to me.
A brief background explanation… I came to observe this because a defect in my EyeOne colorimeter produced a defective monitor profile that had a strongly exaggerated color shift. The shift before the defect occurred was far less and I never noticed the difference between the images displayed by color-managed applications and non-color managed ones. But with the defect the shift was pronounced and led me to track down the source, which I discovered was a bogus monitor profile. Observing the colors displayed by color-managed apps as I moved the defective profile in and out confirmed the cause.
The only thing I can come up with is that I am indeed applying the monitor profile twice and that I should not be using the EyeOne software at boot time to modify the LUT when I’m using it with color-managed apps. I’m afraid that that this not a satisfying explanation because I can’t understand why the EyeOne, a reputable device from a reputable company, would create a situation that, by default, results in double profiling.