P: Crop tool showing last image (GPU on)

[FeedbackCommunityMember]

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.

[99jon]

I am seeing this on Windows 10 although it is so momentarily that I needed to look closely to see it when pressing the R key. It doesn’t appear to affect the working of the crop tool but it looks like a bug as it was not happening in v7.2

[FeedbackCommunityMember]

I'm using a Mac OS High Sierra  10.13.3 definitely 1/2 to 1 second at the moment, yes was ok in V 7.2

[FeedbackCommunityMember]

this is been answered here https://forums.adobe.com/message/10291246#10291246 

[99jon]

Yes the problem also goes away on W10 when disabling GPU. But it was working correctly in v7.2 with GPU enabled. But thanks for bringing it to attention.

[FeedbackCommunityMember]

MacBook Pro, latest OS - the same problem. 

[FeedbackCommunityMember]

I believe it was never really gone, only much shorter before 7.3. This has now been around since early version 6 (just based on memory...). So, there should have been enough time to really solve it.... 

[Drugstore]

Same here!

[Ester5ECF]

A couple bugs were introduced in the newest version of LR - this problem is happening as of 4/11/18. When you click R to go into the crop menu LR flashes the last images first before showing the image you're on and want to crop. This happens all the time. Last cropped image displays for just 1-2 seconds and then LR shows the image you're actually trying to crop.


Another issue - presets are sorting incorrectly. If you rename a preset it should be showing in the folder, alphabetically, but it goes to the bottom of the folder. This might be just a glitch, but no matter how I renamed the preset (tripped checked all spacing and spacing between dashes and numbers, etc. the preset would still not fall into place where it was supposed to be).

Lastly, please give us a way to delete all default LR presets!!!!!!! I have no reason for any of those, and seems like Adobe has just increased the number of all the presets that are showing, which is taking up too much room on the left-hand side menu where I want my own presets to show. I (and all the users that have been asking for this for YEARS on the Adobe forum) want the ability to delete all default LR presets. I don't need them!

[waynem10146058]

"Upgraded" to Lightroom Classic. Now when I click on the crop tool the previously edited photo flickers and is then replaced by the current photo.

I spent over an hour between waiting for Customer Support chat and then debugging.

His solution was to turn off the GPU. This is a bug that Adobe introduced between version 17 and 18.

Got testy when I insisted on a bug report.

[Kanikas]

Moving to Lightroom Classic CC — The desktop-focused app​

[johnrellis]

Please add your details and constructive opinion to this bug report in the official Adobe feedback forum: Lightroom Classic 7.3: Crop tool showing last image (GPU on) | Photoshop Family Customer Community . Be sure to click Me Too in the upper-right corner. This will make it a little more likely Adobe will prioritize a fix, and you'll be notified when the bug's status changes.

[AviMathur]

Hello waynem10146058   ,

Thanks, for sharing this. I would like to tell you that we are aware of this issue and are working on a fix. Please be patient and thank you again for you enthusiasm on reporting this.

Looking forward for more feedback from you.

Thanks,

Akshay

[Arizona Bev]

I am experiencing the same things described by eknowlen, above.  The crop tool problem started with the previously cropped image flashing for a second or two before the one you are working on appears.  That has been going on since upgrading.  HOWEVER, tonight it started leaving the previous image up there permanently.  I cannot crop the image I want to crop!

FWIW, before this latest development (of the previous image staying there, not merely flashing in view for a couple of seconds), I had been using Transform and selecting Constrain Crop.  I don't know if that had any bearing on the issue or not.

Tried closing and restarting Lr.  No help.  Problem remains.

[JohanElzenga]

Preferences - Performance - turn off 'Use Graphics Processor' should solve this.

[CCS18]

Thank you...about to roll back because it's driving me nuts.  That and the pre-set thing, which is even worse for me because I name my key presets with a ~ to start it, and that now makes the preset disappear! Ugh....

[Jose Paredes]

For sure... a few month before this bug is solved.

[mikep66956846]

MacBookPro v7.3 same problem using crop tool. Will disabling GPU have any negative effects?Thanks.

[Arnie47]

The use of the GPU can accelerate any operation where massive parallel computing is needed.
As LR is facing performance issues and sometimes non responsive user interface or delays, the use of the separate GPU for calculation intense operation should help.
So it is very sad, that the us of the GPU causes many many issues (black screen, delayed display, ...) and Adobe often recommends to disable GPU support as a workaround cause this inevitably leads to worse performance.

[JohanElzenga]

No, you won't see any negative effects. In theory some operations might be slower, but in practise I doubt you will notice much difference on a MacBook Pro.

[mikep66956846]

I agree. I specifically bought the 15 inch MacBookPro for the dedicated GPU specifically for LR! I  am really loath to disable it. 

[mikep66956846]

Hm. It's just that  I specifically bought the 15 inch MacBookPro for the dedicated GPU specifically for LR, after reading about GPU acceleration and how great LR would be since it could now take advantage of it. 

[JohanElzenga]

And did you see a spectacular speed gain? Mind you, that crop tool glitch is just that; a glitch. It takes a second or so and then the crop tool shows the correct image, so you could leave GPU on and live with it until Adobe fixes it.

[JohanElzenga]

So don't disable it. It's just a glitch, nothing more.

[mikep66956846]

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.