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.
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
My camera is Olympus E-M1 II, so looks like this is not limited to any specific camera brand.
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
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…
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.
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)
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
Indeed! Strive for what you like instead of searching for what might be “correct” - unless you work in the field of reproductions, where results should look as close to the original as possible.
@Inkheart@platypus@Joanna
There is at least a color style choosen by each manufacturer for its bodys and this is why lot of nikon users like “nikon colors”.
Would be nice if they were “cracked” by DxO more faithfully when creating body profile.
Seeing all the attention that dxo gives to its tests I would expect and like something closer.
DxO demosaicer looks in a way like fujifilm at the age of the silver photography (I am sure @Joanna understand what I’m saying). For sure it is not an ektachrome !
Maybe trying to shrink all raw datas in adobe rvb color space does not allow to keep some subtlety.
A RAW is a box of ingredients you can use to make a cake.
The RAW Preview you see in most apps is just the picture of a cake on the back of the ingredients box.
RAW’s aren’t ‘supposed’ to look like anything - they are a bunch of ingredients. You have to cook them before they become a cake, so complaining they don’t immediately look like a specific cake is kinda missing the point.
And the jpeg or tiff your camera provides or embed in your raw (I know it can provide several and you can choose them) is often the starting point recipe that mades you choose a camera ! Sooooo …
So it should be the reference recipe
The brand specific colors …
What the photo on the back of the cake box looks like depends on the brand, but what the actual cake looks like when baked depends on you.
So I wouldn’t get too concerned about whether your cake looks like some arbitrary standard, as long as you’re happy with the result.
The point is, RAW’s are not a standard image format, they are a collection of data. There is no ‘normal’ way for a RAW to look, there is only an interpretation. By definition, interpretations differ.
< /tin hat off >