PL6 - Color Rendering "DXO Portrait" changed

DxO PhotoLab
1

Hi,

I recognized that Color Rendering “DXO Portrait” on PL6 is much more muted / less contrasty than on PL5. Is this on purpose?
When I apply “DXO Portrait” on PL6 the images always look “foggy”

Just as quick comparison a crop of same image having the same preset applied “Portrait - Standard”.
PL5:

PL5_Portrait
PL5_Portrait978×692 243 KB

PL6:

PL6_Portrait
PL6_Portrait1003×672 179 KB

Histograms:
PL5:
PL5_Portrait_Histogram

PL6:
PL6_Portrait_Histogram

kind regards
Sebastian

2

@abgestumpft The same as discussed in this topic perhaps In V5 processed images look different in V6?

PS:- It is very useful if as part of the post or part of your name, you include the platform you are using (Windows or Mac) because there can be differences between them and where a workaround might be possible that might vary between platforms, plus if another user wants to try to reproduce your problem it is useful to know on which platform the problem was encountered!

PPS:- and you might find PLv6: Color Rendering observations interesting.

Regards

Bryan

3

DPL6 introduces the “DxO Wide Gamut” working colour space. Try the “Legacy” colour space and most colours and presets return to what they were pre-DPL6.

4

Thanks Bryan and platypus for your replies!
The topic linked by Bryan is the same.

I did some quick testing and what I found out so far is:

  1. With all other (non-portrait) presets the color space is set to “DxO Wide Gamut” and looking similar/same to PL5.
  2. The DXO Portrait Presets (both built in and my personal ones using color rendering “DxO Portrait”) use Color Space “Classic (Legacy)” and then look washed out. When changing this to “DxO Wide Gamut” it will then look very similar to the DXO PL5 Portrait setting.

I will go through the two threads you linked in detail later…

1 Like
5

A correction: when I apply “DXO Portrait” Color rendering and then change color space to “DxO Wide Gamut” the color rendering is automatically changed to “Neutral Color”.

7

@abgestumpft Hello, this problem will bee fixed in January release. Thank you for your understanding

5 Likes
8

Hi @Cecile-C
thanks for the confirmation that this a known problem and will be fixed.

1 Like