White balance picker issue

[Conrad Hoffman]

We're coming up on yet another release and the white balance picker (normal editing, jpeg files) has yet to be fixed. This is basic functionality and should be addressed. I use this a lot, or at least would if it worked correctly- needs to adjust both sliders, not just the upper one.

[Conrad Hoffman]

Now up to 2.2.0.1881 and this issue remains. White Balance works correctly with RAW files, but not with a simple jpeg:

1) Open "Info" at lower right.
2) Select "Sample from location" and place the target on an area you want to sample, just so you can see the RGB values.
3) Select "White Balance" from the column on the right, "default".
4) Select "Picker" and sample close to, or around, the RGB value target.

Both sliders should have been adjusted such that the RGB values are all equal- a pure grey. That's how white balance should work, but only the upper slider is getting adjusted.

Also, the small target for RGB normally appears at the upper left of the image, but I noticed that it was off the image to the lower right today. Not sure if that's a new bug or something I did differently.

Thanks!

[Chris B]

Hey Conrad Hoffman,

As far as I know, the Tint is only affected when the Temperature is set to use Kelvin. In the Develop Persona, you will notice that the Temperature uses Kelvin and if you develop the image (as a Pixel layer) and return, the Temperature then uses % as opposed to K. Using the White Balance Tool here only adjusts the Temperature and leaves the Tint alone—similar to how the Picker only affects Temperature on a JPEG.

As far as I can see, this has always been the case and is true for V1. Unless I have completely misunderstood your post? 

Can you suggest another app that does this different to what we do so I can investigate further?

I have managed to reproduce the issue regarding the target. If I add and delete a couple of times, the target seems to be placed to the right of my image, as opposed to the top left corner as expected. I can log this. 

[Conrad Hoffman]

Hi Chris,

Yes, it's always been this way. It defeats the purpose of using grey cards and such, something I do often. I don't have the "mainstream" programs, but-

Paint Shop Pro 2019, 21.1.0.22 x64: Found under "Adjust", their implementation is a bit of a confused mess, but the picker does adjust both temp and tint correctly.

Luminar AI, 1.5.5 (not Neo): Found under "Light", the picker adjusts both and works correctly.

Qimage Ultimate, any recent version: Qimage is mostly a printing program, but does have some unusual editing capabilities. Under "Edit Image" the picker does full adjustment and works correctly. FWIW, this program can be considered a gold standard when it comes to color management and printing, but the learning curve is a bit steep and the interface is "unique."

I don't understand why Affinity Photo would only adjust temp with jpg images (I haven't tried Kelvin yet). If there's a reason one would want it that way, please let me know!

Best,
Conrad

[Chris B]

Thanks! We can take a look at those.

10 minutes ago, Conrad Hoffman said:

I don't understand why Affinity Photo would only adjust temp with jpg images

It is likely a bug, in this case. I think because it has been this way since day 1, I or we have not realised it should work in another way I can get this passed back to the developers. Thanks!

[Conrad Hoffman]

Thanks! Also, white balance seems to work OK with raw files in the develop persona, but not with jpegs opened in the develop persona. Not sure how to display kelvin?
CH

 

[walt.farrell]

13 minutes ago, Conrad Hoffman said:

Not sure how to display kelvin?

As far as I know it is only provided with RAW images or RAW image layers, not with JPG/TIFF/PNG.

[Alfred]

26 minutes ago, walt.farrell said:

As far as I know it is only provided with RAW images or RAW image layers, not with JPG/TIFF/PNG.

That aligns with what Chris wrote here:

9 hours ago, Chris B said:

In the Develop Persona, you will notice that the Temperature uses Kelvin and if you develop the image (as a Pixel layer) and return, the Temperature then uses % as opposed to K.

 

[Hangman]

Currently selecting the White Balance tool in 2.2.0 (1881) and sampling a RAW file removes the check mark from the White Balance panel and subsequently closes the panel even though the values are still being updated but I think this is part of an already reported bug regarding certain sliders not working unless the option is unchecked and then checked again, e.g., the Shadows & Highlights sliders.

Though the behaviour for the White Balance tool is slightly different, in as much as unchecking and rechecking the White Balance option makes no difference, as soon as you sample the image the check mark is removed and the panel closed.

[Chris B]

There was an issue on macOS where raw files were opening and the White Balance dropdown was already expanded, preventing any edits - is that what you were referring to? 

[Hangman]

Hi @Chris B,

In previous versions of Photo, opening a RAW file resulted in the Exposure and Enhance options being auto-selected but White Balance, Shadows & Highlights and Profiles are initially unselected.

In 2.2.0 it's the opposite, i.e., the Exposure and Enhance options are not selected but White Balance, Shadows & Highlights and Profiles are auto-selected.

Leaving White Balance selected, as soon as you select the White Balance tool and sample the image, the White Balance checkmark is removed from the White Balance Panel resulting in the panel closing but the White Balance values are correctly updating. If you then add a checkmark in the White Balance panel again so you can see the values and take another sample using the White Balance tool, the checkmark is again removed and the panel closes.

This feels like a slightly different but possibly related issue/bug, though I'm not sure...

[Chris B]

Yes, this is what I was referring to. We've got a newer build that has fixed the issue you mentioned but it is different to what the OP is talking about  

[Hangman]

2 minutes ago, Chris B said:

We've got a newer build that has fixed the issue you mentioned but it is different to what the OP is talking about

Sorry, I realised this is a different issue, I should have made a separate thread but glad this particular issue is fixed in a newer build...

[Conrad Hoffman]

Just bumping this up. It's been rather a long time and nothing has been done on this. I shoot mostly jpegs and fiddling to get grey to equal RGB values is a pain. Hoping it will be addressed soon.

[Chris B]

Thanks for the bump. I will go ahead and update the bug report.