Skip to main content
C
cwurzbach
Known Participant
September 12, 2024
Question

Help With quickDevelopAdjustWhiteBalance

  • September 12, 2024
  • 1 reply
  • 547 views

I am attempting to adjust the temperature and tint for a large number of images using photo:getDevelopSettings() but I am running into the bug mentioned here (and other places) where the temperature and tint = nil.

 

I'm not sure when this bug is going to be resolved so instead I am attempting to use quickDevelopAdjustWhiteBalance. However, I cannot figure out how to produce a consistent value from the amount setting in photo:quickDevelopAdjustWhiteBalance( settingName, amount )

 

For example, this photo:quickDevelopAdjustWhiteBalance( "Temperature", 1 ) produces various values depending on the current temperature value of the image.

At current temperature of 2000, it produces a result of +14

At current temperature of 3000, it produces a result of +17

At current temperature of 4000 it produces a result of +43

 

Could anyone help make sense of the calculation to produce a consistent value? For example, +100 every time.

This topic has been closed for replies.

1 reply

johnrellis
johnrellis
Legend
September 20, 2024

"I am running into the bug mentioned here (and other places) where the temperature and tint = nil."

 

That bug has been marked as fixed in LR 13, since no one has been able to reproduce it. Are you sure that you're accessing photo:getDevelopSettings ().Temperature and .Tint for raws only?  For non-raws, they will be nil (you need to access .IncrementalTemperature and .IncrementalTint).

C
cwurzbachAuthor
Known Participant
September 20, 2024

Thanks for the response. Yes, this happens with only raw photos on version LrC 13 and above. To reproduce, I typically need to attempt to adjust quite a few photos (like 100 photos or so) but the bug is still there. To reproduce, I typically discard all standard previews, then set the white balance to as shot on the photos then do it.

 

johnrellis
johnrellis
Legend
September 20, 2024

I poked around and, as you observe, the bug has reappeared since I last tested in LR 13.0.1. I updated the bug report with a modified recipe for reproducing it and asked Adobe to reopen the issue:

https://community.adobe.com/t5/lightroom-classic-bugs/p-sdk-photo-getdevelopsettings-sometimes-returns-nil-for-temperature-and-tint/idc-p/14872184#M56961 

 

The end of the post has a simple workaround that I've tested on 500 photos exhibiting the problem.  

 

I'm skeptical this will ever get fixed. The developer assigned to the bug last year clearly didn't understand the SDK API very well.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices