Lightroom: Inconsistencies when using a dual screen configuration

  • 1
  • Problem
  • Updated 6 months ago
  • (Edited)
Hi,

Assuming a dual screen configuration, Loupe view on main display, Grid view on secondary display.

In Library mode:
1. Select several images in the grid on the secondary display.
2. Apply a command like Delete or Ctrl-S to save the images metadata.
3. The command applies only to the "most selected" image

In Develop mode:
...
3. The command applies to all selected images.

This is inconsistent and misleading since the same command can lead to different results. Long lasting problem that has been reported multiple times during the past years. Why a different behavior if the applied command is not related to the selected module (Library or Develop)?

Using LR 2016.6.1 on Windows 10.
Photo of Patrick Philippot

Patrick Philippot

  • 289 Posts
  • 42 Reply Likes
  • frustrated

Posted 2 years ago

  • 1
Photo of David Martin

David Martin

  • 16 Posts
  • 11 Reply Likes
At the risk of sounding glib, this defect, which I too have seen, persists because Adobe Lightroom developers and managers are steering LR towards the iPhone/selfie crowd and don't give a damn about working professionals or advanced amateurs with sophisticated equipment.
Photo of Joel Weisbrod

Joel Weisbrod

  • 164 Posts
  • 93 Reply Likes
Not sure this is a "bug" or "incorrect". I actually like it this way.

When in Library Loupe Mode, changes as you mentioned only apply to the current photo even when multiple photos are selected. In Grid Mode, it works as you would like.

I am using multiple monitors and when in Library mode, I put the main monitor [1] in Grid Mode and the secondary display [2] in Loupe mode. Under this setup, the multiple selection process allows changes to affect multiple photos.

In develop mode, the multiple selection actions only affect a single photo (if done on main monitor in Develop Loupe Mode) but affect all selected photos when the change is made on the grid mode of the secondary display. Again, this is the logical action.

When you are in Library mode with [1] being loupe mode and [2] being grid mode, it performs exactly as I described for develop mode.

I believe this is the desired functionality and was well thought out by the developers. It is a logical and consistent approach that works for me and I guess for many others.

I suggest doing what you want for a multi-image selection on the display that has the grid mode and it will simply work as desired.
Photo of Patrick Philippot

Patrick Philippot

  • 286 Posts
  • 41 Reply Likes
I suggest doing what you want for a multi-image selection on the display that has the grid mode and it will simply work as desired.
I do not agree. This is only true if you are in Grid mode in the main LR window, not in the secondary window. My displays are not identical  and I'm logically using the display that has the best quality and resolution to display my images in Loupe mode while managing or developing. The secondary display is here just to ease management and is therefore almost always used in Grid mode.

I don't see any logic in the current behavior but I admit that some users may like it. This should be configurable. The management of dual display configurations in LR has always been questionable. And I have not seen any progress in that area since years.

Not talking about bugs appeared more recently like the secondary window constantly disappearing and re-appearing (or not) without any obvious reason.
Photo of Joel Weisbrod

Joel Weisbrod

  • 164 Posts
  • 93 Reply Likes
Actually, I just tested this and it does in fact work in the secondary window on my setup. My displays are not the same although similar but I wonder if it is some issue with your graphics card. 
Photo of Patrick Philippot

Patrick Philippot

  • 286 Posts
  • 41 Reply Likes
I wonder if it is some issue with your graphics card
No. I always had this problem with various graphics adapters.

Do you mean that in the Library module, you can have a grid view on the secondary window (display), select say, 3 images images, hit the Delete key and get a message box asking you whether you really want to delete these 3 images instead of asking you whether you want to delete the selected master image (the so called most selected image) ?
Photo of Joel Weisbrod

Joel Weisbrod

  • 164 Posts
  • 93 Reply Likes
Okay, no for the delete key. But attributes, keywords, etc. do work when the grid is on the secondary display. I am not sure why delete doesn't work the same way which I guess is your point.

As a work around, could you simply switch cables on your monitors so the hi-res is [2] and has the loupe mode making [1] available for grid mode?
Photo of Patrick Philippot

Patrick Philippot

  • 286 Posts
  • 41 Reply Likes
Okay, no for the delete key.
Not only the Delete key. Ctrl-S, various inconsistencies with the Stacking commands,... That's the problem : depending on which module you are in, which command you are using, on which window the Grid view is displayed,... the behavior is different. This is not what I call consistency. Users can get used to everything, this doesn't mean that there's nothing to fix. 
Photo of Patrick Philippot

Patrick Philippot

  • 286 Posts
  • 41 Reply Likes
As a work around, could you simply switch cables on your monitors so the hi-res is [2] and has the loupe mode making [1] available for grid mode?
:-) This could only be considered if I didn't use any other image processing software.
Photo of Patrick Philippot

Patrick Philippot

  • 289 Posts
  • 42 Reply Likes
Problem still there in current version.
Photo of JonathanB

JonathanB

  • 12 Posts
  • 4 Reply Likes
You can go to the Metadata menu and select 'Enable Auto Sync' to change this behaviour when using the Filmstrip and/or Secondary monitor in the Library Module. But be careful you understand the implications as sometimes you might have the  filmstrip hidden and not realise you're applying a change to multiple images.