Skip to main content
Inspiring
April 4, 2018

P: Crop tool showing last image (GPU on)

  • April 4, 2018
  • 68 replies
  • 2722 views

Have updated to LR Classic CC 7.3  Develop module when using the crop tool it shows the last image cropped for about 1 second before showing the current selected image.

68 replies

Inspiring
April 27, 2018


Kind of hard to describe. So I recorded my screen. https://youtu.be/vyhtoP_yZ4w

Basically when you crop a photo, it's all fine, but when you go to the next photo and select crop on that, it shows the previous photo, with the crop you had, then shows the next photos, with noticeable lag. I am not running a weak system, I have a 6 core/12 thread machine for video work running SSD's. This is a lightroom glitch that seemed to come up when the newer version came out.
chrisc25335006
Participating Frequently
April 26, 2018
Fixed for me in 7.2, then 7.3 broke it [7.3.1 still broken]. Now even going back to 7.2 doesn't work!
Fed up of being told to disable GPU, gone back to Capture One, won't be renewing my plan if not fixed.
JohanElzenga
Community Expert
Community Expert
April 25, 2018
Lots of bugs were solved with 7.3.1, but indeed not all of them. This kind of bug fix update is always a trade off between what gets fixed and how long it takes to release it. There were a few high priority bugs that needed fixing fast, and this one is just a glitch, so I guess they felt it could wait a little longer.
-- Johan W. Elzenga
Participating Frequently
April 25, 2018
New update..., same bugs 
Inspiring
April 25, 2018
Same cropping problem here. macOS High Sierra 10.13.3 on iMac 2017. Very annoying.
Inspiring
April 24, 2018
Same issue.  macOS High Sierra 10.13.4 on an iMac Pro.  
Known Participant
April 24, 2018
This issue is still not fixed in 7.3.1.
Known Participant
April 20, 2018
yeah, I prob will just wait, it isn't a big deal , just an annoyance. Not sure about the speed gain, since I went from a 2011 MacBook Air to this high-speed MacBookPro-it is wayyyy faster, for obvious reasons.
Known Participant
April 20, 2018

JohanElzenga
Community Expert
Community Expert
April 20, 2018
So don't disable it. It's just a glitch, nothing more.
-- Johan W. Elzenga