Unexpected behavior with AutoSync

Report · Nov 23, 2023

Just when things couldn't get more unsuable for professional photographers. The 2-year Auto sync bug is back!

I posted about this bug for over 2-years before it was "addressed" in a recent update (13). I had spotted it happening a couple of times after said update but was unable to replicate whilst screen recording, until now....

Same as before, when auto sync is selected and multiple images are selected for syncing, adjustments to entirely unrelated aspects of the develop module will elicit adjustments to elements of an image like filters (in the case of the screen recording, a graduated filter) across all images.

A "collection ruining" bug if you're not well versed with the plague-like bugs of Adobe Lightroom Classic.

In the case of the screen recording, with auto sync selected, I made an adjustment to the Orange Hue of an image intented to be synced across the entire collection, when in fact the graduated filter of that image was then synced across all images. As you can see in the history, the last few adjustments were to Orange Hue, Temp, Tint and a radial filter. Nothing to do with a graduated filter.

Report · Nov 27, 2023

Here is the original Auto Syn Crop Issue in action. Same behaviour but instead of crop being synced we now have filters being synced when unrelated adjustments are made.

Report · Nov 26, 2023

@Rikk Flohr: Photography can we please give this thread a better title. The current one bears no relevance. This issue is connected to the "auto Sync copies previous crop.....etc" issue.

https://community.adobe.com/t5/lightroom-classic-bugs/p-auto-sync-copies-previous-crop-from-before-a...

Report · Nov 27, 2023

I have a catalogue of my own work standing at 140,284 images currently. I have had no other issue with the catalogue and trust me, being a Lightroom user of 8 years I'm very familiar with corupt catalogues.

I also edit other New Zealand wedding photographers images as a contractor opening multiple catalogues a week and see the exact same issue with anyone using LR 13+

I'm also running an M1 MAX macbook pro (see pic)

If you are not having issues with the below (I don't think you viewed my previously posted links) then you are not on the msot recent version of Lightroom as it is affecting 100% of users.

https://community.adobe.com/t5/lightroom-classic-bugs/p-unable-to-advance-to-the-next-photo/idc-p/14...

I, like all the other users in that thread do not use smart previews currently as it's not possible to use Lightroom with smart previews due to this bug.

Do some reading, do some reasearch, update your lightroom and then come back with some "expert" advice.

I think I knwo exactly who you are and what your motive is and you're not fooling anyone 😉

Report · Nov 27, 2023

If you are not having issues with the below (I don't think you viewed my previously posted links) then you are not on the msot recent version of Lightroom as it is affecting 100% of users.

https://community.adobe.com/t5/lightroom-classic-bugs/p-unable-to-advance-to-the-next-photo/idc-p/14...

I, like all the other users in that thread do not use smart previews currently as it's not possible to use Lightroom with smart previews due to this bug.

I read those links indeed and no I have never seen that bug since I never use smart previews. I am on 13.0.1 for sure. I don't use smart previews and haven't for many years because they degrade performance tremendously. I don't get why anybody would use them except perhaps if you are editing catalogs for other people where they only send smart previews along. I don't do that kind of work though and It is a stupid bug and Adobe should have caught that.

Do some reading, do some reasearch, update your lightroom and then come back with some "expert" advice.

I think I knwo exactly who you are and what your motive is and you're not fooling anyone 😉

As said, my Lightroom Classic is fully up to date and my only motive is helping people on this forum. I wish I could reproduce this as the more people reproduce stuff like this the more likley it is it gets fixed.