PLv7: Wide Gamut Color Space - Soft Proofing, Export to Disk, NikCollection

[Wolfgang ([ Win10, PL+VP+FP, Nik7 / 3.3 ])]

@Klick

@John-M

BUT, I’m not sure that the Nik tools can handle the WGCS (which is unique to pure-DxO tools - such as PhotoLab). I am confident, tho, that Nik tools can handle AdobeRGB - which is why I exchange files with Nik tools via that ICC Profile.

That is a justified thought. Transferring an image to the NikCollection in AdobeRGB should not cause any “damage”, as we only had a maximum of AdobeRGB available up to PLv5.

something to consider …

DxO’s WGCS is their own ‘spawn’ (for additional input …), but not a widely used color space. Returning to PL with such an intermediate Tiff file doesn’t (shouldn’t) cause any problem as long you don’t use it “outside” PL ( → add a descriptive suffix as a reminder).

Otherwise you might want to use Rec. 2020 or ProPhoto instead, while AdobeRGB does not fully cover P3, but is suitable for printing.
[ note – those paper profiles (2nd graph) reflect the color range of my paper & printer ]

@Klick

@John-M

I guess the answer is that “Average Joe” who is not aware of Soft Proofing requirements also probably doesn’t notice differences between what is seen within PL and what he gets in his exported image (!)

One thing, however, that I only became aware of through the discussion here:
Suppose I work with the WGCS and have soft proofing permanently activated.
I set sRGB IEC61966-2.1 as the profile for soft proofing.
This allows me to see on the screen what should also be visible on the Internet, as in my case.
Under these circumstances, what is the advantage of working in WGCS?
I mean, even if the WGCS can display so many and very saturated colors, I can’t see them due to the permanently switched on soft proofing (with sRGB IEC61966-2.1, for example), because this limits the colors. So I could set the legacy color space right away.
Where is my fallacy?

Having Soft Proofing with sRGB IEC61966-2.1 permanently enabled can be a “solution” for sRGB users (screen, output…) and make their lives “easier”. Also, they could use the legacy color space, as long DxO will support it, and don’t mind a couple of disadvantages (has been discussed somewhere – just don’t remember in detail).

But the sRGB/Legacy color space isn’t for everyone. You may want to take advantage of the larger color space (like your P3 capable screen) or print (which is what I do) and see in advance …
The real problem for sRGB users is that they can’t “see better” and therefore have difficulty following what’s happening when using DxO WGCS as their internal color space.
Monitor & destination gamut warnings are helpful tools, but they cannot replace the impression you get when you are on a wider gamut screen and switching between the (VC) versions.