# White Balance and border buffer

**URL:** <https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239>\
**Category:** Troubleshooting and Bugs\
**Created:** [January 24, 2021, 4:17am UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239 "2021-01-24T04:17:58Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [January 24, 2021, 4:17am UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/1 "2021-01-24T04:17:58Z")

</div>

I haven’t tested it extensively yet, but it seems that white balance options (none, neutral, auto warm etc) are considering the entire frame and not taking into consideration the “border buffer” setting.

---

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [January 25, 2021, 3:34am UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/2 "2021-01-25T03:34:25Z")

</div>

Please disregard this post. I believe the problem is with the scene and not knowing exactly where the border is.

---

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [February 14, 2021, 10:29pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/3 "2021-02-14T22:29:45Z")

</div>

Ok. I am revisiting the issue.

Please take a look at the images. It looks like WB is not taking border buffer into account.

Original

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/1/121cdf1f26416947b2b007aa0a682e3b7adee7c6.jpeg)

Converted with border buffer 15% WB None (OK!)

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/3/307ce1b65fd82c82427d2d62285b00eaef713276.jpeg)

Converted with border buffer 15% WB Neutral (does not look neutral to me)

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/3/3183ac7438793156631e7c6777449adda734443c.jpeg)

Original (no borders)

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/a/a334aae6b4756d1fb766856cc3f2706a33b28603.jpeg)

Converted with border buffer 0% WB None (OK!)

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/4/4b6e253c70e037d448120fa9856b1675cf0a5f06.jpeg)

Converted with border buffer 0% WB Neutral (looks ok to me)

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/d/d21289b897ecf8905255b08cb202e855a6357295.jpeg)

---

<div class="post-metadata">

**Author:** ![nate](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/nate/32/4_2.png) [@nate](https://forums.negativelabpro.com/u/nate)\
**Post date:** [February 18, 2021, 4:57pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/4 "2021-02-18T16:57:39Z")

</div>

Hmm, thanks @photogeek - that’s odd.

Just tried to replicate the issue you had with 15% border buffer and “Auto-Neutral”, but it worked just fine, so not sure why what you are seeing is so different…

Here’s what I see with 15% border buffer and “Auto-Neutral”:

 ![border-buffer-15-auto-neutral](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/8/8170b845bd66c75dfa1981c839d8038d3485113e.jpeg)

Which is more or less exactly what I see when I crop first and then have no border buffer.

---

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [February 18, 2021, 6:51pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/5 "2021-02-18T18:51:30Z")

</div>

I am still in trial mode, and the version I am using says 2.2.0 and there is no advanced tab.

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/5/5b1910f79e02e3de8372e7e21a11cd3b05cf58fe.jpeg)

---

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [February 23, 2021, 3:39pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/6 "2021-02-23T15:39:19Z")

</div>

@nate BTW, I installed an older version and the issue is not present.

---

<div class="post-metadata">

**Author:** ![nate](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/nate/32/4_2.png) [@nate](https://forums.negativelabpro.com/u/nate)\
**Post date:** [February 23, 2021, 3:59pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/7 "2021-02-23T15:59:32Z")

</div>

Very strange. Nothing should have changed between versions in regards to how the border buffer is calculated internally… also, in my own test of this image I was not able to reproduce your result… I had the same the result whether using border buffer or manually cropping in. So my guess is you may just have had a weird anomaly with image - perhaps the metadata got corrupted for instance.

Feel free to email me the original RAW. Or even better, if you select the image where this has happened, you can go to “File \> Export as Catalog”, and send me the whole “catalog” that contains the image converted with NLP v2.2 (where the auto-netural white balance is too warm). But exporting as a catalog, I will be able to open it up in NLP and get a better sense at what is going on…

---

<div class="post-metadata">

**Author:** ![photogeek](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@photogeek](https://forums.negativelabpro.com/u/photogeek)\
**Post date:** [February 23, 2021, 5:54pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/8 "2021-02-23T17:54:38Z")

</div>

Thank you Nate.  
I will send you the RAW file.

---

<div class="post-metadata">

**Author:** ![printer](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@printer](https://forums.negativelabpro.com/u/printer)\
**Post date:** [March 16, 2021, 10:49am UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/9 "2021-03-16T10:49:45Z")

</div>

@nate I have encountered exactly the same issue. It seems the auto white balance does not take the border buffer into account.

I am using the latest version of NLP with Lightroom Classic 10.1.1 release (Camera Raw 13.1). My OS is Windows 10. I mainly use TIFFs, but I downloaded the sample RAW dslr scans on the website, and I was able to reproduce the same result using the first file \_DSF8434.RAF.

---

<div class="post-metadata">

**Author:** ![nate](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/nate/32/4_2.png) [@nate](https://forums.negativelabpro.com/u/nate)\
**Post date:** [March 17, 2021, 6:06pm UTC](https://forums.negativelabpro.com/t/white-balance-and-border-buffer/3239/10 "2021-03-17T18:06:21Z")

</div>

Thanks for confirming @printer!

I’ve been able to find the issue and this will be fixed in v2.3.
