John Wheeler Offline Upload & Sell: Off
|
p.2 #11 · Color discrepancies from Lightroom to Flickr, Imgur, Windows Photos, firefox, and chrome/brave browsers. | |
ruthenium wrote:
Yesterday, I bought these roses for my wife - killing two birds with one stone, so to speak - to make my wife happy on the one hand, and to have something to photograph on a gloomy day like today, on the other hand.
Below, I uploaded two pairs of jpegs.
In each pair,
the 1st jpeg was exported as Display P3, and
the 2nd was exported with the sRGB profile.
The first pair was exported from DxO Photolab 9.
The second pair was exported from Capture One.
There are some inevitable differences between Capture One and Photolab, because of the different color profiles.
The only argument in favour of using the smaller sRGB profile, where some of the visible vibrant colors are clipped and appear washed out, is that of the wide compatibility of sRGB.
I don't believe in this argument. In fact I believe that it is the Display P3 profile that is more broadly compatible with the modern devices. For example, all modern Apple devices support Display P3, and using sRGB instead means degrading the image quality for Mac and iPhone users. I use a MBP for photography, whereas my Windows laptop is for all work-related uses. Whereas I understand that not every Windows jpeg viewer or browser might be supporting Display P3, I have not seen a case when a jpeg exported with the Display P3 profile was displayed in Windows in a way that looked worse(!) than the same image exported as sRGB.
Thus, I am interested in the experience of FMers. Particularly, I wonder if you happen to see any detrimental effect of the Display P3 in your browser or jpeg viewer (feel free to download these images). That is if there is a browser or jpeg viewer where the sRGB jpegs display better image quality, and where the image quality of the Display P3 jpegs is degraded to make them look wrong or poor vs. the sRGB.
...Show more →
Hi @ruthenium
As an interesting twist, your middle image from Photolab 9 is created using sRGB color numbers but does not contain the sRGB profile. It is my understanding that Photolab does not embed the sRGB profile (it embeds all other profiles) because, as the industry-standard default, embedding the sRGB profile is unnecessary. I am unaware of an option to force Photolab to embed the sRGB profile. I don't use Photolab, so this is just my understanding.
As such, if I have Photoshop Color Settings set to Working Space of P3, and the management policy to convert incoming images to P3 (the working space), what actually happens is that it leaves the image as Unmanaged, so the sRGB image is displayed, assuming the color numbers are in the P3 space.
Following is the Color Settings for Photoshop:

Viewing the image in Photoshop with those Color Settings and the image is oversaturated:

If I force the sRGB profile to be embedded, then you get this image:

I know this does not provide and answer to have an image in P3 and does it cause a problem, yet this helps demonstrate the problem you can have it the profile is not embedded
John Wheeler
|