Infrared white balance

[zibrah]

When setting the white balance on a fuji raw file in develop the color is way off. The temperature goes to the maximum giving an extreme yellow color.

It happens whether I select with a point or option and drag to select an area. Affinity 1 did a great job of white balancing infrared.

All of the settings are the same in both programs.

The first is the original file and white balance.

The second is after white balance in Version 1

The third is after white balance in Version 2

I hope it gets worked out because Version 2 is way off... making it all but unusable for infrared

MacBook Pro intel.  Big Sur

Edit: I just wanted to add that in V1 that the temperature would rocket to 25,000 but the results were good.

        In V2 it rockets to 25000 but obviously the result and value is way off and incorrect (extreme yellow/orange). 

       I have tried all the combinations in the color and graphics settings to no avail. I have used the integrated and dedicated graphics cards and all of the metal and OpenGL settings possible again with the same results and can replicate it every time. It appears to be broken when compared to V1

 

[wik-wav]

I'm also having an issue with infrared white balance - the range is just too small for proper correction currently.

[NoNo]

I have the same problem as described by zibrah. With version 1, the white balance can be set on my Nikon RAWs with all imaginable IR filters, but not with version 2.

Edited November 14, 2022 by NoNo

[AndrewG]

Yes I'm also having the same problem with the raw files from an infrared converted Nikon D7200.  White balance adjustment worked fine in AP v1.

[Chris B]

Hi all,

I'll try and find out what has happened. 

[NoNo]

Thank you very much. With this hopefully unwanted change, version 2 is unfortunately worthless compared to version 1 for photographers who use the near infrared (NIR) with converted cameras.

[NotMyFault]

5 minutes ago, NoNo said:

Thank you very much. With this hopefully unwanted change, version 2 is unfortunately worthless compared to version 1 for photographers who use the near infrared (NIR) with converted cameras.

Worthless maybe a bit exaggerated conclusion. There are several ways to achieve white balance by other methods (curves, levels, …).

IR Photography is more a creative discipline, not a science. 

[wik-wav]

1 minute ago, NotMyFault said:

Worthless maybe a bit exaggerated conclusion. There are several ways to achieve white balance by other methods (curves, levels, …).

IR Photography is more a creative discipline, not a science. 

While it is a creative discipline, setting white balance is not part of the creative bit (because this is the starting point, literally setting a reference for what white is, from which any other edits are to be applied and it is meant to make a picture look as neutral as possible).
As a side note, I'd like to mention it's possible to set it correctly in the develop persona using overlays (for example making a gradient that fills the entire picture and adjusting it twice). This is not ideal but it works for now.

[NoNo]

Or you use AP in version 1. There it works without any problems. Manual white balance using a pipette is an elementary basic function for IR photographers and has nothing to do with creativity. To compare CWB AP1 vs AP2, CWB only:

[NoNo]

This does not only apply to classic longpass filters. Also other filters like here with an InfraBlue filter. Only CWB, nothing else!

No matter which IR filter, the problem is always the same.

[Old Bruce]

I shoot Infrared with a Canon and an infrared filter on my old Nikkor glass. I use a Tripod because the exposure times are really long. I have never used the White balance tool for this. About the only settings I use in the Develop Persona are some noise removal and a bit of exposure adjusting, less is more for the IR work I think. Then I use a fill layer with the colour chosen by clicking on the spot I would consider to be 'white' in the final picture. Then I set the Fill Layer's blend mode to Divide. I get some good results.

[NoNo]

This indirect solution may work untested with a longpass filter around 700nm, but there are many other IR filters that have nothing in common with this category of IR filters. My goal are false color IR photos, where many natural colors are preserved in addition to the wood effect. This works fine with AP 1 but not with AP 2. So why want to use AP 2 with any weird tricks?

A few false color IR photos processed with AP 1:
 

[maikm]

I'm also affected. Glad I didn't delete V1 yet. My converted Nikon Z5 images will now turn completely red when I use the WB picker in V2 develop persona, while it works fine in V1. It feels like there is a safeguard in place in V2 to protect from "unreasonable" values, which did not consider IR imaging.

[Chris B]

Can you provide some of the images you are working with so I can do some comparisons for the developers, please.

[maikm]

Sure, here's a sample NEF file: maik_20221128_150459_z5_000069.nef

[wik-wav]

Sure. Included are pictures taken with several different filters and some fullspectrum shots too.

DSCF6517.afphoto DSCF0344.RAF DSCF0372.RAF DSCF0618.RAF DSCF0663.RAF DSCF9094.RAF DSCF0169.RAF DSCF0176.RAF DSCF7437.RAF

[Chris B]

Thanks for the samples. 

I think we've worked out what is happening. The White Balance Tool now affects Tint in some sort of negative way.

We are speaking with dev at the moment for a possible solution. 

[NoNo]

Installed version 2.0.3 today and the manual white balance now works. Thanks everyone!

 

[maikm]

Indeed, confirmed for me too. Thanks!

[NotMyFault]

Unfortunately with some unwanted side effect:

 

[AndrewG]

The WB tool now seems to work ok for me (Nikon D7200 converted camera 720nm filter).

Thank you.

[CoilM]

1 hour ago, NotMyFault said:

Unfortunately with some unwanted side effect:

 

Just to let you know that I tried downgrading to 2.0.0 and the error is still the same.

[NotMyFault]

6 minutes ago, CoilM said:

Just to let you know that I tried downgrading to 2.0.0 and the error is still the same.

Ok, then we may have 2 unrelated bugs affecting white balance for RAF files.