Soft Proofing

[John-M (Melbourne, Australia - Win10)]

@Wolfgang

Now, with DxO using an ‘automated’ not user configurable rendering for export (in case of sRGB / AdobeRGB / DisplayP3 profiles), one might think to get a visual discrepancy in softproof … from choosing the fixed rendering intents perceptual or relative colorimetric.
– But that is not the case. The same ‘automated’ rendering is applied to the softproof so that it looks identical to the equivalent export.
To check yourself, you can export from the softproof copy (“same as softproof”) and compare the softproof version to its output.

Spot on

@George

Softproofing is meant to see how an image is reproduced on another device, not connected to my pc

Actually, the implication of the behaviour that Wolfgang describes above results in that not being so;

• PLv6 is applying an additional, automated “Protect Saturated Colors” algorithm (PSCA) when we Export-to-Disk … Note: This is NOT related to the same-named slider with Color Rendering.

• Therefore, even if we’re doing everything on the same sRGB monitor, including Exporting-to-Disk via ICC Profile = sRGB, it is always advisable to Soft Proof if you’re expecting WYS-is-always-WYG.

See more details on this on my post just above this one.

Also see here for attempt by @KeithRJ & me (with help from others too) to map PLv6’s color management pipeline. Note, tho, that it’s a Work-in-Progress.

Regards, John M