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

Greetings all, 

 

Updates for the Adobe Photography Products are released.  The August 2024 updates contain an update for this issue.

By Rikk Flohr

Let me see if I can comment, previous attempt failed (or I placed in wrong post)

Looking at the list of issues fixed in v13.5, I do not see this one included. Perhaps a member that has the issue will reply to confirm the issue is resolved.

from:

https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html

The "photo has develop adjustments" icon is appearing on some of my photos that I have not applied any adjustments to. In history, it just has two steps: "import" and "white balance as shot." All of my unadjusted photos without the icon have the same two steps in history. How can I stop Lightroom from adding the icon to unadjusted photos? Also, how can I reset multiple images at once so that they no longer erroneously show the icon?

Hi All,
I have a small issue with LrC develop module.
Once I have all the photos imported and I go through them one by one LrC would mark some photos as 'EDITED' ( small +/- icon in the right bottom corner of the photo) 
It does it randomly and I only go into the photo to look at it without changing anything.
Also what's weird is that it happens to some photos not all of them (totally random).
The problem that I have is when I want LrC to show me only edited photos it shows me the ones that I have edited along with all marked by LrC as edited randomly.
I wonder if that's a program glitch or if there is a setting that I don't know about.
Thank you in advance for all the help.

@efficient_person1243 

"For reference I also have had this issue since 2022. If my camera white balance is set to a specific K value (which it has been for 2 years now) it will import and apply a history step as "WB - As Shot" and renders my organizational workflow useless. Great work Adobe."

Do you use JPG or raw? If you use raw/DNG - then the white balance you set in the camera is irrelevant.

Solution as normal is we wait a few months for Adobe to fix. This one has only shown up around May. Adobe took a bit of time to agree hat it was a bug, and as such it did not get fixed in the last update. Had Adobe immediately agreed it was a bug, we may have seen it fixed at v13.4. It will probably get fixed, in the next update. Often the problem with a bug is to convince Adobe that it is a bug, not a as designed feature. The members managed to get Adobe to state it is a bug, so, it should get fixed. Cross fingers that it gets fixed at next update. When? We common users have no idea, and Adobe does not share that.

This is LrC 101, common process, nothing new. Adobe fouls up, the community members complain by placing a Bug Post, Adobe might come back with not a bug and relocates to discussion. Additional members provide replies showing it is a bug, enough evidence then forces Adobe to state Ok a bug, Adobe log's the Bug, eventually it gets fixed.The post gets relocated again back into Bugs, Adobe may or may not reply as such. Adobe does not state the estimate time to repair. SOP

Oh, and workaround is to either rebuild the library previews, or not use embedded profiles, or to roll back LrC.(v13.2??)

so you criticize the guy but offer no solution? 

Absolutely incredible that this continued mistake in the development of Lightroom for over several years now has not only Adobe Employee eyes on, but moderator and 6 pages of replies to it... and it still isn't fixed. This is genuinely baffling for a corporation that gains revenue hand over fist and can't maintain it's applications in a meaningful and efficient way.

Dissapointing.
For reference I also have had this issue since 2022. If my camera white balance is set to a specific K value (which it has been for 2 years now) it will import and apply a history step as "WB - As Shot" and renders my organizational workflow useless. Great work Adobe

 

By @ShootingPixelsAndy

You state:

"Absolutely incredible that this continued mistake in the development of Lightroom for over several years now "

Well no, this bug is since May 2024, one version older then the current LrC v13.4. Unfortunately it was not fixed at the time. So this has not been a problem for "several years"

You also state, perhaps to support the previous:

"For reference I also have had this issue since 2022."

I see that you are a new member, so you would not have reported that in 2022. Do you have any references to support that. To the best of my knowledge this just showed up last May, and only for users applying embedded profiles.

Are you perhaps conflating a problem or workflow argument)  where LrC apply's As Shot for WB as seen in the Develop Panel edit panels, that does not match the in camera WB setting, with the issue in this bug, where LrC places a History Step of As Shot as the first History state? It used to be, before this bug, that the As Shot for WB did not show up in the History panel. Despite that in fact being applied. And that is a problem if you want to filter on images you have not edited.

Absolutely incredible that this continued mistake in the development of Lightroom for over several years now has not only Adobe Employee eyes on, but moderator and 6 pages of replies to it... and it still isn't fixed. This is genuinely baffling for a corporation that gains revenue hand over fist and can't maintain it's applications in a meaningful and efficient way.

Dissapointing.
For reference I also have had this issue since 2022. If my camera white balance is set to a specific K value (which it has been for 2 years now) it will import and apply a history step as "WB - As Shot" and renders my organizational workflow useless. Great work Adobe.

I have the same issue with the "White Balance - As Shot" thing added to the history (this annoys me cause it fools up the before and after feature). I rebuilt the previews from the library tab and this fixed the problem, the "White Balance - As Shot" disappeared from the history in the Develop module...