7
Replies
…have created 1:1 peviews beforehand.
Now when I scroll through them in the develop module, the files open but change appearance after about 4 seconds. They don't do this in library, but only in develop. Very annoying.
By @zobeleye
The modules work differently.
In the Develop module, the priority is maximum image quality so that you can see properly to make the best editing decisions. So in Develop, what you see is a full bit depth wide color gamut render, from the raw data through all applied Develop options. In other words, it is not using anything pre-generated in the preview cache. The Develop module does use a cache, but it’s the full quality Camera Raw cache. This is why you have separate controls in Lightroom Classic for the preview cache and the Camera Raw cache. In Develop, display time is about whether the current state of the image matches what’s in the Camera Raw cache for it, and if it isn’t up to date or isn’t cached, it must be rendered.
If it must be rendered, now the Develop display time depends on the speed of the CPU and GPU, and also…the more edits have been applied (masks, healing spots, removal tool spots…) the longer it will take to render a particular image. Higher pixel dimensions will also slow Develop rendering, such as a raw image from a 50 or 100 megapixel camera. It can also depend on the speed of the volume where the Camera Raw cache is located, but recent Macs have such fast internal storage that if the Camera Raw cache is left at its default location (the internal Mac startup volume), that storage should be some of the fastest available.
That’s the Develop module. Anywhere else, image display time is different because previews are used instead.
In all other modules and views, such as the Library module Loupe and Grid views, or the Book, Web, Print etc. modules, what you see is an 8 bits/channel Adobe RGB JPEG preview of whatever size is needed. If you are looking at the grid, you see previews generated at thumbnail size. If you’re looking in Loupe, it could be a standard, embedded, or 1:1 preview depending on what’s been generated. These should normally display faster than Develop because all they should have to do is pull the JPEG preview out of the preview cache and throw it on the screen. If a preview is not already in the cache for an image, then it has to be rendered, and right now preview rendering depends completely on CPU speed, and (for bulk preview generation) the number of CPU cores. As of Lightroom Classic 14.1.1, the GPU is not involved in preview generation.
Hopefully that explains it: Compared to all the other modules such as Library, which use previews, Develop uses higher image quality specs and different hardware resources for rendering.
Is bulk generation possible in the develop module?
I don't think so.
It is the Library module (not Develop) where an embedded preview made by the camera is first seen, before a LrC-generated preview can be generated. A 1:1 preview may also wait until you first view that particular photo full size within Library.
But you can select a bunch of photos and manage what the Catalog does for their Library previews:
Any changed image gets its Library previews invalidated requiring their re-creation.
All of this works independently of, and I think as a background task in relation to, whatever previewing and dynamic appearance updates happen inside Develop.
Personally, I don't wait for 1:1 Library previews and such, preferring to evaluate image detail and content inside Develop - which is where I would be carrying out actions in relation to that image detail and content.
Only one question i still have now.Is bulk generation possible in the develop module?
By @zobeleye
I don’t think so, or at least not in the same way.
I’m not sure if the following is completely accurate, but my understanding is that when you select an image and switch to the Develop module, in addition to rendering the selected image, it will also start rendering and caching images next to it and nearby. This is to minimize the display time if you decide to go to the previous or next image. I don’t know how far in either direction it will try to pre-render. Of course, how quickly it can get ahead of you depends on how much spare processing power is available.
If you move among non-cached images faster than Develop can pre-render them, then the initial display time could be longer.
I have an M1 Pro MacBook Pro, and most of my images appear in Develop within about 1 second if they have basic edits. But, I have some that can take 4 seconds to display at full resolution, and even a couple that take over a minute; those tend to have a large number of masks. I have a suspicion that dynamically calculated mask features I like to use such as range masks and operations (e.g. Intersect) might delay Develop display even more, but I could be wrong there.
The only thing I can think of to help in Develop is to maybe increase the size of the Camera Raw cache, only because it might increase the chance that an image is already cached. But that won’t help the speed of non-cached images.
How many megapixels are your images, typically? And do the slowest ones tend to use a lot of masks or spot corrections?
AdChoices