Automatic corrections applied even though "No Correction" preset selected


I’m new to DXO Photolab, trying to make a switch from Lightroom.

One thing I cannot figure out is:

  • When I select a photo in the Customize tab, there will be a short loading after which the program will apply some corrections to the image, resulting in a more contrasty/vibrant photo
  • In the PreferencesCorrection Settings, I have the RAW and RBG images set to “No Correction”, yet some correction is still being applied
  • Are there any other settings I should be aware of that control this behaviour? I would like to start the editing with a “raw”, unedited image

Please let me know if you’ve had similar experience and know how to fully turn off these automatic corrections.

Thank you

1 Like

What you are seeing is not “corrections” but simply the process of demosaïcing. What you see to start with is the JPEG preview, followed by the demosaïced image.

Be assured you are dealing with the RAW image.

Yes, this is how I find photolab demosaicer behave with no correction for my camera. To contrasty, to vibrant, and with some kind of color shift.
I now generally begin with neutral color realistic tonality (in color rendering tab - I have a nikon camera, I don’t know what curve you can use with your body), and tweak the intensity as starting point. Combined with exposure compensation/contrast/selective tone/tone curve/color accentuation help getting better values. I tend to avoid smart lighting because I prefer to choose rather than letting the software to choose for me, but sometime it allows to achieve thing hard to do otherwise.
This is the best I found (for now) to try to keep more natural and subtil color than photolab provides by default.

Have you already opened the photo in PL5 before you changed the preferences to “No Corrections”? If so, PL5’s database will remember the original preset used(DXO Standard is the default). Try putting the photo into a new folder that PL5 has never seen before(Inkheart test folder or whatever) using File Explorer and then restart PL5 and point to the new folder to open the photo. If this doesn’t work, you may have to delete the database. Please remember to back-up the database first.


Or create an empty preset and apply it. (if I understand what you want).
I have one with only optical corrections applied as starting point.

Optical corrections includes vignetting corrections which, depending on the photo, can have a very pronounced effect on tone levels. I don’t think OP wants these corrections at the start of editing.

Indeed, I forgot vignetting. I was about sharpness and chromatic aberration.

1 Like

Hi Mark, thanks for the feedback.

I tried the steps you mentioned, but nothing seems to be helping.

  • I’m starting DxO with the “No Correction” preset
  • I copied the raw file to a different folder
  • I used new raw files that were not loaded in DxO before
  • I deleted the database (I assume it’s the file in AppData\Roaming\DxO\DxO PhotoLab 5\Database?)
  • All to no avail, the “No correction” preset still uses aggressive corrections

To illustrate what I mean exactly, here’s an example. From the left: JPEG preview, Lightroom RAW, DxO RAW:

Sorry for the delay in responding, the moderation of my posts takes forever :neutral_face:

Did you try to activate and change options in color rendering tab, and tweak its slider ?
This changes the starting point (kind of transfer curve from your raw to your bitmap displayable image).

I didn’t keep the default one in order to limit this oversaturated starting point.

What is your camera ? Mine react the same way (D850) if I keep default starting point.

@Inkheart – would you mind to upload a jpg + raw-file so that we can try?

I did play a bit with these settings, and some of them improve the initial state a lot, but my understanding is that this is also applying color corrections, and I just would like to have the original RAW colors after opening it in DxO :sweat_smile:

My camera is Olympus E-M1 II, so looks like this is not limited to any specific camera brand.

Sure thing, here’s the RAW file. I don’t have a separate JPEG, what I posted above is the built in preview when I open the file with FastStone.

P3130916.ORF (18.5 MB)

When you open a file the first time im PL, for a short moment you see the embedded JPG and as soon the raw-file is developped you see PL’s interpretation (talking about the “no correction” preset)
– which can be different as it can be from Lightroom’s interpretation or e.g. FastRawViewer,
while the jpg appearance simply mirrors your in camera settings → PhotoLab 5 Color rendering picks wrong camera body

If you don’t like PL’s interpretation for your cam

choose a different Color Rendering
Screen Shot 03-19-22 at 10.13 AM

and set it as standard (new images discovered by PL)


I took your file, opened it in Apple’s default Preview app on my Mac and opened it in PL5, with no corrections applied. Then, I took a screenshot of the two side by side…

There is the slightest of difference, caused by the demosaïcing process, not by corrections.

On the other hand, if I extract the JPEG preview from your RAW file and open show it in a QuickLook pane, alongside the default preview that QuickLook gives from the RAW file…

There really is no difference, because the preview shown by Finder is the inbuilt JPEG preview image.

As I and @Wolfgang have both said before, what you are seeing when PL first opens the image, is the JPEG preview image being shown whist the demosaïcing is happening. And as Wolfgang says, not all apps use the same demosaïcing algorithm, so you will see differences between what Lightroom gives and what PL gives.

But, rest assured, what you are seeing has nothing to do with any corrections being applied. You have every chance that Lightroom isn’t showing you the “correct” RAW rendering.

Out off interest, in PL5, I selected the Adobe DCP “natural” rendering for your camera…

Capture d’écran 2022-03-19 à 10.52.21

… that gives me…

So, what PL5 is showing appears to be the same as that as its default.

A RAW image is what it says on the tin - a collection of raw data, which can be interpreted to suit the photographer’s preference. Just as there was no standard way of printing a film negative.


Good, you wrote “correct” with quotation marks.

Imo, there is no “correct” raw rendering, only dialects of whatever colour language was used when the photo was taken. All raw developers have their own ideas of how raw image data should be transformed into something that we can recognise as a representation of what was photographed.


Because I’m a bit OCD, here’s a series of screenshots from each of the 9 RAW processors/viewers that I possess (app names are in the screenshot filename)

1 Like

…and thy are all showing “correct” renderings…

Indeed. To quote Sally Mann…

What is truth in photography? It can be told in a hundred different ways. Every thirtieth of a second when the shutter snaps, it’s capturing a different piece of information

Thank you all for your input. I guess I will just need to create a starting preset that I will happy with, and won’t look overly saturated to me :slightly_smiling_face:

< tin hat on > But then you won’t have the untouched RAW :stuck_out_tongue_winking_eye: :roll_eyes: :laughing: :grin: < /tin hat off >