Lightroom Classic: After adjusting on one image, the exact edits for that image, masks and all, were applied to all other images

  • 1
  • Problem
  • Updated 3 weeks ago
  • Solved
  • (Edited)
When using Lightroom Classic for the first time since upgrading to MacOS Mojave, I noticed that after adjusting on one image, the exact edits for that image, masks and all, were applied to all other images, thereby ruining all previous edits on those other images - many lost hours of work.
Photo of Thomas C. A. Brevik

Thomas C. A. Brevik

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 3 weeks ago

  • 1
Photo of Carlos Cardona

Carlos Cardona

  • 296 Posts
  • 58 Reply Likes
Maybe you accidentally hit Com-A and selected all? Darker grey not selected, middle Grey selected, bright grey the active shot.
Photo of dmeephd

dmeephd

  • 152 Posts
  • 35 Reply Likes
Oh boy, that's a killer if true.  I am in LR 7.5 with Mojave right now.  I will attempt to replicate.

When you state "...all other images..." what exactly are the parameters?  Everything in your catalog, or the current working folder or collection?
Photo of Thomas C. A. Brevik

Thomas C. A. Brevik

  • 3 Posts
  • 0 Reply Likes
There were a whole "Synchronize Local Adjustments" in the History, so I suspected multiple selected images as well. And I did discover after trying to replicate that at some point all the images in my Smart Collection were indeed selected, but not on purpose. So, thankfully it was a case of some editing steps done on multiple images, that were unintentionally selected. I am always careful to avoid this, unless in the selection process (N). (I was able to backtrack wrongful edits on the other images,)
Photo of Tom Mickow

Tom Mickow

  • 302 Posts
  • 101 Reply Likes
1 - Could be wrong, but I don't think Mojave is officially supported yet, so you're putting yourself in a bit of a use at your own risk situation.

2 - Any chance you had multiple images selected and Auto Sync turned on?  That would explain the behavior you described.


3 - You should be able to go to the History panel and step back the changes to your image(s).  Not the best solution if you changed tons of images, but still workable.
Photo of dmeephd

dmeephd

  • 152 Posts
  • 35 Reply Likes
If Mojave isn't officially supported yet, what in the heck has Tom Hogarty and his band of merry misfits been doing these past months?  (Frankly, Tom should have been axed after that disasterous October 2015 relase of LR.)

If it weren't for Apple adopting PostScript fonts back in the day, Adobe and John Warnock would have been relegated to the dustbin of history.

John, you're still on the Board of Directors of Adobe.  Perhaps you need to drop a few floors down from the ivory tower and kick some Adobe butts.  There is no excuse for Adobe to not be in-the-loop with the development of an Apple Mac OS and be ready for prime time well before the release.
Photo of john beardsworth

john beardsworth

  • 1080 Posts
  • 254 Reply Likes
It doesn't help the OP to ramble on about irrelevancies like OS support or late 1980s graphics tech, does it? It's even harder to see its comedic effect. The OP probably did something as basic as hitting Cmd A or had AutoSync enabled, there is a CmdZ or CtrlZ undo, and what's actually missing is the ability to select multiple images and move back through the history steps.

Photo of Anthony Blackett

Anthony Blackett

  • 68 Posts
  • 26 Reply Likes
What is really missing, and has been since the day LR 1.0 was released, is being able to edit the history panel. By that I mean having the ability to:

- click on a history step and delete it (or click n drag off the panel to bin it)

- click n drag a history step to move it to another positon in the history order.

- select multiple history steps of the same adjustment (eg. exposure) and combine them into one step repesenting the final adjustment value.

After all, the LR adjustments are simply pieces of data recoded in the catalogue database and should be easily maniplated by the LR software.
Photo of dmeephd

dmeephd

  • 152 Posts
  • 35 Reply Likes
Agreed.  And if LR was based upon a true relational database with full referential integrity, then we would not have these problems.  But Adobe took the cheap way out, using a free SQLite instead of something else.

It's all about profits, not customer satisfaction.
(Edited)
Photo of john beardsworth

john beardsworth

  • 1080 Posts
  • 254 Reply Likes
No, History is simply a chronological record of what you did (calling it the History Log might have been less misleading) and chopping out, moving or consolidating history steps isn't much more relevant to the OP's problem than imagining he would be helped by a paid-for relational database instead of Adobe using the same robust engine that  Apple also chose for Aperture. The OP's problem appears to be making the same change to multiple images, and that is resolved ideally by Undo, and afterwards by allowing the user to select multiple images and go back one step at a time. FWIW, a SQLLite-hacking plugin once did this.


Photo of Carlos Cardona

Carlos Cardona

  • 296 Posts
  • 58 Reply Likes
The poor guy had autosync on and watch out! Adobe haters gotta hate! Chill peeps! It’s not always Adobe’s fault, you know!
Photo of dmeephd

dmeephd

  • 152 Posts
  • 35 Reply Likes
True, but more often than not it is their fault based upon the numerous bugs in the LR 7.x releases...and Adobe's lack of effort to address issues which have been known for years. Read the posts in this forum where Adobe actually acknowledges the issues.  They are there.  Period.

It's one thing to make your living as a pundit or an author of Lightroom help texts and another to be a professional photographer who places their livelihood in Adobes' hands and sees no improvement from one realease to another.

Every hour I spend working around Lightrooms' faults costs me money, so please forgive me if I tend to look in the direction of Palo Alto when I want to discover the source of the problem.
Photo of Carlos Cardona

Carlos Cardona

  • 296 Posts
  • 58 Reply Likes
Maybe it’s not Adobe’s lack of effort, maybe they’re trying real hard, all the time. Not being a coder, I don’t really know how hard it is to make a huge program that sits on top of a huge operating system, but I’m guessing it’s real hard so I cut the bugs some slack. I have worked with coders, and I know their work ethic and pride. As a Mac IT Pro for 25 years, I don’t seem to have as much a problem as some people on this board, because I know sometimes the problem is with the operating system, (or the user!) and I’m always doing updates and maintenance (like with your car) and therefore not always Adobe’s fault. That being said, I know how lousy their Creative Cloud authentication servers have been over the years, so that must also be hard to get right. Some of their employees are photographers too, and they are in the “making money” business, so they sometimes have to make tough choices.


PS- I’m now a pro photographer who relies on Lightroom, still the best organizing/developing tool. I just need 64GB now to make it work well!
(Edited)