P: photo:getDevelopSettings() does not always return all / valid values

I forgot to mention that this workaround is slow -- about 0.25 seconds per photo on my computer.

@LightroomStatistics, recently while learning how LR builds previews, I discovered a workaround for this bug: Increment the photo's exposure by 0.01, request the photo's thumbnail, decrement the exposure by 0.01, request the thumbnail again. After doing this, the value of Temperature will be non-nil.   Here's a script demonstrating the workaround:

local catalog = import "LrApplication".activeCatalog ()
local currentTime = import "LrDate".currentTime
local message = import "LrDialogs".message
local sleep = import "LrTasks".sleep

local size = 50
local poke   

local function fix (photo)
    poke (photo, 0.01)
    poke (photo, -0.01)
    return photo:getDevelopSettings ().Temperature
    end

function poke (photo, delta)
    local exp = photo:getDevelopSettings ().Exposure2012
    catalog:withWriteAccessDo ("Poke " .. delta, function ()
        photo:applyDevelopSettings {Exposure2012 = exp + delta}
        end, {timeout = 30})

    local done = false
    local handle = photo:requestJpegThumbnail (size, size, function (data, err)
        if err then assert (err) end 
        done = true  
        end)

    while not done do sleep (0.05) end 
    end

local t = currentTime ()
local nNil, nFixed = 0, 0  
for _, photo in ipairs (catalog:getMultipleSelectedOrAllPhotos ()) do 
    if not photo:getDevelopSettings ().Temperature then
        nNil = nNil + 1
        if fix (photo) then nFixed = nFixed + 1 end 
        end
    end
t = currentTime () - t
message ("Test results", 
    string.format ("size: %d, nil: %d, fixed: %d, time/photo: %f",
        size, nNil, nFixed, t / nNil))

Any news on this?

@Rikk Flohr: Photography

The only workaround I know of is to do Library > Previews > Build Standard-Sized Previews, which forces the deferred rendering of photos with changed settings. The SDK doesn't provide any methods for doing this, unfortunately.

Also experiencing this behavior. Any workaround to get the correct values.
I need them for Temperature and Tint.

Also noticed that after Resetting the settings with <Ctrl><Shift> R a lot images report no values for Temperature and Tint.

Not getting the develop settings break many of the existing plug-ins!
This is a core functioanlity of the SDK

Lightroom version 13.3.1 and CameraRaw 16.3.1

After setting the White balance to "As shot" the photo:getDevelopSettings() doesn't return the correct develop settings for Temperature or Tint. All photos selected are RAW files.

Also there is a difference in behavior when running the script on images with or without having resetted the settings to original <Ctrl><Shift> R.

On new images the value of -999999 returned, however when you Reset the images with <Ctrl><Shift> R and run the script again, instead of the value for Temperature and Tint is nil.

Only after 1 or more seconds the correct values are returned.

First run on new images:

Now hitting the Reset settings <Ctrl><Shift> R key:
Same images still selected.

Code used:

local LrApplication = import("LrApplication")
local LrDialogs = import("LrDialogs")
local LrFunctionContext = import("LrFunctionContext")

local catalog = LrApplication.activeCatalog()

local logFilename = 'WhiteBalance_01.txt'
local MyLogger = import 'LrLogger' (logFilename)
MyLogger:enable("logfile")

local inspect = require "inspect"

local function main(context)
	LrDialogs.attachErrorDialogToFunctionContext(context)

	local photos = catalog:getTargetPhotos()
	MyLogger:info("#photos", #photos)

	local devSettings = { WhiteBalance = "As shot" }
	catalog:withWriteAccessDo("Apply White balance settings", function()
		local preset = LrApplication.addDevelopPresetForPlugin(_PLUGIN, "WB As Shot", devSettings)

		for _, photo in ipairs(photos) do
			MyLogger:info(photo:getFormattedMetadata("fileName"))
			photo:applyDevelopPreset(preset, _PLUGIN)
		end
	end)

	local message = "Loop 1\n"
	local nilValues = true
	local counter = 1
	while nilValues and (counter < 20) do
		nilValues = false

		for _, photo in ipairs(photos) do
			local fileName = photo:getFormattedMetadata("fileName")
			local developSetings = photo:getDevelopSettings()
			MyLogger:info(fileName, inspect(developSetings))

			-- Test for nil values
			if (nilValues == false) and
				(
					(developSetings.Temperature == nil) or
					(developSetings.Temperature == -999999) or
					(developSetings.Tint == nil) or
					(developSetings.Tint == -999999)
				) then
				nilValues = true
			end

			message = message ..
				string.format("image: %-15s temperature: %-8s tint: %-8s\n", fileName,
					developSetings.Temperature or "nil",
					developSetings.Tint or "nil")
		end

		if (nilValues == true) then
			counter = counter + 1
			LrTasks.sleep(0.5)

			message = message .. string.format("\n\nLoop %d -- wait for an extra %.1f seconds\n",counter, 0.5)
		end
	end

	LrDialogs.message("LightroomStatistics", message)
end

LrFunctionContext.postAsyncTaskWithContext("", main)

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

I had filed a bug report about this for LR 12.2, but my bug recipe worked correctly in LR 13.0.1, so I asked Adobe to close the bug report:

https://community.adobe.com/t5/lightroom-classic-discussions/photo-getdevelopsettings-does-not-always-return-all-valid-values/td-p/14331997 

However, following your steps, I can reproduce the problem in LR 13.1 / Mac OS:

1. Put 200 raws in the Quick Collection and select it as the current source.

2. Select all the photos and do Quick Develop > Reset All.

3. Run your script above and observe these incorrect results:

4. Run the Any Filter plugin's Filter command with the single criterion Temperature and observe the same number of photos (183) with no value for Temperature:

5. Select all the photos and do Library > Previews > Build Standard-Sized Previews, forcing LR to re-render all the images.

6. Rerun the script and Any Filter and observe all photos have valid values for Temperature.

-------

There have been a number of similar bugs reported over the years. Internally, LR defers a lot of computation after the user applies a command to a batch of photos, and the SDK doesn't always force deferred computation when accessing develop settings.  Sometimes there are bugs with the deferred computation overwriting user-applied settings, with no plugins involved (e.g. applying Auto Settings to a batch of photos).