Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

The last done edit is not Copy and Pasted if done with Keyboard or SDK API

Explorer ,
Oct 19, 2025 Oct 19, 2025

When I hover with mouse above a Slider, and use the Keyboard up/down arrows to adjust its value, and once happy with the value press Cmd+C, confirm the fields to be copied by pressing Ok, move to the next image and press Cmd+V, all Settings of the previous image are copied, except the last made change with the Keyboard. 

 

The isse is identical if I use a plugin to change the value. Like the Elgato Streamdeck Plugin by SideshowFX, that makes a call to the SDK function LrDevelopController.increment(key) or LrDevelopController.setValue(key, valueto change the value. The behaviour is exactly the same. The last value is not copied, but the value done one step earlier is. For instance, if I adjust Temperature, and then Brightness, followed by a Copy+Paste action, the Brightness value change will be ignored, but the Temperature change will be copied. 

 

If I however use the mouse to make the Change by using the Slider, Copy and Paste works as expected. 

 

This is a Bug that has been present and plagueing me since I'm rather certain Lightroom V1 from 2007. For me, it is the most annyoing and time killing Bug that I am personally facing in Lightroom. It triggers me every single time I use lightroom since 18 years. 

 

I'm finally taking my time to file a bug report, because I've come to accept this bug wont ever magically disappear. I'd be forever greatful if this bug would finally get tackled. Lightroom would be so much more fun to use, If I didn't constantly have to go back and forth images repeating Copy and Paste action because the last done edit hasn't been taken, or proactively do weird combo key presses to avoid this happening, because this bug is really really present in my mind when I'm editing. It's really a huge rock blocking my otherwise very speed workflow, and it's been there since so many years. 

TOPICS
macOS , SDK , Windows
279
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 19, 2025 Oct 19, 2025

Hmm, I'm not observing that in my LR 14.5.1 / Mac OS 15.7.1, when I follow these precise steps (see the attached screen recording):

 

1. Click on the first photo in the filmstrip.

 

2. Hover the mouse over over the Temp slider.

 

3. Use the up-arrow key to increase Temp.

 

4. Hover the mouse over the Exposure slider.

 

5. Use the down-arrow key to decrease Exposure.

 

6. Type Cmd + C to open Copy Settings and observe that Basic is already selected.

 

7. Type Return to close Copy Settings.

 

8. Used Cmd + right-arrow to move to the next photo in the filmstrip.

 

9. Type Cmd + V to paste the settings. Observe that the values for Temp, Tint, and Exposure from the previous photo are correctly pasted into the current photo.

 

I get the same correct results if I use the mouse to click on the Copy button in step 7 and use the mouse to move to the next photo in step 8.   

 

1.  Do you see the misbehavior when you do these exact steps? 

 

2. Do Help > System Info. What are the exact version numbers of LR and Mac OS you're currently running?

 

Unless Adobe can easily reproduce the problem, they're not going to pay much attention, unfortunately.

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 20, 2025 Oct 20, 2025

Hey John, 

thanks for following up. I've made a screen recording as well. Indeed, on the first try after I read your post it did not happen, I went ahead and tried again: it happened. In the screen recording I am attaching it's happening most of the time, but not every time. 

 

I am running LR 14.5.1 and mac os 15.6.1, but as I said: this is not a new issue, it's been haunting me since the very very early days of LR, and I've been using it since V1.0. I am honestly puzzled this is not a known thing because I'd put my hand in fire: I do not remember any time this has not been plaguing me, and I'm having a very hard time to imagine it's only me. I am pretty sure this an issue that has it's core in some lower level code of the LR UI that has been untouched ever since it was released. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 20, 2025 Oct 20, 2025

I just called a colleague and was able to confirm: on his windows machine it does not happen, but on his mac he is able to confirm the problem. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 21, 2025 Oct 21, 2025

Your video clearly shows the misbehavior.  I tried for several minutes reproducing those steps in my Mac LR 14.5.1 and the bug isn't occurring in my LR.

 

Perhaps Adobe will file a formal bug report internally, but usually, if an Adobe employee can't reproduce the problem, it won't get acknowledged (unless many people report it).

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 26, 2025 Oct 26, 2025

Wow, this is very surprising. Like I said: I've never not had this issue. Multiple different computers, every now and then started a fresh os install. Multiple Catalogs. All the OS X/MacOS and LR versions, *never* not had this problem. 

 

I'd be very happy to give access to my system to adobe engineers if they want to check it out. It is the single most PITA and I'd be immensly happy if this would finally get looked at. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Oct 28, 2025 Oct 28, 2025

There is a known very rare problem with the Ui.

Checkboxes appear ticked BUT then those settings do not get copied...or rather the last copied settings are used.

Might be a problem with the scope not being updated.

 

Do "Check None" then tick again the checboxes you need.

 

Pasting should work after that.

 

Is rare but it happens.

 

P.S.

I can't understand what you are doing in the video.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2025 Oct 30, 2025

Thanks for chiming in Cella. 

I'm doing exactly what I described in the reproduction steps: i hover over a setting, change it using keyboard, press cmd+C, hop to the next image using the arrow key, hit Cmd+V and repeat that multiple times. If it helps get this issue fixed I'm happy to record a yt video describing the issue as best as I can. But it's really just what I described. 

 

I'm also not very certain about your suggestion. I've spent quite some time about thinking how this could possibly make sense. It may somehow, but it would be extremely odd and point to pretty severe problems on lower levels in the LR UI Code, which would kind of make sense considering the age of the problem. But since I basically never change the options in the copy window it would be extremely odd, that only the last changed item would "appear checked but be unchecked". And if true seriously problematic. 

Also the problem for me is not rare at all. In a 1 on 1 session with a developer I'd be able to reproduce it no problem at all within minutes. 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Oct 30, 2025 Oct 30, 2025

You might be copying copying too fast.
Try doing 

1. Cmd + C
2. UI shows up
3. Wait a second

4. Enter to copy the checked settings
5. Next image
6. Cmd + V

Aside for this suggestion I can't reproduce your issue.

.I don't copy settings as fast as you do and neither does @johnrellis 




Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
20 hours ago 20 hours ago
LATEST

 

quote

You might be copying copying too fast.

By @C.Cella

 

I've just tried trying to work slower, the problem is the same. The UI shows up fully. Even if I wait for a few seconds longer the problem is the same, and frankly: even if I worked too fast for lightroom, it would still be a bug. 

 

I've asked a few colleagues working with the same setup and all are able to reproduce the issue no problem at all.

 

I'd like to reinforce my offer to work with an adobe engineer via remote connection to try and pin down the problem and see if we can find a solution. 

 

The problem unsurprisingly persists in the latest release of lightroom. I'd really really like to tackle this. This is a major handbrake when working with lightroom. Yes, I've waited 18 years with reporting it, but I'm not going to give up now running against a "can't reproduce" wall. I'm not making this up.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines