P: White Balance - As Shot added as a History step automatically when using Embedded Previews

Oh really? Since I have the same issue with my photo collection, I have to use the current solution before the bug get fixed.

Btw thank you for your information.🫶🏻

@cmeiling it was a confirmed bug fixed in a previous release. Unfortunately the fix introduced another bug which is currently being investigated by the engineers.

deleted, my bad

I've investigated the reason. 

Probably one reason is, the photo actually didn't change WB by itself. It's just because the Look is different between Library and Develop mode.

If you switch back to Library and the color turns into original, that's what I mean.  (Not sure why Adobe design the stuff like this).

To avoid this, we need to use only JPEG workflow.

That means we need to go to

1. Preferences >> General >> Treat JPEG files next to raw files as separate photo .

2. ReStart Lighroom

And then 3.Reimport all the images (only JPEG files) that you want to edit.

Hope this can help.

The bug is that added step in history, not the shift in the white balance. If you import using embedded previews, then Lightroom initially shows the preview that was generated by the camera. When you switch to the develop module, Lightroom will show you its own preview which will always be a bit different.

Is the White Balance: As Shot step being added to the history or are you just seeing the white balance update on screen?

This issue is not been fixed.

It still happened on 13.5

The white balance is shfting automatically while importing the image.

08/23/2024

The bug recipe posted above now behaves correctly in LR 13.5:

https://community.adobe.com/t5/lightroom-classic-bugs/p-white-balance-as-shot-added-as-a-history-step-automatically-when-using-embedded-previews/idc-p/14659514#M54416

@ShootingPixelsAndy: "I thought Adobe's policy was to include information about bug fixes reported by users?"

That is the policy, but there are infrequent omissions.

I did a quick test and it seems to be fixed but I wouldn't say I've tested enough to be certain yet. I also couldn't see any reference to the fix in the release notes. I thought Adobe's policy was to include information about bug fixes reported by users?