Skip to main content
Inspiring
June 27, 2014

P: Crop tool "jumps"

  • June 27, 2014
  • 16 replies
  • 884 views

Whenever I crop or straighten images in LR 5.5 my crop tool seems to jump into another "suggested" cropping. Then it jumps back to my cropping. This is very annoying and takes a lot of times when editing 1000+ images in a row ...
I hope there is help. I have seen this problem in a lot of other forums aswell but there is not solution yet. I guess it's a bug that needs to be solved.

Working on Mac OS X 10.9.3 (Server HD)

This topic has been closed for replies.

16 replies

Inspiring
July 15, 2014
It's something to do with the way it's caching the image, it will jump around between the original crop and the crop that you have made. It's very annoying. It's not having a poor video card or lack of power, I have the most powerful 27" iMac you can get with the fastest Nvidia card, and it still does it really bad. I hope they can work on this.
Inspiring
July 13, 2014
Same problem on iMAC and Windows 7, on both installed new CC 2014.
Participant
July 9, 2014
I have the same problem on a Windows 7 Machine. It seems to happen especially when switching from the library into the crop tool directly via the R shortcut with images that are already cropped. It then displays a crop frame overlaid on what should be the whole image, but instead the "whole image" displays the previously cropped image area for a short moment until lightroom corrects itself. Maybe the graphics card wrongly reuses the cropped image area for the entire image?

Anyhow, this is terrible if you are used to work at high speed because every crop has to wait for lightroom to catch up with the full image before you can get to work. Please fix ASAP - thanks!

Machine Specs: Windows 7 64 bit, Nvidia GeForce GT 640 w driver version 337.88, 16GB Ram, Lighroom 5.5
Inspiring
July 6, 2014
same problem here.
Inspiring
June 27, 2014
Thank you so much! I really hope this gets solved very soon!!!
RikkFlohr: Inactive
Inspiring
June 27, 2014
I see this in Mac. I have checked. A bug has been reported in Windows already. I have added the Mac OS to the bug as well.