Export for Web: sRGB or P3?

Viewing 4 posts - 13 through 16 (of 16 total)
  • Author
    Topic: Export for Web: sRGB or P3? Read 24361 Times
  • John Sadowsky
    John Sadowsky
    Participant
    Posts: 169
    Export for Web: sRGB or P3?
    on: April 25, 2020 at 11:02 pm

    This was an oops – webmaster, please delete this post.

    JSS

    Andrew Rodney
    Andrew Rodney
    Participant
    Posts: 294
    Re: Export for Web: sRGB or P3?
    Reply #1 on: April 26, 2020 at 2:26 pm

    But people are viewing this outside of color management, then DCI-P3 will look butt ugly on an sRGB gamut display. Because of a lack of color management.

    I’m not so sure about that. Display-P3 has the same D65 white-point as sRGB. Yes, an image in Display-P3 viewed without CM (as if it were sRGB) that will desaturate the reds and greens (blue is the same as sRGB), but the whites will be correct so there won’t be an apparent color cast. I think that was Apple’s intent when they defined Display-P3 (as opposed to DCI-P3).

    When you actually test this, you’ll be more sure ?. The facts are simple: with color management, ALL the attributes of the Working Space and display profile are used to produce a preview. Without color management the RGB values are sent directly to the display.

    The video referenced DOES show the effect of viewing sRGB without color management on a wide gamut display. IT IS UGLY and previews incorrectly. Just like Adobe RGB (1998) or DCI-P3 previews ugly without color management on an sRGB gamut display without color management.

    And if you own Photoshop, it’s easy to use its View>Proof Setup> Legacy Macintosh, or Internet Standard to soft proof how images appear without color management to again see how ugly this is and to insure you understanding what I wrote.

    Bottom line: With color management, ANY and all tagged RGB color spaces will preview the same on your system and ‘correctly‘ (the qualities of the display calibration and it’s profile of course play a role). In Photoshop and a web browser that is color managed, and all other properly color managed applications, they match.

    Without color management, none of the above is guaranteed nor should be expected. It doesn’t matter if your display has a DCI-P3 color gamut, an sRGB color gamut, an Adobe RGB (1998) color gamut nor what the white point is. With color management = correct preview. Without color management, incorrect color preview. 

    The display profile, it’s color space (gamut, white point etc) is utterly divorced from the profile of the Working Space by design. Display Using Monitor Compensation is used to produce this color managed preview. No matter the color gamut of the display.

     What devices/apps/browsers don’t have CM anymore? 

    Well Edge Chromium color management is broken depending on the type of display profile used, some versions of FireFox have no color management on by default, and there are other browsers that have NO color management whatsoever. There is also the issue of what a browser does (assumes) if it tries to preview an image that has NO embedded profile or EXIF data defining the scale of the RGB values.

    https://graphicartsmag.com/articles/2019/11/stabilizing-colour-management-with-varying-web-browsers/

    Don’t ASSUME all viewers on the web have color managed browsers.

    Don’t ASSUME all viewers on the web have calibrated and profiled their displays.

    Don’t ASSUME all images have embedded profiles or are in sRGB.

    The issue is whether or not the viewing browser is color-managed

    No, that IS the issue, always.

    Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

    • This reply was modified 2 years, 7 months ago by Andrew Rodney.
    Andrew Rodney
    Andrew Rodney
    Participant
    Posts: 294
    Re: Export for Web: sRGB or P3?
    Reply #2 on: April 26, 2020 at 2:31 pm

    Firefox was apparently the first to employ CM, and before 2015 most browsers did not have

    No. Safari on Mac has been color managed from day one. And that day was January 7, 2003!

    Worse, FireFox when it finally did get color management had that OFF by default and turning color management on was about as non intuitive as anyone could possibly design in a product.

    https://cameratico.com/guides/firefox-color-management/

    • Enable it on the Firefox advanced configuration
    • Type in about:config on your Firefox address bar.
    • Use the filter field to search for color_management.
    • Update the following fields:
    • gfx.color_management.mode
    • Set to 1 to enable color management for all rendered graphics.
    • The default value of 2 enables color management only for tagged images, so all page elements and untagged images are rendered in the monitor full color gamut, leading to oversaturated colors.
    • gfx.color_management.enablev4
    • Set to true to enable ICC v4 profile support.
    • There’s no need to specify the monitor ICC profile manually as it’s read automatically from the operating system.
    • Restart Firefox.

    Pathetic but that’s the way to do it.

    Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

    Andrew Rodney
    Andrew Rodney
    Participant
    Posts: 294
    Re: Export for Web: sRGB or P3?
    Reply #3 on: April 26, 2020 at 2:48 pm

    One would assume the same for Android apps.

    No need to assume:

    https://developer.android.com/training/wide-color-gamut

    Android 8.0 (API level 26) introduced color management support for additional color spaces besides standard RGB (sRGB) for rendering graphics on devices with compatible displays.

    And that happened THIS year. Kind of sad but true.

    Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Viewing 4 posts - 13 through 16 (of 16 total)
  • You must be logged in to reply to this topic.