Strong exposure/tint compensation needed in develop persona

[ArieV]

Hi there,

 

I recently noticed some funny behaviour in the develop persona.  Most raw files need 1-2 stops of exposure increase, and the tint in white balance needs to be in the +45 range (towards magenta).  The same files look and process okay in DPP without drastic adjustments.  I get the same behaviour with raw files from Canon 70D, 7D, and 400D (.CR2) and RP (.CR3).

When I do apply the strong exposure and tint compensations in Affinity Develop persona I end up with good results, so this funny behaviour is no big deal.  But When I first started using Affinity a few months ago these strong compensations weren't needed.

Did I change some type of setting somewhere?  Or is something else askew?

Thanks.  Arie

 

[stokerg]

Hi @ArieV,

Do you have a couple of sample RAW file you could attach?  

Also if you can open a RAW file and while still in Develop click, View>Assistant Manager and take a screenshot of those settings and attach it here?  There will always be some difference to how different apps display RAW data and some apps don't even display the RAW data, they display an embedded JPG but still, i wouldn't expect too much of a difference between apps when displaying the actual RAW data.

[ArieV]

Hi stokerg,

 

Sorry about the delay.  I've attached a sample .cr3 file.

Preview in Canon DPP

 

Preview in Affinity, with default settings.  Note tint slider on bottom right.

 

 

IMG_4680.CR3

[ArieV]

.. and

[RichardMH]

Can you also post a screenshot of your colour preferences? (Edit->Preferences->Colour) And are you on a Windows PC?

[Ron P.]

I did not touch the White Balance settings, but did adjust some of the other tonal settings, as seen in my screenshot. In the Assistance Manager, my settings are Take no action for Tone Curve and Exposure Bias. I want to control those. Even if you choose to have Photo apply those, you still must adjust the other settings. Photo will not automatically apply these, it gives us the RAW data with little to no intervention, so we can develop our RAW files as we want them to appear. We may want an accurate depiction of what we saw when we pressed the shutter, or an artistic, creative depiction. 

I don't see that much difference in what DPP provided.

 

[NotMyFault]

9 hours ago, ArieV said:

.. and

 

A screenshot of the info panel of the raw file (showing all capture settings and active recipe in DPP) would help.

if you have any “picture profile” or adjustment active, DPP will respect them, whereas Affinity will ignore them (sharpening, color, saturation, …) leading to strong differences.

[ArieV]

Hi @Ron P., the settings you used are roughly what I end up using.  Lots of exposure and a tint of around +43.  So yes it is possible to get a good result, and one that matches DPP, but it's weird that suddenly I have to resort to these values.  I'm trying to understand what's going on in order to get a better grasp on Affinity and my camera.

The funny thing is that until a few weeks ago, the default exposure was just about right (I was using, say -0.5 to 0.5) and the tint values were in the middle of the slider (typically +4 to +6).

I'm running Windows 11.

@NotMyFault, I shot this photo at 100 iso, f/7.1, 1/250 s, evaluative metering, no exposure compensation.

I understand that DPP uses things like picture styles and previous DPP processing parameters.  I used a standard picture style.  The file I supplied (and others in my catalog) do not have previous DPP processing values in the header.  I know this because DPP asks before it saves and overwrites old values.  In any case, if those values got out of whack it'd be DPP showing a strange result upon opening, and it's Affinity that shows the underexposure.

 

[ArieV]

Hold the phone....  I just saw that my camera has the Auto Lighting Optimizer enabled.  I'm not sure how that happened.  I turned it off, tried a few test shots, and things look better exposure-wise.

But that still leaves the funny tint values.