Skip to main content
Known Participant
August 6, 2024
Answered

30 Seconds to move between images in Develop

  • August 6, 2024
  • 5 replies
  • 3319 views

I have a problem with LRc on my Macbook Pro M1 (32 GB RAM/ 2 TB SSD): everything is running extremely slow. Changing from one photo to another takes e.g. about 30' in the "Development" module. The slowness applies to almost everything. It was not there from the beginning, but gradually increased within the last few months...

 

The Adobe support is underground: first one has to talk to a robot until the robot decides to give over to a human. The humans are little better, as they give general place paste/copy suggestions and refer to websides that are acessible anyhow, but all these suggestions do not help. Needless to say they fade away shortkly afterwards... . No advertisement for the expensive subscription 😞

 

I read here in the forum that the slowing down of LRc seems to be a common problem with Mac OS, but could not find a real solution. I wonder whether someone has found the problem and how to fix it. Below the system info...

 

Wolfgang

Lightroom Classic version: 13.4 [ 202406181129-60d181b7 ]
License: Creative Cloud
Language setting: en-AT
Operating system: Mac OS 14
Version: 14.5.0 [23F79]
Application architecture: arm64
Logical processor count: 10
Processor speed: NA
SqLite Version: 3.36.0
Power Source: Plugged In, 100%
Built-in memory: 32.768,0 MB
Dedicated GPU memory used by Lightroom: 7.724,0MB / 21.845,3MB (35%)
Real memory available to Lightroom: 32.768,0 MB
Real memory used by Lightroom: 4.274,7 MB (13,0%)
Virtual memory used by Lightroom: 417.249,2 MB
Memory cache size: 165,8MB
Internal Camera Raw version: 16.4 [ 1897 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 1385MB / 16383MB (8%)
Camera Raw real memory: 1432MB / 32768MB (4%)

Cache1:
Final1- RAM:963,0MB, VRAM:5.702,0MB, DSC05714.ARW
Final2- RAM:469,0MB, VRAM:0,0MB, DSC05715.ARW
NT- RAM:1.432,0MB, VRAM:5.702,0MB, Combined:7.134,0MB

Cache2:
m:165,8MB, n:1.159,1MB

U-main: 83,0MB

Standard Preview Size: 2048 pixels
Displays: 1) 3024x1964, 2) 3840x2160

Graphics Processor Info:
Metal: Apple M1 Pro
Init State: GPU for Export supported by default
User Preference: Auto

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/ws/Pictures/Lightroom/Lightroom Catalog-v13-3.lrcat
Settings Folder: /Users/ws/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Flickr
4) Loupedeck2
5) Nikon Tether Plugin

Config.lua flags:

 

 

 

This topic has been closed for replies.
Correct answer Conrad_C

This is interesting: I came to 1920x1080 as this is listed as "default" in the system settings. Therefore I have set it to this value. Now I have set it to 2560x1440. I will work for a while and in case this was the problem, I will report it...


quote

This is interesting: I came to 1920x1080 as this is listed as "default" in the system settings. Therefore I have set it to this value. Now I have set it to 2560x1440. I will work for a while and in case this was the problem, I will report it...

By @WS007

 

If you set it to 2560 x 1440, then you now have it set up exactly the same way I do for my 14" MacBook Pro and 2560 x 1440 display, so that should (?) rule out your display setup as a cause for long slowdowns because I run it the same way and it’s fast. So, something else is probably the cause…

5 replies

Inspiring
August 16, 2024

Can you try updating to 13.5 ?

I had the exact same problem, and 13.5 is at least significantly better, it not completely solved.

MacBook Pro 16’’ M1 Pro 16GB on OSX Ventura 13.1
GoldingD
Legend
August 6, 2024

 

 

everything is running extremely slow. Changing from one photo to another takes e.g. about 30' in the "Development" module. 

 

 

Ok, first a few common inquiries

 

  • Is this performance degradation seen in both the Develop Module and the Library Module, or just the Develop Module?
  • How much free space in percent (yes %) on that MAC Hard drive? Looking for at least 20%, some say 25%
  • In LrC /Preferences/Performance/ what is your Camera RAW CACHE Settings amount? Hopefully not the Adobe default of 5 GB
  • Your Loupedeck 2 Plug-in, what version number?
  • Your Loupedeck application, what version number?

 

Conrad_C
Community Expert
Community Expert
August 6, 2024

That is definitely not expected; I use a similarly configured M1 Pro and don’t see anything close to that kind of delay moving between images in Develop. I get less than one second from image to image, maybe slightly longer if not already cached.

 

If it’s taking 30 seconds per image, open Activity Monitor and see if, during that 30 seconds, any process is using an unusually high percentage of CPU or GPU. If there is, it will either be Lightroom Classic (which would indicate a problem there), or it will be another process that is taking CPU away from Lightroom Classic (such as anti-malware software, accessory driver software, or another background process that might not be working properly).

 

Also, how much free space is on the Mac’s internal SSD? For any images that have been viewed recently in Develop, those should be cached for fast display in the Camera Raw cache, so another possible cause is something wrong along the path to the Camera Raw cache folder, such as a problem with folder permissions or corruption. The current location of and size limit for the Camera Raw cache is in Lightroom Classic > Preferences, Performance tab.

 

You have two 4K displays connected and there’s nothing wrong with that, but if the Secondary Display window is open, see if it’s any faster with the Secondary Display closed because that feature is said to be a factor in some slowdowns. I leave Secondary Display open all the time, but maybe I don’t notice a problem because it’s on a smaller display.

 

Another thing to try, if you haven’t done this lately, is to choose File > Optimize Catalog.

WS007Author
Known Participant
August 7, 2024

Hi Conrad,

Thank you for th eextensive reply with a lot of suggestions that I will follow...

 

Just one thing: you say I have two 4k displays open? Not that I know: I have the retina display of the Macbook (1512x982) and one secondary monitor (BenQ SW270C with 1920x1080)...

 

Could this be the problem and how can I turn these two 4k monitors OFF (I cannot see them in systems settings)?

Legend
August 15, 2024
quote

Apple supports up to 4096 x 2560 on my internal display. Everything is tiny and unusable but it works. Notive is 3072 x 1920. I have no idea how this works but it does.

 


By @Lumigraphics

 

I don't think it really does, because you can't display a higher resolution than the native resolution. If you could do that, then two screen pixels would somehow have to display three distinct image pixels, which is simply impossible.

 

What I think happens is that apps can send 4096x2560 pixels to the screen (and so a screenshot will also be that size), but this gets downsampled to the native resolution of 3072x1920 pixels when it is displayed. That's the same as the 5120x2880 pixels that are sent to a 4K screen when you set the screen to 2560 pixels. 

 

Here's a screenshot of what SwitchResX can do with my 4K screen. Do note that not every setting is HiDPI, so not every setting uses the downsampling trick. The difference is clear to see. If I set the screen to non-HiDPI 2560x1440 pixels, then the image is quite soft, because now the 2560 pixels are upsampled to 3840 pixels and you can clearly see that.

 


Nope, its showing me actual pixels. The panel must be above native resolution and scaled for default.

Legend
August 6, 2024

Where are your photos located? Internal, external, network?

WS007Author
Known Participant
August 7, 2024

Hi Lumigraphics,

My photos are located on the SSD drive of the Macbook Pro...

dj_paige
Legend
August 6, 2024

Try temporarily turning off your anti-virus.

JohanElzenga
Community Expert
Community Expert
August 6, 2024

Another thing to look at is Loupedeck. I believe there are some issues that have not been resolved yet.

 

-- Johan W. Elzenga