The (main) difference in our version is that we’ve tried to make it specific to our understanding of PL’s unique implementation of the CM pipeline - especially with regard to its proprietary “Protect Saturated Colors Algorithm” (PSCA), which has some specific implications for PLv6 users.
We decided there was only so much that could be included in one diagram - and we didn’t want it to become so complicated that it couldn’t be readily understood. For simplicity, you can envisage “convert to monitor profile” as being part of “#7 Convert to soft-proof profile” … the absolute completeness of which will depend on whether or not the monitor is capable of rendering the specified soft-proof target.
For example, I can see 4 distinct scenarios for soft-proofing;
-
Using, say, a P3-capable monitor - and Soft Proofing for an sRGB monitor
– In this case the P3 monitor IS able to accurately simulate the sRGB rendition -
Using, say, an sRGB-capable monitor - and Soft Proofing for a P3 monitor
– In this case the sRGB monitor cannot simulate the P3 rendition - so, instead, we need to review the OoG warnings instead (as made available as toggle-buttons on the Histogram) -
Using, say, an sRGB-capable monitor - and Soft Proofing for an sRGB monitor
– Counter-intuitively, soft-proofing IS still advised in this case … because; PSCA (See the diagram) ! -
Using any-capable monitor - and soft-proofing for output to a printer
— This is the classic and obvious purpose of soft-proofing.
John M