FAIL: Lightroom Classic 7.0.1

  • 5
  • Problem
  • Updated 10 months ago
Merged

This conversation has been merged. Please reference the main conversation: Lightroom Classic CC 7.0 and 7.0.1: Memory leaks and progressive slowness worse than prior version

Hello, I too have seen major performance degradation since upgrading to Lightroom Classic 7.0.1 ala Mac Sierra 10.12.6.

I'm a real estate photographer, and I've been a pro user since Lightroom 3.  The biggest increase in performance I noticed was the ability to create many HDR's at once.  Better memory allocation to that task I suppose.  However, overall the product has more degradations than improvements.  Can't even edit a basic 40 gb shoot.

Here is a list of issues I've experienced.

1. Import issues:  File corruption, and very degraded import speed.

2. Major Lagtime between mouse movement and cursor on the screen, while in develop mode.

3. Inconsistent behavior when creating panos and hdrs.  The new file created sometimes ends up at the end of the files sometimes placed with the originals. NO consistency in this function between catalogs.

4. WB/Temperature seems off. No consistency.

5. Lens correction always needs more correcting. Essentially useless.

6. Is it me or has anyone else notice more noise issues than usual?  I see more noise in my images than with older versions.

7. Just switching images in the film strip (dev. Mode) is painfully slow. So much so, it renders LR useless in meeting deadlines.

8. As usual, poor and generic documentation that is hard to find and access.

9. Inadequate feedback/reporting system for issues.

10. Adobe clients have to work their asses off to solve problems and troubleshoot.  Should be easier.

11. Adobe Classic: Just confuse my workflow some more and add more steps.  That should help our company add dollars to the bottom line (not).

NOW may be the time for me to forever ditch LR.
Photo of Dave Hall

Dave Hall

  • 6 Posts
  • 3 Reply Likes

Posted 10 months ago

  • 5
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2647 Posts
  • 337 Reply Likes

3. At least in the past, Panos/HDRs at the end vs with originals is due to the sort order.  By filename is with originals, by date is at the end.

Photo of Reinard Schmitz

Reinard Schmitz

  • 55 Posts
  • 7 Reply Likes
Indeed, I expected more than degraded speed and more mistakes after two years paying 12 € every month. I can't understand what's going on at Adobe. What we need is competition...
Photo of Gary Rowe

Gary Rowe

  • 91 Posts
  • 33 Reply Likes
And what we are NOT getting for the money we've been paying is a better version of Lightroom :-(
Photo of David Martin

David Martin

  • 16 Posts
  • 11 Reply Likes
I refused to upgrade to this "release" after the October disaster of 2015.  And I am so glad I deferred after reading all of the problems users have seen, especially on the Mac platform.

Tom H. needs to resign from Adobe immediately.  He should have quit in 2015.  This version os a world-class POS, and I will never commit my 2.4 million images captured over 40 years to this crappy appication.

I too am looking elsewhere.  And there wilbe an elsewhere.  If software development has taught us anything over the past 20 years, some bright bot (or girl) comes along with a far bette rmousetrap and the old tyrant falls down hard.
Photo of Reinard Schmitz

Reinard Schmitz

  • 55 Posts
  • 7 Reply Likes
Would like to read here what's an alternative to LR when you need the map and the organising features – there is none, that's the problem and they know it. With our money they payed the development of a new product no professional really needs.
Photo of Shane Betts

Shane Betts

  • 160 Posts
  • 54 Reply Likes
I'm starting to wonder if the speed up in Classic is purely a result of the catalog being updated for the upgrade and, after a few weeks, the new catalog gets gunked up like the old one and we're back to square one.
Photo of Shane Betts

Shane Betts

  • 160 Posts
  • 54 Reply Likes
BTW, Dave Hall, go back to 7.0.0. I found 7.0.1 is practically unusable on Mac for me.

This conversation is no longer open for comments or replies.