Skip to main content
Participating Frequently
June 30, 2013

P: Navigator preview pane shows wrong photo

  • June 30, 2013
  • 74 replies
  • 1672 views

In Lightroom 5 sometimes the Navigator preview pane display gets stuck on a different photo than what I'm working on in the develop module. I haven't managed to figure out when in happens specifically, but I notice it once every few working sessions.
Thanks, David

74 replies

Known Participant
December 14, 2015
I also have this problem with the latest standalone version of Lightroom 6, 6.3

I think I have noticed this before, but I have really noticed it lately. I upgraded to v6 I think 3+- months ago, but it's just in the past week when I have really noticed it. The only thing I can think of that I've done differently is that just within the past week, I have tried for the first time LR's HDR feature. But, the problem seems to happen on other than just HDR images.

When this happens, which is very often, the incorrect image shows up in the Navigator panel. Further, the file name, above the film-strip, is the name of the file in Navigator, not the one you are working on.

I can move the mouse cursor to the image I'm working on and enlarge it, but that does not fix the problem in the Navigator panel. What usually "fixes" it is if I move the mouse cursor through the film strip again. But, once in awhile, that doesn't even work, and the "fix" is when I click on the correct image in the film strip.

I did just upgrade to 6.3 last night, and the problem still exists.

I have temporarily "fixed" the problem by going into Edit/Preferences and unchecking the box that says "Show Photo in Navigator Upon Mouse-Over."

For me, the worse problem is not seeing the incorrect image in Navigator; it is seeing the incorrect file name above the film-strip.
Participating Frequently
December 14, 2015


BUG REPORT LightRoom :navigator window will display a different photo in the navigator window than the selected photo. This will happen when selecting a graduated ND filter, and erasing parts of it in zoom 1:1 view. the navigator will then show the view from another photo from the series, being the last one the mouse did fly over in the "negative" strip. Moving the "active" window within the navigator is still possible, but the display of the navigator window being wrong, it's kind of weird and difficult to know where you are. Restoring to FIT view does not restore the navigator view. Selecting another negative will refresh the navigator, but the "mouse over" will still trigger the navigator view to refresh to the negative being hovered on, without any mouse click needing to be activated.
Paul
Lightroom version: CC 2015.1.1 [ 1032027 ]
License: Creative Cloud
Operating system: Windows 7 Ultimate Edition
Version: 6.1 [7601]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2,3 GHz
Built-in memory: 24573,5 MB
Real memory available to Lightroom: 24573,5 MB
Real memory used by Lightroom: 1930,7 MB (7,8%)
Virtual memory used by Lightroom: 1902,6 MB
Memory cache size: 0,0 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: No
Displays: 1) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
Quadro 4000/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 353.06
Renderer: Quadro 4000/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler

Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: D:\_Paul\Adobe\Lightroom\Catalog\PPL_2013\PPL_2013-2-2.lrcat
Settings Folder: C:\Users\Paul\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Behance
2) Canon Tether Plugin
3) DxO OpticsPro 10
4) DxO OpticsPro 10 Importer
5) Export to Photomatix Pro
6) Facebook
7) Flickr
😎 HDR Efex Pro 2
9) Leica Tether Plugin
10) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
D
September 13, 2015
Had this issue for quite a while. Glad it is not caused by my setup. Mac Mavericks and LR 5.7. So what is the solution to incompetent corporations? Fire the president? I guess if a hedge fund manager with millions of shares called and demanded a fix that would get their attention.
CresnyAuthor
Participating Frequently
September 3, 2015
Pete,

It certainly can be turned off if you remove the check for that, but that eliminates the mouse-over functionality. It's not consistent, but happens quite frequently, now in LR CC 2015

David
carolek42204412
Participant
September 3, 2015


When using Lightroom CC sometimes my navigator shows the wrong image to the one I am working on! I can still click on the navigator to move around the screen, but I have to click on the wrong image!
Inspiring
August 16, 2015


This is the same bug that had been supposedly fixed in LR4, but still occurs in all 5.x versions that I've tried. And I've tried them all.

Basically, the preview screen of Navigator sometimes shows the image that's not current with the selected one. The only solution so far is to restart the program.

Here's my screenshot of the problem:
Inspiring
July 25, 2015
Works for me on my Win7 cc2015 also, although disturbing that I don't have the problem in LR4 when the same checkbox is checked. Was worried that it was another symptom related to the long standing issues with AMD video card drivers.
Participating Frequently
June 20, 2015
As listed above from the one screen shot and accompanying comments, Adobe *KNOWS* what the issue is. I had a one-on-one video session with one of the production managers at Adobe LAST YEAR, and this has yet to be fixed, even with a major point-0 release.

When you use your mouse to hover over images in the thumb strip, it shows up in the preview pane. When your mouse leaves the thumb strip, it is SUPPOSED to revert to the currently selected image. The problem is that they are not properly tracking "Mouse Out" event (when the mouse cursor leaves a particular area within an application's visual UI)

This should be quite well documented by now. Like I said, I even had a one-on-one session where I showed them exactly this, and explained in quite detail how it happens. I also showed OTHER examples of Lightroom not properly following mouse-out commands (cursor showing up as the wrong icon in various parts of the application)

If this frustrates you too when trying to work, simply run your mouse cursor over the thumb strip again, and then out. Continue to do this until the preview pane goes back to normal.... or... ya'know... Adobe applies a very VERY simple fix.

The actual fix if they decide to implement it: Store the target object under the mouse as a reference in a variable. Upon every mouse-move command received, test the new target against the saved one. If it changes, manually fire an internal mouse-out event. This bug should have been fixed in an afternoon in a single sitting by even a junior dev, it is that freaggin simple.

Really, this just shows how little Adobe cares right now about actual user experience, yet cares more about DRM. Look at the new shiny DRM in Lightroom CC that failed for everyone on day-one of release. How much time, money, energy, and effort did various developers and sys admins put in to making that new DRM, yet no effort so far into fixing this very simple bug? And I bring up the topic of UX because of this: the bug in question is a UX bug. It directly hinders the user experience. And the inclusion of more DRM added to the UX frustrations. We were promised quicker fixes with the CC model, but instead we're just left with bugs that persist for years (I have other documented ones that have lasted this long too)
Inspiring
June 20, 2015
When I clicked on an image in the filmstrip at the bottom of my primary display, it showed up in the navigator. Is that workaround for when the navigator goes off the rails? I shouldn't have to, in my opinion, as clicking on the grid in the secondary display should always update the navigator.
Inspiring
June 19, 2015
It is broken in the latest version of LR and has been annoying me since version 4 at least.