"Neutral color, neutral tonality" renders reds too magenta

Some of us have noticed that using PhotoLab’s “Neutral color, neutral tonality” setting, even after otherwise white-balancing to taste, leaves reds looking too magenta. Recently (maybe the last year or two? going back to PL 3?) To make reds look correct, I’ve frequently found myself forced to go into HSL, choose the red channel, and rotate it counterclockwise (toward yellow and away from magenta).

And it’s not only me. Here’s a recent thread at DPReview:

Has anyone else experienced this?

FWIW, I have a Dell U2415 monitor that I calibrate and profile with an X-Rite ColorMunki Display, and I also print my photos on both an Epson R280 (at home, with CcMmYK Claria inks) and a Canon Pro-100 (at work). The problem persists across all outputs.

Reds can shift off their expected hue under the circumstances you mention, @NAwlins_Contrarian.
I get the effect quite often, as my default preset contains the neutral, gamma 2.2 colour rendering.

The colour shift can mostly be removed with the tone curve (see note below) or the HSL tool. I consider this to be a necessary consequence of the math involved rather than something odd or wrong.

Note: Neutral rendering often produces images that look too bright. I correct this with the tone curve, which often moves purple-red hues away from magenta.

PS: This kind of magenta-shift is fairly old: https://forum.dxo.com/t/export-to-lightroom-kills-reds/1455

1 Like

NAwlins, I’d recommend you pick an alternative neutral preset if you don’t like the built-in preset. It’s very easy to roll your own. My main preset includes switching the rendering to Leica M-E, M9, M10 (for Nikon Z6, D850, Z9; D4 used Leica M-10D preset) which has higher contrast and more vivid reds. It’s a better starting point for me. In certain environments, my starting point preset includes Fuji Pro 400 which adds quite a bit brightness in the mid-tones, more contrast and improves greens.

If you don’t like to the colour profiles, you can roll your own neutral by adjusting HLS the way you like and include that HLS setting in your own neutral profile.

Neutral at the end of the day is either 1. math or 2. subjective. Pick your poison. At least PhotoLab give us the option to very easily create our own neutral or starting point presets which suit our work and our perceptions.

1 Like

I have the same problem and have reported this as a bug to no avail.

Yes, this looks like a bit of a bug.
I opened the raw with DXO Generic and neutral tonalities and exported a jpg. I then did the same with C1 using Auto and Linear tone curves.
I then opened each of the 4 images in C1 and dropped a colour picker on the red wood,
This gave the following readouts:
Test R G B L
C1 Auto 227 127 109 155
C1 Linear 193 88 84 119
DXO Generic 225 108 96 142
DXO Neutral 219 61 112 114

What strikes me is that in C1 you get the shift in values that you expect i.e. as luminance decreases RGB values decrease.
In DXO as Luma decreases the Red value only shifts down a little, the Green goes down but the Blue value increases.

The question is, which colors are correct? Just for comparison, I compared different profiles of a color checker. Maybe that helps for the discussion.

2 Likes

@maderafunk Thanks for that image. I saved your image, opened it in C1 and dropped some colour readouts on the patches.

You don’t see such a large shift in colours with your D750 image, suggesting that it is camera dependant, although you do still get an increase in the Blue channel as the luma goes down. This does not happen with the other colours and suggests that maybe DXO Staff could comment?

A noticeable colour channel shift (very noticeable on the Panasonic G9) for one colour,


is surely not intentional? If it is, why?

It might indeed be the case that some color profiles are not correct. I have noticed for example, that for some cameras (Canon 1DMK3, Leica M9) there is a noticeable shift in White Balance in comparison to other color profiles.

You could try to calibrate a profile for the G9 based on this studio picture by Dpreview. It might not be the best image, as sometimes there studio scene becomes a bit old and the colors of their color checker might have faded, but maybe it is good enough.

This was a very good idea. Having just come across this thread, and tried your suggestion, the colours out of the G9 do seem improved across the board.

See two images below - both started at “No Correction” preset, only change between them was application of new calibrated profile.

Inbuilt DxO Generic profile

Calibrated profile

Differences subtle, but noticeable.

I’ve had a similar problem since forever with the way PL handles Canon RAW files, in particular with .CR3 files, less so with .CR2 files. For me, the workaround is to tweak the tint slider on the RAW white balance. Typically at least halving the (positive) value that PL sets / derives from the camera ‘as shot’ value, to shift the white balance tint away from magenta towards green.

Since every image requires its own tweak I don’t bake an adjustment into my default preset. I just expect to have to mess with the tint slider.

Aye, tweaking the tint slider was my approach before, as well as experimenting with different camera body/filmpack renderings.

But after trying this new DCP last night, it seems as if it generally provides a more accurate starting point, and the WB presets actually correspond to what one might expect in terms of temperature and colour.

I expect images will still need tweaking, but the base seems to be much improved, meaning I’ll spend less time fiddling to get a good base colour before I start making more creative hue adjustments.

Can you run that by me again please?

I shoot with a Canon R6 which outputs .CR3 files and I find the PhotoLab profile for the R6 to be an awful starting point - it completely changes the look of any image it’s applied to from a generally balanced and pleasing set of tones to… a mess.

I didn’t have this problem with my previous cameras (a 5D and a 6D).

Now I tend to apply PhotoLab’s portrait or “natural” presets which aren’t camera specific at all, but are more pleasing to work with than anything specific to my camera. Given Canon is traditionally popular for its colours, I feel like I’m missing out.

If there’s a better way, I’m all ears!

I don’t know if it’s better or not but for my Canon 90D (and previously a 400D) I start from:
working colour space: DxO Wide Gamut
RAW white balance: as shot
Colour Rendering type: Generic
Colour Rendering rendering: Neutral colour

Got you, so you’re just kinda… sidestepping any issues with Canon profiles or colours and using some other interpretation?

I mean I don’t see why not as such…

Yes, I didn’t like PL’s profiles for the 400D or the 90D. I find that starting from what PL thinks is neutral and then seasoning to taste gives me much more pleasing results.

Mind you I’m only an amateur, poking at one or two photos at a time. I’m also retired so I have plenty of time to edit photos. I suspect if I were a pro., with deadlines to meet, my current approach would not be cost effective.

1 Like

I understand, I’m much the same myself (not professional through-and-through, though I do do some paid shoots). At any rate I rarely HAVE to process hundreds of photos in a session. I honestly don’t think PhotoLab is the right tool for that!

1 Like

FWIW: I find that [Type = Camera Body & Rendering = DxO One] provides a very good result … Perhaps because DxO put special effort into getting the rendering right for it’s own (tho, now redundant) equipment (?)

As I have both Sony and Olympus/OM-1 gear, I use this rendering to produce a “consistent look” from both sources.

Ok with you.

I bought DxO Optics Pro in 2008 and for several years I noticed a green dominance on the pictures of my Sony A700.

Since they have corrected, it is good and I can see the difference between camera jpeg and DxO jpeg.

This might be a silly question, but does this not make sensor biases (e.g. “Canon does nice colors” or “Sony can’t do warm tones”) redundant?

We can just pick a sensor profile we prefer…?

1 Like

This is correct

Sigi