Skip to main content
Adobe Photoshop Family

26 Messages

 • 

436 Points

Tue, Jun 12, 2018 8:40 AM

Lightroom: Previous image appears when cropping; MIDI2LR very slow

Hi
I have noticed two bugs from the last release of LR CC
- when cropping a new image during half a second the last crooped image appears before that the one I want to crop now appears.
- I work with a midi control panel with the plug-in Midi2LR. It cannot be used anymore because of a dramatic slowdown into the delay between the action on a button and the result on the screen (1-3 seconds which is not manageable)

thanks for your feedback

Responses

Champion

 • 

3.3K Messages

 • 

58.1K Points

3 years ago

The first one is a known bug. Adobe is working on a fix, but a work around is to go to Preferences - Performance and turn off the use of the graphics processor.

Johan W. Elzenga,

http://www.johanfoto.com

26 Messages

 • 

436 Points

Thanks 
i did what you suggest and that's ok
what about the second bug ? any idea ?

Champion

 • 

5.5K Messages

 • 

97.2K Points

3 years ago

It's much better to post one issue per topic (thread), otherwise Adobe and others are much less likely to pay attention.

Re cropping, be sure to click Me Too and Follow in the upper-right corner of this bug report: 
https://feedback.photoshop.com/photoshop_family/topics/lr-classic-7-3-crop-tool-showing-last-image

That will make it a little more likely Adobe will prioritize a fix, and you'll be notified when the bug's status changes.

26 Messages

 • 

436 Points

done
thanks

Champion

 • 

5.5K Messages

 • 

97.2K Points

3 years ago

Re MIDI2LR: It's a third-party plugin, and you're much more likely to get help from the developer's web site and forum:
https://groups.google.com/forum/#!forum/midi2lr

26 Messages

 • 

436 Points

i did it
they say it is an Adobe issue
it is true that it stopped working properly after the last LR CC update

Champion

 • 

5.5K Messages

 • 

97.2K Points

Based on years of experience as a plugin developer, I can say that Adobe will likely only pay attention to this issue if the MIDI2LR developer posts a bug report here with a precise recipe for reproducing the problem. I haven't seen any such post yet. (I'm not justifying Adobe's behavior, just observing the reality.)