Library module Workflow changes with Previews

[Zenon]

Lightroom Version Number

14.4

Operating System

1. macOS 15 Sequoia

Since the change to the Denoise process that now adds data I'm looking at a possible importing change. I've always imported 1:1 because I never really worried about storage. I still don't. I can always dump previews. I've never really use the Library for viewing as I do a pretty intense pre-cull using Canon's DPP. I realize that the Previews in the Develop module are cached in Adobe Camera Raw 2 folder in the user library.

Everything I have read says the Library and Develop modules use a different set of Previews which makes sense. The answer I can't find is there some hidden connection? If I import using the Minimal Previews will there be a delay when I open a file in the Develop module and zoom to 100%?

Thanks in advance.

 

[Califdan]

Everything I have read says the Library and Develop modules use a different set of Previews which makes sense. The answer I can't find is there some hidden connection? If I import using the Minimal Previews will there be a delay when I open a file in the Develop module and zoom to 100%?

If your catalog is on a reasonably fast drive such as your internal drive or an SSD the extra delay will be trivial IMHO. I only generate Minimal previews on Import and barely notice any delay when taking an image into the Develop Module or zooming into 100%.

 

[clee01l]

If I import using the Minimal Previews will there be a delay when I open a file in the Develop module and zoom to 100%?

I always import using the Minimal Preview option I've never noticed any delay when pulling up a full size image in Develop. I think most people with a Silicon Mac have enough processing power that this would never be an issue. Also I often import using my iPad Pro and the Adobe Cloud. I have not idea what previews are generated if the Adobe Cloud is doing a full size synce to the master catalog. I still never see any delays

 

[Hal P Anderson]

If I import using the Minimal Previews will there be a delay when I open a file in the Develop module and zoom to 100%?

The kind of previews you create on import has absolutely no influence on any delay you see when opening a file in Develop. There is no hidden connection.

 

[Johan Elzenga]

The kind of previews you create on import has absolutely no influence on any delay you see when opening a file in Develop. There is no hidden connection.

Absolutely true. The develop module has its own previews, so what library previews you have when you switch to develop is irrelevant.

 

[Zenon]

Thanks everyone and that was what I thought. I was pretty sure the Library and Develop previews were independent. Sometimes the way things are worded in different articles can through you off. All of them dedicate very little time to the Develop previews. Not much there to discuss anyway. I'll be importing using minimum from now on as well.

 

[BobT]

Thanks everyone and that was what I thought. I was pretty sure the Library and Develop previews were independent. Sometimes the way things are worded in different articles can through you off. All of them dedicate very little time to the Develop previews. Not much there to discuss anyway. I'll be importing using minimum from now on as well.

That makes sense for your situation where you don't cull in Library but elsewhere. However, my first quick-n-dirty cull is in the import dialogue box. The second, more critical cull is in Library. Here I find having 1:1 previews already up, speeds up culling. When working quickly through a large burst, using Compare with minimal previews, the first instance of each new image, is of a low quality, giving the impression it's out of focus and the finger hovers over the Unselect button only to have a sharp 1:1 pop up a fraction of a second later. This is frustrating and means consciously slowing down the cull. With 1:1 previews already in place, the cull can proceed as fast as the eye/brain can manage. For this reason, I prefer to create 1:1 previews on import and do something else while waiting for the longer import to complete.

 

[Gnits]

This is my approach, (ie I cull and do first rating in Library mode)… except… I have my standard size previews set to 2048… as why render 9500 pixels wide (a7RV) when my 4k screen can only display 3840 pixels. As I mostly leave the LrC side panels in place 2048 pixels works for me.

Am I missing something.

 

[Zenon]

That makes sense for your situation where you don't cull in Library but elsewhere. However, my first quick-n-dirty cull is in the import dialogue box. The second, more critical cull is in Library. Here I find having 1:1 previews already up, speeds up culling. When working quickly through a large burst, using Compare with minimal previews, the first instance of each new image, is of a low quality, giving the impression it's out of focus and the finger hovers over the Unselect button only to have a sharp 1:1 pop up a fraction of a second later. This is frustrating and means consciously slowing down the cull. With 1:1 previews already in place, the cull can proceed as fast as the eye/brain can manage. For this reason, I prefer to create 1:1 previews on import and do something else while waiting for the longer import to complete.

Thanks

 

[clee01l]

That makes sense for your situation where you don't cull in Library but elsewhere. However, my first quick-n-dirty cull is in the import dialogue box. The second, more critical cull is in Library. Here I find having 1:1 previews already up, speeds up culling.

How so? I use Minimal Previews on import. I start culling often on a 13" iPad Screen with the image sized to fit. If I need to pixel peep (to check focus perhaps). Zooming 1:1 could not be any faster on the iPad. And it is near instantaneous on my Mac Studio.

I would be interested to see exactly how many 1:1 previews are in my Previews folder

 

[BobT]

This is my approach, (ie I cull and do first rating in Library mode)… except… I have my standard size previews set to 2048… as why render 9500 pixels wide (a7RV) when my 4k screen can only display 3840 pixels. As I mostly leave the LrC side panels in place 2048 pixels works for me.

Am I missing something.

Yeah, I might look into fine tuning it like you. Perhaps I could reduce preview size a bit but certainly minimal is a pain for quick culling, at least on my machine.

 

[Jim Wilde]

Yeah, I might look into fine tuning it like you. Perhaps I could reduce preview size a bit but certainly minimal is a pain for quick culling, at least on my machine.

Have you looked into the "Embedded & Sidecar" preview option when importing? I use it all the time, it gives me a 1:1 preview in Library without having to wait for them to be built. If your camera creates full resolution embedded previews (not all do) it would be worth trying it.