Lightroom Classic: Library Module - grid and strip no longer synchronized

  • 8
  • Problem
  • Updated 6 months ago
  • (Edited)
Clicking on the thumbnails in Library module, the main grid view and the strip view below are not synchronized any more, so clicking on the strip no longer actually selects an image, and clicking on the grid does not update the selected image in the strip.
Photo of Larry Brandt

Larry Brandt

  • 3 Posts
  • 1 Reply Like

Posted 7 months ago

  • 8
Photo of John R. Ellis

John R. Ellis, Champion

  • 3382 Posts
  • 853 Reply Likes
Try resetting LR's preferences: https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/. Sprinkling that magic fairy dust often fixes things when LR's user interface goes wonky.
Photo of Larry Brandt

Larry Brandt

  • 3 Posts
  • 1 Reply Like
I closed and re-opened Lightroom and it seems to have sorted itself out. Bug occurred originally after making a Metadata filter for ISO speed, and it did not resolve itself until the re-open, so possibly still some kind of bug.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3214 Posts
  • 795 Reply Likes
Definitely a bug. Rebooting the computer, restarting LR, and/or resetting preferences often fixes weird behavior. This has been true for years, suggesting some significant underlying flaws in LR's architecture.
Photo of Tanja Schulte

Tanja Schulte

  • 115 Posts
  • 42 Reply Likes
i had this bug too... does not happend often but after some heavy importing or mass editing of keywords.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3370 Posts
  • 844 Reply Likes
Does it go away for you immediately after restarting LR?
Photo of Larry Brandt

Larry Brandt

  • 3 Posts
  • 1 Reply Like
Yes, problem closed as far as I'm concerned, though it's obviously still a bug
Photo of John R. Ellis

John R. Ellis, Champion

  • 3370 Posts
  • 844 Reply Likes
Tanja, what about you?  Does restarting LR make the problem go away immediately?

The bug is not closed -- restarting is just a possible workaround.
Photo of Kenneth Seals

Kenneth Seals

  • 1 Post
  • 0 Reply Likes
This un-synchronized issue happened to me this morning after importing 950 photos. I had done the initial cull with photomechanic, so the PM xmp files are present.  I restarted LR CL and the problem went away. 
Win 10 Creators, 
Photo of John R. Ellis

John R. Ellis, Champion

  • 3214 Posts
  • 795 Reply Likes
Please also click the ME TOO button in the upper-right corner.
Photo of Graham Washatka

Graham Washatka

  • 1 Post
  • 0 Reply Likes
I was experiencing this same problem. After restarting LR the issue is gone, but it seems likely it will be back again.

Maybe this is happening after a new Import has been done? I'll try to report back with when this is happening.

- Graham
Photo of Cees Wouda

Cees Wouda

  • 14 Posts
  • 1 Reply Like
Same problem here. Specifically after start op of computer and then start up of Lightroom and subsequent import. Rating assigned in loupe view seems to get assigned only to the first picture of the import. From loupe view switching to Develop also brings up de first picture instead of the picture I am looking at. Closing down Lightroom and restart brings everything back to normal. Also the next import behaves ok. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 3382 Posts
  • 853 Reply Likes
Adobe employee Simon Chen provided this workaround for similar symptoms: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-bug-filmstrip-no-longer-... Please report back here whether it works or not for you (to help others).
Photo of Bhargav

Bhargav, Official Rep

  • 33 Posts
  • 7 Reply Likes
Hi Larry,

Try this workaround to see if it works for you. If not, delete the config.lua file afterwards.

  1. Choose Edit > Preferences.
  2. In the Preferences dialog, go the Presets tab.
  3. In the Presets tab, click the Show Lightroom Presets Folder button. The root preset folder opens in the File Explorer. 
  4. In the File Explorer, navigate into the Lightroom folder.
  5. Go to the link https://adobe.ly/2hUHGYa and download the config.lua file. Copy the downloaded config.lua file into the Lightroom folder mentioned in the previous step.
  6. Relaunch Lightroom Classic CC.
The System Info dialog (Help > System Info) should display the config.lua flags entry as shown below:

Config.lua-Flags:
AgView.disableDirect2D = true

Thanks,
Bhargav
Photo of John R. Ellis

John R. Ellis, Champion

  • 3284 Posts
  • 818 Reply Likes
Is that any different from the workaround posted by Simon Chen?
Photo of ross

ross

  • 7 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom Classic: Wrong image(s) displayed in Library module's filmstrip after R....

I have been using Lightroom CC (now Classic) for years and have always been plagued with this problem in my workflow. Surely, I have thought, someone else must have experienced the same issue, reported it and a fix will be forthcoming shortly. Alas, none of this seems true.

I want my photos named for the date and sequence that they were taken. I also don't want to keep all of the photos that I take. My rename & cull process is iterative using the Library module. First I rename all of my photos, then I cull, rename and repeat. Typically, I work in Loupe mode.

The problem is, after these rename operations, some of the thumbnails in the filmstrip are wrong! That is, they reflect different images. This is really bad in my workflow as it can cause me to remove photos that I did not intend to!

Perhaps the problem stems from the fact that, because of the sequenced rename operation, some kept images assume the names (sequence numbers) of some removed images. Regardless, this is certainly a bug. After a rename operation, thumbnails in the filmstrip should properly reflect the images that they are supposed to represent.

Eventually, things get back in sync. Unfortunately, I have no idea what operations it takes to do so. Of course, it should just happen automatically. I have tried Save Metadata and Synchronize Folder operations but they don't always work.

Please help. I am tired of culling good images with the bad.
Photo of ross

ross

  • 7 Posts
  • 0 Reply Likes
I don't know why my topic ...
Wrong image(s) displayed in Library module's filmstrip after Rename Photo(s) operation
... was merged here.
I think that these are two very different issues - mine being much more serious in that the UI suggests that you are selecting one image when you are actually selecting a completely different one.
This is a terrible mistake when made as part of a workflow that deletes images!
Photo of John R. Ellis

John R. Ellis, Champion

  • 3292 Posts
  • 820 Reply Likes
The original poster experienced the same problem: The image shown selected in the grid wasn't the image he clicked on in the filmstrip.   So he thought one image was selected but in fact another one was.
Photo of Chinoy Gupta

Chinoy Gupta, Employee

  • 23 Posts
  • 8 Reply Likes
Hi,

Can someone post a snapshot or a screen recording while this issue is present.
Photo of ross

ross

  • 7 Posts
  • 0 Reply Likes
I found a way that I can (relatively) reliably recreate this problem with my source pictures. I have found that I can do this with three different sources. They have been both Lightroom exported JPG images (2) as well as Canon raw source files (1).

1. Copy 8 pictures from a previous project named, from the start of the same day, with the pattern YYYYMMDD.NNN, where YYYY is the year, MM is the month, DD is the say and NNN is a sequence number to a temporary (empty) directory. This is the way my Lightroom is (custom) configured to rename things.

2. Launch Lightroom, go to fullscreen mode (this makes a difference for me sometimes) and import this directory by  Adding the images.

3. Reject every other one (starting with the first) from the filmstrip (X) and delete them (CTRL-BACKSPACE, delete).

4. Select them all (CTRL-A) and rename them (F2) all with the same pattern.

5. Things look correct in the filmstrip until you click on the second one whose image then changes to the last one and sticks.

----

I tried to recreate this using simple images created in Photoshop and failed. I tried to create larger simple images using ImageMagick and failed. Finally, I was able to reproduce the problem using 8 images created like this from a bash shell:
d=20171111 # today
$ i=0; for c in navy cyan green yellow red magenta blue black; do convert -size 6720x4480 gradient:$c $d.00$((++i)).png; done
Note that jpg images created the same way did not reproduce the problem.
Note that even this did not always reproduce the problem.
It does reproduce it, however, if I reject and delete the files before the images in the filmstrip are fully rendered.

From what I can tell, the problem seems to be sensitive to the time it takes to render the filmstrip images. I have seen sensitivity on file type, image size, image complexity and fullscreen.

When I reproduce this bug, the picture that I select in the filmstrip is the same one that gets selected in the grid (the second ones) but they both have the wrong image (that of the last). This does not seem to be the same behavior as the original poster of this thread described. I think, perhaps, this is a different issue and should not have been merged with this one.
(Edited)