@Hugo I have repeated a slightly different set of tests so
Image only in PL5 and PL6 directories
Discover and apply the preset ‘1-Portrait - Standard’ in PL5 and PL6 to the original image
Check the Colour Rendering (CR) and Export i.e. ‘Generic Rendering - DxO Portrait’
Disable Colour rendering and export
Compare 4 images and attempt to spot any differences (zoom used to show the differences, if any that appear to be occurring)
Can you see any difference and should there be any difference!? Please note that this is not taking any image data from PL5 to PL6 this is applying the “locked” presets from the two release to two images isolated in directories (actually from two machines)
PL5 versus PL6 after the application of a specific standard preset:-
The “standard” “locked” DxO presets are not the same between DxPL5 and DxPL6, or they don’t exist in 6 (because mine might have come solely from a migration from 5 to 6) or they don’t give the same results or …
The PL6 image created from a PL5 DOP is not the same when exported from PL6
I need to lie down and will re-review tomorrow!!??
I made some time to test one of my images just now in PL4, PL5, and PL6. First, with the No Corrections preset, but using the Legacy working color space and Soft Proofing for sRGB in PL6, I see no noticeable differences. With Color Rendering on and set to “DxO camera profile (E-M10)” (“Camera default rendering” in PL4), there is a bit of a loss of saturation in all three, and again they are all equal.
Repeating this test with the image of the model in the top post, there are again no differences. When I change the color rendering in all three PLs to DxO Portrait, the situation changes. Now PL6 has muted colors. The same thing happens with my own test image. So that’s a major cause of the problem, and hopefully the only cause.
This isn’t the only color rendering option that’s broken in PL6, but I don’t believe there are many.
I repeated my test by taking Hugo’s DOP and applying the DOP to some of my images but then went back to Hugo’s model images because the comparisons are easier. If the Color space is changed to Wide Gamut then the images where PL6 has used the PL5 DOP become closer to the original, arguably slightly better!!
@BHAYT If you swich to Wide Gamut the problem is mostly solved (but there is no portrait rendering in V6). However that is not really the issue. The rendering should be exactly the same in V5 en V6 (legacy mode). If it does not work for portrait rendering, there might be issues in other renderings too.
Although this is might be a minor issue for most users, it is a huge issue for me, since I used the portrait rendering in 99% of my images (model and studio shots)
@Hugo the test with Wide Gamut was just part of a test to see if I could use your DOP on my images, a trick I have used that works on DxPL(Win) and it occurred to me that we had not tested the impact of Wide Gamut. When using my own images on PL5 I was not able to get the ‘DxO portrait’ rendering it simply was not there!? When I used your DOP I was in ‘DxO portrait’ but my own camera rendering was also available!?
So I agree with you that this is a bug but one which might be linked to the introduction of Wide Gamut (!!"??) (or not) and using Wide Gamut might provide a temporary work around. But I would definitely raise the issue as a fault with @DxO_Support-Team
@Joanna that appears to be the case but I am also puzzled by what I think I saw in some of my tests.
Unfortunately I am using two machines, one on PL5 and the other PL6 but sharing directories, each designated to a version of the product and that has been fine but my snapshots are not as well filed as they should be and that has me feeling that 3 screens, 2 machines but only one aging brain is losing contact with reality if you can describe this testing as reality!!
The issue that is puzzling me is
The problem definitely exists and appears to be associated with ‘1 - Portrait - Standard’ and the ‘Rendering’ of ‘DxO Portrait’ that results from using that DxO supplied, “locked” preset in the move from PL5 to PL6 with a PL5 DOP.
I believe I have seen anomalies with other DxO presets?
If I apply the preset to some of my own images in PL5, in order to carry them to PL6 I do not get the ‘DxO Portrait’ ‘Rendering’ I get my camera rendering and things go as they should! Hence, the hacking with the DOP, which worked but the differences were not as obvious as with the picture provided by @Hugo so I reverted to those images rather than using my own!
Applying ‘1 - Portrait - Standard’ to my own image
@Hugo Please raise this fault via the DxO support channels because raising it here gets you opinion, advice and “advice” and confirmation but I am simply not sure anyone in DxO is monitoring the forum anymore, let alone actually preparing to react!?
During Beta testing, the issue that making any change to existing customer presets was to be avoided as much as possible seemed to be accepted by DxO and the ‘Wide Gamut’ feature was made optional but something seems to have slipped through.
Whenever new features are provided, particularly when they involve image editing, it must be possible for the user to continue with the “legacy” features wherever possible until they decide to adopt the “new”, or not, as they choose.
Not that all developers of image editing software even keep the interface the same going from one release to the next!!
This is not a perfectly black image, which means that differences exist… I still needed the >10 stop (roughly 1000x) enhancement to make the differences visible. A difference of 1/1000 cannot be distinguished by an average human eye/brain, that combo is good for about 1/100 only.
Images that have been migrated from DPL5 to DPL 6 and exported without further adjustments can be identical, except images containing fairly saturated colours that fall between Adobe and DxO Wide gamuts. Hugo’s image has no such colours.
I tried different target profiles in soft proofing and found that AdobeRGB and SP (off) produce identical results, no matter if I set perceptive or relative rendering intent (which might be meant to act on paper simulation only)
Export was done with ICC = “As shot” in all cases
Tested on macOS Monterey 12.6.1 in iMac 2019.
I could also test on a M1 MacBook Air running Ventura, but I don’t feel like it right now.
whereas, when Exporting-to-Disk, the PSCA is always applied.
Similarly, the “Intent” setting;
I agree with your suggestion that it relates only to the “Simulate paper & ink” setting
– That is, presumably - - we’ll know for sure “soon” !
– The current UI layout for this setting is confusing (I’m guessing that will change … hopefully !)
Does absolutely nothing in the current version of PLv6 … instead, the concept of “intent” is handled by the Protect Saturated Colors Algorithm (See reference above).
So, the result may have been exported with an AdobeRGB profile (if that was the camera setting).