LIGHTROOM: Dual screen enhancement please !

  • 3
  • Idea
  • Updated 6 years ago
  • (Edited)
Running LR in develop module with dual screen is slow and not perfect.

Slow mainly because the first screen is rendered with the high quality redering algo of the develop module and the second screen is rendered with the fast rendering algo of the library. So LR make a similar work twice.

Not perfect because the develop module use, as I know, the ProPhotoRGB icc profile as working color space. The library use the AdobeRGB icc profile for the preview. So it is impossible te have the exactly same image between the screens. And I don't talk about the preview quality set in preferences which could be set to low or medium, a good choice for library view but not for develop view.

I have 2 (or 3) main usage, of the second screen with the develop module :

1: A view with the grid view (second screen) and the image I am working on.
2: A view at 100% and a view where the photo fit in the screen.
3: If I have a rotated screen, I certainly use the second screen in rotated position to have a better view of my portrait photo. But actually I didn't have a such screen.

For case 1, I use my second screen as a filmstrip and the fact that actions applied on selection are just applied on the most selected photo which is just very annoying. So I just can't adjust an exposure of a photo which is a part of a similar set of photos and use the wonderful Ctrl+Alt+Shift+M shortcut to make all the set, selected in grid view, with a good exposure for example.
So please add an option, permit to change this behavior and have a unique harmonized comportment of grid on main screen, grid on second screen and filmstrip.

For case 2 and 3, If little twist of color are not so annoying, however sometimes they are really visible; performance of develop module is just killing me and could just run almost 200% faster if the second screen have a develop mode as grid, loupe, comparaison mode etc... and this develop mode simply reuse the rendered image for the main screen.
So please, and I strongly insist on that, add a option that permit to use a uniquely rendered image in the same color space.

If you have another ideas or comments?
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 3
Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 131 Reply Likes
" performance of develop module is just killing me and could just run almost 200% faster if the second screen have a develop mode as grid, loupe, comparaison mode etc... and this develop mode simply reuse the rendered image for the main screen. "

I don't think that would speed things up at all.

If the image is show in whole in the Develop module, you might be rendering either the 1:2 or 1:4 tree - 1/4 or 1/16th of the total pixels. If you are showing a 1:1 view on the second screen, that would require rendering at 1:1 - 4 or 16 times as many pixels, and thus 4 or 16 times slower.

Try putting Develop (without the second monitor on at all) at 1:1 and using the sliders to see what I mean.
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
Lee, I'm afraid I'm not agree with you, if I well understand what I read (I'm not english), the second monitor never uses the rendered image of the develop module. It use always it's own rendered process. This is why for example, when you left the develop module for library module, seeing at 1:1 an image you have just working on, require a new rendering process. The second sceen is always linked to the library module and never to the develop module.

Whatever I look at 1:1 or 1:2 or 1:4 on main or second screen, I have test almost all of the possible combinaisons and this is always, at least, twice slower with the second monitor than without. Without, the second monitor, LR run fine not so fast and smooth as LR3 can but I can use it without hangs even on my modest config.
I can even tell that the fast rendering process (set to medium quality) in the library is almost as slow than the full rendering process in the develop module.
Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 131 Reply Likes
If you have the Develop module's output on both screens - one at "fit" size and one at "1:1" size, the "fit" size that you are used to using now is going to be 4 to 16 times faster than the 1:1 size. You won't get the 1:1 size for free, as you implied.
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
If I have the Develop module's output on both screens, in my mind, that's a big benefit:

Because since LR is in version 4, develop module always render image to 1:1 to show NR etc... even if we are not at 100% zooming. So display the image in 1:1 or in fit view in develop module don't change nothing.

Am I wrong ?

To be sure, I have make a test, moving tool white balance from 2000 to 10000K. I run 10 test in fit view and 10 test in 1:1 view. I choose WB because this tool is especially super slow to apply with LR and very simple to mesure because of big color twisting. So :

– 10 run at fit view take an average of 23"46 seconds.
– 10 run at 1:1 view take 23"37 seconds.

On an E8400 core 2 duo, win 7 64bit, with 40D cr2 raw file, just 10 Mpx by the way. So little config and little raw file ;).

My conclusion is white balance cursor is super slow (like crop) and another reason to hate LR... and displaying an image in fit view and 1:1 view don't change anything in term of performance.

So using a single rendering process, always at 1:1 view, displayed in both screen should be an enhancement, a big one I think. Even if some interpolation are needed to produce the fit view.

But even if two processes are used, having the same working color profile on the two screen is an enhancement.
The actual state is the worst that can be exist in terms of productivity.