This conversation has been merged. Please reference the main conversation: Lightroom: Applying Auto Tone to a batch of photos loses subsequent develop settings
This bug has been present since V3 and is still there in V5. Very tired of this as it kills my workflow.
Running v5.2 of Lightroom on OS/X.
Does it have something to do with the number of images selected?
There's not necessarily a pattern (i.e., it works for exactly 10 images) but when dealing with large sets of images, it happens consistently.
Perhaps this is a race-condition as I'm generally working in the "develop" tab while Lightroom is building 1:1 previews in the background - it takes some time given the number of images I'm working with and I don't wait for the previews to be generated before I start working on the images.
I just tried a sync of 100 photos with exposure pushed to the top (so I could notice if thumbnails were adjusted) and noticed that for some images it would take me clicking on the image to preview it before the change was reflected on that image.
Do your changes eventually take place?
Have you tried this process with a new administrator user on your computer?
I use OS/X not Windows. I don't recall this bug in v3, but it's certainly been there since v4 where I've just learned to tediously work through all images and not rely on trying to synch files. I'd hoped that the upgrade to v5 would have fixed it.
When you select one of the images that hasn't had the change applied and check the history panel, do you see auto-tone in the history list? As if it has been applied?
The Auto-sync not syncing may be a different issue from the auto-tone not syncing
The problems may be unrelated, but in general I have found that any task that is applied to multiple photos does not always get applied to all images.
From the user standpoint, the settings are applied to a photo, not to a representation of a photo at a particular degree of resolution. While at the implementation level this makes practical sense, at the UI level it causes confusion and inconsistency.
A simple fix I might suggest is to automatically "auto-tone" a higher-resolution preview when the history of the photo shows that the last operation performed was "auto-tone"; clearly it is the user's intention that this setting be applied and thus it makes no sense not to apply the setting once a higher-resolution preview is available.
I just did an experiment to test it.
1. In a folder of 380 photos, I applied settings to the first photo.
2. I then selected all photos
3. Synced all the settings, watched as the displayed thumbnails updated
4. Checked the photos that had updated thumbnails and the settings were correct.
5. On the last thumbnail that had been updated, I used the right arrow to go to the next photo. This was NOT synced.
6. Displayed the images in the folder in grid view (thus displaying around 20 images. Watched as these thumbnails updated.
7. Checked the settings on the images that had now updated, and these were correct (except the image I found before that hadn't updated).
8. On displaying the next image that didn't have its thumbnail updated, the settings were NOT synced.
9. Did this again with another 20ish photos, and the same thing occurred.
It seems to me that perhaps the routine that updates the develop settings is somehow incorporated in the function that updates the thumbnails?! It seems the settings are only updated AFTER the thumbnails are updated.
Therefore there seems to be a workaround, but going to grid view and waiting until all the thumbnails are updated (this might mean scrolling a few times if you have a lot of photos) before applying further changes.
ADD: I have just discovered that whilst the sync did occur after waiting for the thumbnails to update, some settings did NOT sync for all photos. For example, on the first batch that synced immediately Vibrance did sync (+10), but for all photos that synced after switching to grid view and waiting for thumbnail updates had Vibrance set at 0. This is unbelievably odd and makes me wonder how Lightroom is actually attempting to apply these settings.
Apply/synch settings does not apply to all images.
LightRoom 5.3 does not reliably apply settings to all selected images. If I have many images selected and attempt to apply or synchronize color adjustments to all images, LR will only apply to ~95% of the frames at any time. It requires applying at least 3 times to get all the images to accept the change.
When I apply settings to 300 images, I'm probably not going to actually view each image but make initial select choices from the thumbs. From a set of 300, I might actually select less than 10% to open in the Develop module and fine tune. I'd really prefer to get that job done as soon as possible and not have to be manually applying settings to each image or, worse yet, manually applying settings to all 300.
I understand that LR doesn't update the preview to reflect new develop settings of images not on screen to reduce the drag on the GPU/CPU. I don't agree with it but I understand it. (Perhaps a choice could be offered in preferences?). What I don't understand is why the metadata that should be applied when applying Auto Tone or synching settings is tied to the preview - so that we not only have to MANUALLY reveal and apply/synch in screen-sized batches but wait for our GPU/CPU to do the math before we can move on. I can't even do anything else while it's grinding away because, if I bring another app into the foreground (Mac, ElCapitan), the whole LR process stops and awaits my return. There are only so many coffees I can make in a day.
Could I suggest that the application of new metadata for develop settings be applied AS METADATA independently from applying the math and/or building an updated preview? This should make applying and synching develop settings very lightweight for the GPU/CPU, fast and not require images or thumbnails be visible for the changes to be made. Apply the metadata immediately, render stuff later.
Not only does synching develop settings across images still require all shots to be visible, not only does this still not guarantee all selected shots are updated, not only does the number of shots you can apply the changes to each time reduce, but now I'm finding that applying a preset to a single frame does not guarantee the settings will be applied.
I have had to deselect and reselect images and apply a preset two, maybe three times to get the preset settings to be applied. Not talking about the preview here, just the sliders to have changed in line with the preset.
My cache is set to 200GB, BTW, on a fast RAID with TB's of space.
I still wonder if these changes could be applied purely in metadata and the preview updated when you actually view the image. I understand that actions such as white balance pipettes and autotone require processing and therefore need the attention of the GPU/CPU but simply moving a slider to a predetermined setting should not.
1. Select all images in a large set (maybe 100+ shots)
2. Hit the AUTO tone button to have LR make auto adjustments
3. Enable AUTO SYNC
4. Change a slider value on a single image while all are selected
5. See that the change is made and is set for several images down the timeline
6. See that the change does not get applied (or is overridden by AUTO) further down the timeline. (bug)
Same issue with copy/paste settings with Auto Sync off.
I've tried many things for the autotone : on import, with a preset or with autosync in the develop module. To apply fixed values after that, I also tried many things : grid mode and auto sync. And with autosync, I tried by applying a preset as well as by syncing manually. I actually tried avery combination.
I even tried a fresh install on LR, with a brand new catalog with all my pictures freshly imported.
I tried with and without xmp metadata synced.
I'm running out of options.
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.