When I load image from library, i have problem because the correcation that i don’t want to add are enabled.
I don’t want to have for example enabled DXO Smart Lightinig for all photos added.
But now all photos what i customize have the same correction added.
Where i can disabled it?
If an image is worked on in DxO PhotoLab for the first time, it applies the default preset. The default preset of DPL is “DxO Standard” unless you have changed settings.
If you don’t want DPL to apply the preselected default preset, you can instruct DPL to use a different preset, be it from its pool of presets or a preset that you made yourself. How this can be done is described in this section of the DxO PhotoLab Manual.
On my Mac, things look like this:
PhotoLab settings can be changed
Selecting “no correction” also means that a fixed color temp is used. On my pc standard 5400. I think that’s strange sine the color temp is used together with the demosaicing process. If you’re not aware of that, then you start with a wrong image by definition, or nearly.
I just found out that only General Purpose presets except “no correctios” is using a color temp. None of the others is activating the wb settings. Can somebody explain that?
Both “NoCorrection” and “DxO Standard” presets are “absolute” presets. This means that all tools will be reset to what the absolute preset dictates.
Let’s say that you’ve used the DxO Standard preset and have changed a few things, e.g. white balance. In order to reset the image tho what it was when you applied the preset, click the preset again.
Let’s now see what happens with “Neutral Colour”, which is a partial preset. Apply it to the image and only a few tools will be set to what the preset dictates. Neutral Colour does not change WB, Distortion, Perspective, Noise reduction to name a few.
To me the color temperature is part of the demosaicing process. Based on the values of the raw data a certain correction is done on the channels to get the right colors. If you don’t do that you’ll have wrong colors. How can the demosaicing proces been done without a colortemp???
A fresh picture, no correction. Raw is disabled but shows 5400K. I enable raw, as shot 4579K. I disable raw, temp doesn’t change, histogram doesn’t change.
It seems raw is enabled while it shows disabled. And the color temp and tint are from “as shot”.
Most sensors only read one colour in one place with one photosite. In order to get a multicoloured image, photosites that read different colours are arranged side by side in the image plane. Because we cannot have more than one photosite in one place, the missing parts are interpolated while demosaicing. Colour temperature or white balance don’t matter during this process which is like creating a map, all you want to know is, if there is water, desert or forest, but the kind of trees you’ll find does not matter at that stage…
Each sensor maker builds photosites with a manufactured, known response to daylight, flash, tungsten light etc. and derives, from these responses, the multipliers for the respective colour temperatures. Said multipliers are then stored in the camera’s firmware and applied according to the WB you set in your camera.
Whatever WB you set in your camera, the sensor will always deliver the same value per photosite and only the software, be it in camera or on the PC, will calculate the image from the photosite values and the WB dependent multipliers.
DxO measures these responses under different lighting conditions - and you can find many results like this example on dxomark.com
It was a rethorical question.
In contrary to what the pallets suggest, one can’t disable the wb tool. Even if it shows disabled it’s using a color temp “as shot”. But when ‘disabled’ it shows a wrong temp. Enabling will show you the right temp. A reset or disabling the tool will not change that temp. Only a reset, leaving the picture and going back. Call it a bug. Doing the right thing but showing a wrong value.
It took me some time to find out what was wrong.
On my Mac and using the preset “No Correction”, WB is disabled and displays WB according to camera settings. When I switch to a new image, WB goes to 5400 for a split second, but does not do it any more, once that DPL has calculated the previews in the background.
That’s correct. Enabling does show me the right temp. Disable it again doesn’t change the temp again. But leaving the picture and coming back it shows 5400 again.
Leaves me with the question what disabling or enabling means. One can’t disable colortemp in a demosaicing proces. So show it without that choice and show the right,used, color temp.
Bot my 8.1 and 10 pc’s act the same.
It should show 3381 immediately, that’s the temp that is used. You will not see the picture or histogram changing when you select raw or not. It seems in the mac version the 3381 is shown immediately. Reading Platypus the update from initial value to used value is not done in this case on the win pc.
You’ve a Mac. Just curious. Open an image, change the temp to 10000. When you diasble raw you’ll see the image with the temp “as shot”. Does the temp info change to?
When you disable WB palette, the temperature goes back to the default value (but you should not expect any visualization in the preview or Histogram as it does not affect the image because the palette is disabled). But as soon as you enable the palette the auto value will be recalculated and you should see the calculated value (3318 for our example).
that’s not what I noticed.
Enabling WB palette changes the value from 5400 to the WB the photo was taken…in my case 3381
Disabling WB palette does not change back the value to 5400.
Only when I leave the focus to another photo and come back again I will see the 5400
The histogramm does not change during enabling disabling but when changing setting, temperature or tint
My test cases 1 to 6 are as described.
The default value of the WB Temperature slider = 5400°K, but as you know it’s the correction which is calculated individually for each image based on the calibration - that is why you see 5510K for your image. Unless you question is why it’s not 5600 as set in the camera. In this case we need an assistance from @Marie.