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

It appears from other posts regarding this, that it's a bug in the latest version with embedded previews. I'm not the only one experiencing this.

Thank you for your reply!

This seems to have just appeared within the last few updates. I'll import a few hundred images and all of them have the White balance: As shot develope setting applied. I haven't changed anything in my preferences and cannot find where this is turned on. The problem is I cannot filter on un-edited images. 

Bonjour,

J'ai depuis peu un nouveau réglage dont je veux me débarasser. Quand je clique sur une photo dans le module Développement, celle-ci se voit appliquer une modification de balance des blancs ("Tel quelle").

Comment désactiver ce pré-réglage ?

Le fait est que cette photo est défini comme comportant des modifications dans ma bibliothèque dynamique et je retrouve des photos non retouchées dans ce dossier simplement parce-que j'ai cliqué sur une photo au hasard dans le module développement.

Merci.

The issue is still there in 13.3.1 using Windows.

@Patrick Maes 

After updating my catalog to v13.3, I too experienced the addition of the "Multiple Settings" step to newly imported photos. That was during the first session after updating the catalog. In subsequent sessions (after exiting and reopening LR), I've been getting the "White Balance: As Shot" step for newly imported photos (like other folks in this thread have reported).

In my case/observations, it seems like the first and last photos in the imported batch do not get the WB step added but all the photos in between do. The Before view also shows a different WB than the After view as you've reported.

Hope this bug gets squashed soon - having to manually reset every photo is getting rather tedious. If I don't reset, then every RAW file I view appears to be "edited".

I now realize that an issue I experienced when upgrading my v13 catalogs to v13.3 may also be related to this.
Several photos suddenly receive an additional history step "Multiple Settings". That step does not change the develop settings, but when I do a before view the white balance of the before view has visually changed!?!

This is the same phenomenon we see with the imported photos that are given the "White Balance: As Shot" step out of the blue.

I have not adjusted the white balance myself. Before the upgrade, the white balance was the same in the before and after view.

The white balance of the after view after the upgrade is the same as the white balance of the before and after views before the upgrade. That was expected because no WB adjustment was made by the user.
The white balance of the before view after the upgrade is different from the white balance of the before and after views before the upgrade and the after view after the upgrade. That was not expected.

I mention it here because it might ring a bell among the developers.

A little more testing and I've discovered that the WB step is only added when you select the next image in the filmstrip, eg.
If you've got 10 images and start on 1 and then click on 2 WB will be added.
If you then go back to 1 and click on 3 WB won't be added.
Now if you click 4 it also won't have WB added
Continue to 5 and suddenly the WB is back.
Note that this has to be done in Develop and all images need to be using embedded/side car previews.

Every now and then the above fails which I think is somehow timing related and I suspect the bug was introduced with the "Enhanced responsiveness and improved navigation experience in the Develop module." of 13.3

@Patrick Maes, "About step 2 (Set Preferences > Presets > Raw Defaults > Global to Camera Settings.): choosing "Adobe Default" there also results in the unnecessary "White Balance: As Shot" history step. ... In my case (tried several times): not all new imported photos (Embedded & Sidecar import) have this "White Balance: As Shot" step."

Yeah, as I wrote above, in my configuration the bug occurred with both Adobe Default and Camera Settings, though it was intermittent with Adobe Default.

@Ian Lyons: "Note that I cannot reproduce on Mac. Therefore, issue may be Windows only."

I tested my bug recipe on Mac 14.4.1 / LR 13.3, where it failed.