Lightroom: Applying Auto Tone to a batch of photos loses subsequent develop settings

  • 28
  • Problem
  • Updated 8 months ago
  • Acknowledged
  • (Edited)
When you apply Auto Tone to a large batch of photos, LR does not consistently update all the photos, and subsequent batch changes to the photos’ develop settings can get lost.  This happens when using any of the mechanisms for batch changes: Photo > Develop Settings > Paste Settings, Auto Sync, Quick Develop > Saved Preset, or via the SDK.

This problem has existed for many years (see all the reports merged below), at least since LR 5, and probably at least since LR 4.

Apparently, when you apply Auto Tone to a batch of photos, internally LR just sets a flag on each photo, deferring the actual computation of the Auto Tone until later. It won’t actually compute the Auto Tone develop settings until the photo’s thumbnail becomes visible in Library or you edit the photo.  But any other develop settings you’ve applied to the photo in the meantime will get silently overwritten by the deferred Auto Tone.

To reproduce the problem: 

1. In Develop, define a develop preset “Test Dark” with only Basic Tone: Exposure checked, with Exposure = -5.00.  

2. In Library grid view, select at least a couple hundred photos.

3. Do Quick Develop > Reset All.  Scroll through all the thumbnails to make sure the reset completes.

4. Do Quick Develop > Auto Tone (with all the thumbnails still selected).

5. Wait a minute or more (you don’t have to wait, but this shows the bug is not timing dependent).

6.  Do Quick Develop > Saved Preset > Test Dark to apply the preset to all the photos.

7. Scroll through the thumbnails and wait for the three white dots in the upper-right corner of each to go away, indicating that the the deferred Auto Tone is finally being applied.  Notice that only some of them are correctly rendered as auto-toned followed by Test Dark (i.e. they are near black).    

In general, if a thumbnail was off-screen at step 6 when the preset Test Dark was applied, then the Auto Tone will eventually take effect, but the exposure setting of Test Dark will be lost. Further, the develop history will be inconsistent, showing Test Dark as being applied after the Auto Tone, but the exposure slider showing the Auto Tone setting, not the Test Dark settings of -5.00:



Workarounds:

Three workarounds:

- In LR 7.3.1 and later, apply Auto to the batch of photos using a preset, e.g. the built-in preset Classic - General > Auto Settings.

- After applying the batch Auto Tone, scroll through Library grid view and wait until the Auto Tone is actually applied before applying another preset or batch develop setting.

- With all the photos in the batch selected, do Library > Previews > Build Standard-Sized Previews and wait for the progress bar to indicate completion.

A related problem:

A similar problem occurs when synchronized Lens Profile Corrections to many photos, and the workaround is the same.  See https://feedback.photoshop.com/photoshop_family/topics/lightroom-sdk-photo-getdevelopsettings-return...
Photo of John R. Ellis

John R. Ellis, Champion

  • 4289 Posts
  • 1138 Reply Likes

Posted 3 years ago

  • 28
Photo of Hans Kuehne

Hans Kuehne

  • 5 Posts
  • 1 Reply Like
This reply was created from a merged topic originally titled Syncing Development Settings Unreliable After Applying Auto-Settings.

Dear all,

the new Auto-Settings have been greatly improved in quality, but they do prevent syncing development setting "Shadows" correctly after application.

I have a reproducable bug here in my newly updated LR CC classic 7.31 on PC.

Procedure:
- Import 139 images (*.CR2) into a new Folder in a new catalogue.
- Apply Auto Settings to all of them (right-click and context menu)
- Set "Shadows" to Zero again for the first Image
- Select ALL images in the folder
- Sync development setting "Shadows" to ALL images in the folder.

Result:
The development setting Zero for "Shadows" has been applied only to the first 10-20 images of the folder and to the last 10-20 and to some in between.
But more then 50% of the 139 images in the folder remain untouched by the sync.

This problem occurrs only after Auto-Settings have been applied to the images in the folder. otherwise the sync of development settings works fine and applies to ALL selected images.

The described problem was observed after the update to 7.31, but I am not sure, whether it came with this update or with an earlier one.

A re-installation of LR CC classic did not solve the issue.

Whether other development settings than "Shadows" are concerned also has not been tested so far.

Dear Adobe quality team, could you please have a look into this?



Kind regards,
Hans



Photo of John R. Ellis

John R. Ellis, Champion

  • 4254 Posts
  • 1128 Reply Likes
This is a very old bug, dating back to at least LR 4, that Adobe has not yet chosen to fix. Now that Auto works much better, more people are noticing the bug. See the first post in this topic for straightforward but tedious workarounds.
Photo of Hans Kuehne

Hans Kuehne

  • 5 Posts
  • 1 Reply Like

Hi John, many thanks for your help. The workaround with generating standard previews works also for me.

rgds, Hans


Photo of John R. Ellis

John R. Ellis, Champion

  • 4289 Posts
  • 1138 Reply Likes
With LR 7.3.1, the bug no longer occurs when you apply Auto using a preset, e.g. the built-in preset Classic - General > Auto Settings.  

But the bug does still occur when you apply Auto using the Auto button in Quick Develop, the Library menu command Photo > Develop Settings > Auto Settings, or Develop's Auto Sync.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4289 Posts
  • 1138 Reply Likes
In LR 7.5, the bug again occurs when you apply Auto using a preset. It still occurs in the other contexts two: Quick Develop > Auto, Photo > Develop Settings > Auto Settings, Develop's Auto Sync, presets applied during Import.
Photo of Jan Leschke

Jan Leschke

  • 1 Post
  • 0 Reply Likes
Thanks to John R. Ellis, who told me about this bug in the adobe forum. Same problem here, Processing a bunch of pictures with auto and trying to sync settings afterwards leads to confusing results. It works for some pictures of my selection but fails for the bigger rest..
Photo of Dmitry

Dmitry

  • 182 Posts
  • 52 Reply Likes
This reply was created from a merged topic originally titled Paste settings doesn't past settings to all selected images.

1. Copy brightness = 0 and exposure = 0 settings.
2. Select more than 1000 images.
3. Paste the settings.
4. Check all images.

Should be: All images must have brightness = 0 and exposure = 0.

Actual result: Not all images will have brightness = 0 and exposure = 0. Even if you paste settings two times some images won't have brightness = 0 and exposure = 0.
Photo of Dmitry

Dmitry

  • 182 Posts
  • 52 Reply Likes
This reply was created from a merged topic originally titled Paste settings doesn't past settings to all selected images (merging).

I applied Auto to all pictures. Then I want to clear brightness and exposure because Auto values are awful for them. And Paste applies each time only to about 200 random pictures (I select all 1000).

Note: This conversation was created from a reply on: Paste settings doesn't past settings to all selected images.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4280 Posts
  • 1138 Reply Likes
As a workaround to this long-standing bug, immediately after applying Auto, select all the photos and do the menu command Library > Previews > Build Standard-Size Previews.
Photo of Dmitry

Dmitry

  • 182 Posts
  • 52 Reply Likes
Thanks! But it's better to spend time on fixing issues than on searching for workarounds...
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 4280 Posts
  • 1138 Reply Likes
I agree. (I don’t work for Adobe.)
Photo of Robert Frost

Robert Frost

  • 426 Posts
  • 72 Reply Likes
Ah, that is why I've never seen this. After Import I select the batch of images and apply Auto +Sharpen+Clarity using Quick Develop, but I always then render the previews while the batch is still selected, before deciding whether to do anything else.

Bob Frost
Photo of Dmitry

Dmitry

  • 182 Posts
  • 52 Reply Likes
Why do you wait 2 years before you start to work on an issue? Is Adobe corporation still alive? Or you bankrupted possibly? What else reason can be for not fixing serious issues in your software for years?
(Edited)