Well yes, PL’s internal workspace is AdobeRGB
(instead of ProPhoto, ROMM RGB from AP or MelissaRGB from LR)
and set like
makes use of the current display device profile.
With that, a screen capable (or set) to render sRGB colour space displays the correct colour
(within its limits), but the file’s colour space (e.g. AdobeRGB) is not affected.
Colour conversion on export (e.g. from AdobeRGB to sRGB) is done with rendering intent perceptive
→ Add soft proofing to Photolab - #16 by sankos
As said before, PL does not support Lab color space.
In Lab colour space → https://www.xrite.com/de/blog/lab-color-space
the Lightness “L” is separately handled from the colour,
which is represented by “a” for Green (-) → Red (+) and “b” for Blue (-) → Yellow (+) values.
Like this, several programs (AP, PS …) e.g. allow to only sharpen the Lightness information
and adjust the colour(s) separately, the colours without being affected by a contrast curve
OR equalizing colour & softening colour noise without affecting the sharpness / texture (the information from the Lightness channel) OR …
in general (short version !)
-
editing should be done with a 16bit file to avoid (reduce) tonal breakdown
-
exporting for web should be done into sRGB colour space
avoiding / reducing problems with the colour renditon
(untagged files are quite often handled as sRGB) -
the appropriate colour space for printing depends on
-
- if you print yourself → sRGB / AdobeRGB / 8bit / 16bit
-
- the service provider’s information, commonly → sRGB
-
from a somewhat brutal but true saying:
“When you dont’t know (better), keep with sRGB.”
some simple to follow explanations (unfortunately in German only)
→ Interessantes rund um die Foto- und Videotechnik - fotovideotec.de
