Lightroom: LR5 - unwanted synchronisation of picture parameters

  • 5
  • Problem
  • Updated 5 years ago
  • (Edited)
I have Lightroom Version 5.
Sporadic, but often, i have a little problem with LR5. Please see my Screencast on youtube: http://youtu.be/1vs_MFQyo98
I changed a few parameters on the fifth picture, click on the sixth picture and all parameters from the fifth picture was synchronized to the sixth picture.
I haven't used any Button or Hotkeys or whatever. See in the protocol box on the left side. This is empty!
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
  • frustrated

Posted 5 years ago

  • 5
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2657 Posts
  • 341 Reply Likes
I had this happen when I imported a sequence of pictures.

In my case, I click Auto Tone on the 10th of several hundred images and whenever I clicked on a picture to the 10th picture's settings were replicated to the new image. I finally removed all the images I had just imported, and re-imported them and it didn't happen, again.

Do you see this issue in LR 5.2 RC available from Adobe Labs or just LR 5.0?
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
Hi,
i have installed 5.2 RC, too. It is the same problem.
First try on the second picture. :(
In my first post it is release 5.

This problem is on every import. Re-Import doesn't help here.
additional information: i have cleared the history of all pictures at the beginning(!) of my test. It is better to see the problem.

Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 136 Reply Likes
I cannot reproduce this on Windows 7/64.
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
I have Win7 / 64bit, Intel i5 M560, 4GB RAM.
Can reproduce with my V5.0 and V5.2RC Installation.
Photo of Pete Green

Pete Green, Customer Advocate

  • 721 Posts
  • 136 Reply Likes
What happens in a new administrative user account David? Do you get the same behavior?
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
Yes, it's the same problem. This time was the third picture.
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
Anyone other idea?
My final images are also changed. I'm very frustrated.

LR5 destroyed my final/developed images! :(
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 336 Reply Likes
Have you:

Trashed your preferences file?
Redownloaded and reinstalled Lightroom?

Like the others, I have tried many times and I cannot reproduce.
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
- LR5.2 RC uninstalled
- trashed all lightroom directories (preference, catalogues, ...)
- reboot
- installed 5.2 RC
- copied old catalogue file
- same problem at the second picture :((
Photo of Pete Green

Pete Green, Customer Advocate

  • 721 Posts
  • 136 Reply Likes
David: Does it happen if you wait a second or two before switching images?
Could this be related to timing and the speed of your system?

The team is investigating this and is looking into fixing if we can track it down reliably.
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
YEAH!
I can reproduce my problem! :)

New Video/Screencast on Youtube and sorry for my terrible english: https://www.youtube.com/watch?v=nMF-xK...

I try to describe it:
all pictures have neutral settings and history is empty

1.) First picture is selected, change exposure to 2, field is active(!) and clicking in the filmstrip in the grey area under(!!) the second picture
The settings will be synchronisized. Failure!
History from second picture is empty.

2.) Third picture is selected, change exposure to 1,5, pressing escape, field is inactive, new history entry about this change is comming and clicking in the filmstrip in the grey area under the fourth picture. Nothing happens! Everything fine!

3.) Fourth picture is selected, change exposure to 1, field is active and clicking in the middle of the fifth picture within the filmstrip. Nothing happens! Everything fine!

4.) Fifth picture is selected, change exposure to 1, pressing escape, field is inactive, new history entry about this change is comming, and clicking in the filmstrip on the grey area under the sixth picture.
The settings will be synchronisized. Failure!

5.) Seventh picture is selected, change exposure to 1, field is active and clicking in the middle of the eight picture within the filmstrip.
Nothing happens! Everything fine!

The Edit field must be active and you must click in the grey area under the picture. I can reproduce this every time. I'm very confused. It does no matter how long I wait to select the next image.

Can you reproduce this on your machines?
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 336 Reply Likes
I still cannot reproduce using your instructions. I have tried on two Windows 7 Systems and Mac OSx 10.8.4.

What is the Drive and Path of your catalog?
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
oh, damned! :(
Catalogue is in Standard Path: D:\Users\forename.name\Pictures\Lightroom\Lightroom 5 Catalogue.lrcat

Windows 7 64 bit Service Pack 1
Intel i5 CPU M560 @ 2,67Ghz
4GB RAM
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
This issue is affecting me too, and is in serveral different threads that perhaps should be combined.
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 336 Reply Likes
Create a new user called TEST.
Create a new catalog while logged in as that user.
Does the behavior repeat?
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
Rikk -

I can't try that right now, but I suspect that a large catalog and a machine that is not too fast may be a factor. (I am running Win 7 64 too on an i7 and 8GB RAM) I can 't reproduce the problem all the time, only under some load and a backog of writes to the DB.
Photo of Arnold Bartel

Arnold Bartel

  • 191 Posts
  • 44 Reply Likes
I cannot confirm your assumption:
I had this behavior twice and I'm working on a brand new i7 (6 core) with 16 GB RAM.
But maybe an influencing fact is, if LR renders previews in the background.
Photo of Matt Gannon

Matt Gannon

  • 5 Posts
  • 0 Reply Likes
The issue seems to be limited to Macs. In my case, I get the bug where the settings are applied from one pic to the next if the field is still active, but I also get the issue where all settings are periodically copied over, even when a field is not active.

I have noticed that I see this issue on pics where I have performed upright correction. It nearly always happens on the next pic selected in the filmstrip after selecting auto, upright, level or full correction.
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
I have Win7 and the same problem. See the posts above you.
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
Me too on Win7 64
Photo of Matt Gannon

Matt Gannon

  • 5 Posts
  • 0 Reply Likes
More Detail: If I move to the right in my filmstrip (in Develop), all modifications are copied from one photo to the next, including the crop settings and vertical correction. It's like Auto Sync is enabled, but it isn't.

This is not the bug where just one setting is copied if the value is entered manually and the user clicks the next photo without hitting enter.

Literally, all the modifications are copied - including auto correction, exposure, crop, etc. This is a huge issue as I'm afraid to click through my pics.

I did not have this issue in LR5 Beta, only in LR5. I upgraded to RC 5.2 and the issue is still there
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
I can also confirm that the bug copies all develop settings. I also fear for my images. The slower I wait between images before moving the less likely this issue is for me. Do you experience the same on your Mac (I am Win7 64 as I mentioned)?
Photo of David Eckhorn

David Eckhorn

  • 10 Posts
  • 0 Reply Likes
yes, this is right. I have tested it only with one parameters (for screencasts). But it es very big problem. Absolutely all changes of the previous image are copied one to one to the next picture. :/
Without any entries in history and so on.
Photo of Matt Gannon

Matt Gannon

  • 5 Posts
  • 0 Reply Likes
This is exactly what happens to me. I have noticed it happens more if I move quickly from pic to pic. It's awful as it literally can wreck your catalog.

I had to retouch 300 pics the other day because of this bug.

I have a workaround for right now, I simply click the reset button every time I select a new pic for editing. However, this only works the first time you retouch the pic.

Is there any response from Adobe on this? Is there a real workaround or fix?
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
I feel for you, and have not heard much on a solution for Adobe. I have a big catalog (>150k images due to the way my images are used) I wonder if that is an issue for you too. I have a slightly better workaround for me. If I go back a few steps in the history and replay it forward the problem seems to go be fixed without the "big reset". Try that. Like you say it only works when you have only one occurrence of this bug. It has trashed several hundred images over the course of the summer. Talk about non-destructive editing. :-(
Photo of Matt Gannon

Matt Gannon

  • 5 Posts
  • 0 Reply Likes
So, how do we escalate to Adobe for a fix? Have they ackowledged the issue? I'm going to try your option of going back in the history and then forward. At least that's a doable workaround. I've had to use the "big reset" at least 20 times :( My library is big, but not huge. About 15GB of images...
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
It looks like the acknowledged this bug that seems to be the same:
http://feedback.photoshop.com/photosh...
Photo of Pete Green

Pete Green, Customer Advocate

  • 721 Posts
  • 136 Reply Likes
The bugs are likely similar, but slightly different behavior. We think we've tracked it down and are hoping for a fix to be in the 5.2 full release (not the RC)
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
Fantastic! Thank you so much. This has been a major stress for some of us!
Photo of Matt Gannon

Matt Gannon

  • 5 Posts
  • 0 Reply Likes
Pete - This is great news. Thanks! Is there any ETA for the 5.2 Release? Even a rough estimate is fine.
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
Note to moderators: There are at least three threads I am following that discuss variations on this issue. You may want to combine. They can all be found in my profile. One variation that may be important I opened has an actual error message: "An internal error has occurred: history step does not belong to instance" I feel this may be a key clue to finding the bug.

http://feedback.photoshop.com/photosh...
http://feedback.photoshop.com/photosh...
http://feedback.photoshop.com/photosh...
http://feedback.photoshop.com/photosh...
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled
LR5 Develop Module Settings Bug.


As you go from image to image using arrow keys in the develop module, the develop settings are sometimes erroneously "pulled" from the previous image. This changes the appearance of the image on screen but does not show in the history. This seems to happen more often when there are a large number of changes for LR5 to write back to the disk. I never saw this problem in LR4.
Photo of brandon himoff

brandon himoff

  • 28 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled
Lightroom Develop Module swaps develop information between images and gives error..


I get this error message often in LR5 and when flipping between images Lightroom mixes up deveop information between images. This is a very critical error for me:

An internal error has occurred: history step does not belong to instance

I can resolve the issue if I catch it by going back through the history and forward again. This did not occur in LR4. I am using Win7 64. It occurs most when the load in my system is high. The catalog I use is quite large (>150k images) due to my workflow, and this may be a factor.