Major glitch in DxO PL 6.3.0

Interesting (and annoying) glitch that appears to coincide with the newest update for DXO PL 6 (6.3.0). When imported from Lightroom Classic, the file exhibits extreme barrel distortion, so much so it actually leaves black in the corners of the DXO workspace. This does not happen when the same file is imported into DXO 5.5.0 (second pic), nor is it observed in original RAW file in LR Classic. However, when the file is exported from DXO 6.3.0. as a DNG into LR, the distortion (including the black workspace in the corners) is preserved in the export. It does not matter what NR module is being used, the distortion is present upon import into DXO. I literally just updated it, and did not have this problem at all in the previous update. Anyone else experiencing this?

RAW file is from a Sony A1 with current firmware (1.31


Welcome to the forum @polylepis

Showing black corners is a new feature of DPL 6.3. The change is documented in the release notes.

New features
• The paper & ink simulation for Soft Proofing is now available
• The DxO Wide Gamut working color space is now available for RGB images
• A new workflow to download multiple optic modules (modules without ambiguities) has been implemented
• The global value for Lens Sharpness is now set to 1 by default
:+1: It’s now possible to see the whole image without constraint when using the crop tool
• The shortcuts for size/feathering modifiers have been harmonized between ReTouch (previously “RepairTool”) and Local Adjustments
• Preferences regarding Metadata synchronization are now available in the “Metadata” tab of the PhotoLab settings
• A new filtering option has been added for the filmstrip: “Modified since last processing”
• Various updates for the filmstrip filtering options (harmonization with Windows version)
• The slider “Preserve color details” is now displayed in the advanced settings of the soft proofing palette

Seeing the whole image helps to decide, where to crop, specially if a lens exhibits extreme distortions. I like this new feature, but YMMV…


@polylepis polylepis
… and as already said (elsewhere), button “constrain to image” is enabled by default (according to the old behavior).
You should not have seen this phenomenon.


I’m seeing the same behaviour from PL 6.3.0 build 44 after install (I have installed fresh version downloaded from DXO dashboard today).
Effect is visible in PhotoLibrary and Customize views
Vignetting, Lens Sharpness, Chromatic Aberration and Distortion are all enabled on launch.

Further to the above. Simply (and fairly obviously) disabling Distortion gets rid of the black areas, but leave s a distorted view of the image as can be observed by referring to the vertical column to the right in the attached images.
Cropping to corrrect the distortion reduces the pixel dimensions of the image.

Distortion ON

Distortion ON + Constrain to image
and the Crop tool

Crop / Correction Auto based … + Distortion ON … behaving accordingly

please note

The preset “1 - DxO Standard” contains Crop / Correction Auto based on …

When applied to a newly discovered pic (= my standard setting for raw-files)
the pic gets croped automatically, the Crop tool turns off and the black edges are not shown.

1 Like

Can confirm this. Same problem on both Intel and M2 Macs. If the ‘constrain by default’ option is supposed to be active - it isn’t. Normally, I have my RAW imports set to ‘optical corrections only’. Now, that produces these distorted previews. If you change to the ‘DXO Standard’ preset, however, no deformations are seen. Good to have an option to see the full field, but it should not be the default forcing manual cropping every time to fix it.

1 Like

Thanks Andy. I don’t see any difference in behaviour between Standard and Optical Corrections Only presets, but the Constrain to image box seems as though it’s meant to be on when by default. It’s no help to me if I have to pre-process all my images before reviewing them and then having all the .dop files in my folders to manage.
I’ve raised a ticket with support and hopefully there’ll be an update to address the problem - it’s not the full 6.3.1 update after all. I wouldn’t have installed it if the launch splash screen hadn’t indicated that it was there.

Thanks for the input, Wolfgang. I’ve raised a ticket with support.


It is definitely not a bug. All this new feature does is give you a new option to constrain or not constrain the image when Distortion correction is selected. Previously it was automatically constrained. Just leave it set on all the time if you don’t want to see the actual effect of applying the distortion correction to the original image without the crop.



Thanks Mark. The thing is that constrain is not enabled by default. It has to be enabled for every image, either one st s time or by a bulk action when opening images for processing.

It is on by default on the Windows version. What startup preset are you using.



I have a preset based upon the camera body I am using with constrain on by default and lens correction, gamut etc, so I have one for my 80D and one for my R7 and simply apply it to all images in the folder taken with that camera.

With the preset, everything is as I want them, regardless of the original on/off default that DxO decides upon.

1 Like

You can simply edit your default preset so that it includes “Constrain to image” in the active state. :smiley:

1 Like

By default, all DxO-provided presets do NOT default to “Constrain to Image” … which was an unfortunate implementation decision, I reckon, 'cos now behaviour is different by default.
But, there is a fix …

And here are the steps to follow to achieve just that;

  1. Open an Image that PL has NOT encountered before … so that settings for it are not already stored somewhere.

  2. Apply preset: 1 - DxO Standard.

  3. Activate the Geometry tab - go to the Distortion tool - reveal Advanced settings - and tick/check the “Constrain to image” option (plus Keep Aspect Ratio - if that’s what you want. If not sure, try it !)

  4. While you’re at it, set any other options you’d like to see have different defaults from DxO Standard … such as, say, your preferred setting for Clear View … etc.

  5. Go to menu item “Image” - and select: image - Name it as required.

  6. Select menu item “Edit \ Preferences” - and specify that you want your custom default preset (as created above) to be used instead of the default; DxO Standard.

For example: image

If you already have a custom default preset, you can update it by applying your preset, instead of 1 - DxO Standard, in step #2 above

John M

1 Like

I found the opposite setting to that, Mark … = OFF in all DxO-provided preset files (Windows version)

Note that it is a little confusing, internally - the OFF setting (as reflected by the UI) is recorded in a Preset as; image … = OFF in the UI !

Edit: There’s also another entry I hadn’t noticed before: image
… … Does anyone have any suggestion as to what this might do ?


PS. I wouldn’t categorise this as a “Major glitch” … more like a minor annoyance !

1 Like

Thanks John. That’s very helpful and appreciated.

1 Like

Thanks to all responders for the advice and guidance.
I’ve created a preset that preserves my original preference for ‘Optical corrections only’ + ‘Constrain to image’ which gives me the desired outcome.
I had never dabbled with the presets before and wouldn’t have thought to go there in search of a solution.

so, not a major glitch then :wink:

1 Like

Just for clarity, Chuck - I was not the original poster, who used that title.
I do believe there is something counterintuitive in the way DXO have decided to set the default behaviour for this feature for Mac users.
I’m also glad that there is a community of users who help out so readily when a problem is raised.