I have a relatively new iMac with 32gb memory and Lightroom is optimised according to every bit of advice available on this forum and elsewhere. Despite this, on my system, the Adjustment Brush is effectively unusable.
I'm attaching a couple of screen recordings to illustrate the issues.
Video 1 Adjustment Brush Not Responding: The adjustments start at 0:12 and complete at 1:24 (1:12 seconds to complete). The Activity Monitor show Lightroom Not Responding at 1:03. That's over a minute to update one simple adjustment.
Video 2 Adjustment Brush Not Responding: The adjustments start at 0:08 and on average each takes around 30 seconds to update
Video 5 Adjustment Brush Slow Unresponsive: Mask adjustments are slow to update on the screen making the process of painting adjustments unusable. The actual adjustments lag behind up to 30 seconds. It takes almost 10 seconds just to hide the Mask Overlay (1:42 selected - off at 1:51).
Does anyone have any answers on how to improve my system or make this aspect of Lightroom functional?
Yes, turning off the GPU is a big improvement. That's confounding because that option has provided very little improvement in the past. However, now I'm noticing slower page scrolling and spot removal processing and other various actions seem to be a little more sluggish in Develop. For example; the "visualisation" option (spot removal tool) can take 20-30 seconds to restore when switched off (that's improved over the previous state where it was taking up to a minute). I am also finding that screen updates during scrolling (with the hand tool zoomed 1:1) lags and can take upwards of 20 seconds to update when doing fine masking.
So, the issue has improved overall and I can work but it's far from satisfactory.
I really love Lightroom and I'm early adopter having come across in the first days from the original rawshooter software. I'm frustrated, having just purchased a new iMac Retina with 32mb of memory and large SSD in the expectation that the investment would greatly improve my workflow and enjoyment of Lightroom.
But despite the hardware upgrade, over the past 18 months, the feature set has improved but the performance and hence the usability has dropped off massively.
The fact is that the program has been unusable at times for simple editing and I wouldn't even consider doing some of the detailed editing that I routinely now do in Luminar and ON1.
I already go to great lengths to squeeze the maximum performance from Lightroom; I restart my iMac often, I close every background process, make small catalogs; I pay strict attention to workflow order (which means I don't crop or do lens corrections until I finish editing, which is a really compromised process IMO). If I'm accumulating a large history I often clear it all and start again to reduce the system load (that's really time-consuming) and many other little things like turning off my virus software.
What can I do to get a better result with this program? Frankly I'm getting ready to change despite how much I will lose in the transition to a new platform.
Thanks for your help, regards,
It really depresses me to see all these You Tubes of Lightroom users doing these quick and amazing edits that simply can't be replicated on my system. So I guess my simple desire is to just use the program to express my art without all this complexity and compromise. It just constantly stresses me out, totally interferes with my workflow and creativity and provokes my interest in alternatives.
Slightly better off and hopeful, but still frustrated.
Is there an issue with display resolution?
I've done some further testing with the adjustment brush which shows it to be very unresponsive with the GPU on and off. The show/hide selected mask option can take up to 1:20 to change it's state and brushing with low flow/density is just not a useable function. I've attached a video link to demonstrate.
We're really sorry for all the trouble caused you. We have identified this issue as a bug and our engineering team investigating a fix. Please add your vote to the below feedback link.
For now, rolling back Lightroom to 7.2 version is the only workaround available.
It seems like I get significantly better performance If I avoid auto-masking and the paint adjustment tool in favour of radial filters. But that's not a solution, it's a poor workaround.
Sometimes it runs OK (but still not fast or snappy) but othertimes is just like Harvey.
Toggling Hardware Acceleration is a mixed bag too - sometimes on is better, sometimes off is better. I've been unable to find a consistent experience or set of circumstances where it goes good or bad.
Even flicking from Develop to Library takes seconds.
I know the retina screens have so many more pixels to paint and display, but the performance is simply lacking, especially given the power of the hardware itself. It is almost like no testing is being performed on screens such as this (or the issues are being ignored).
I've continued troubleshooting these problems without any progress so I've now taken the same images into OnOne and Affinity and been able to process them far more intensely and without the slightest issue.
Since my last post, I have also discovered that file size appears to be a big part of the issue. LR 7.x copes reasonably well with files from my Fuji XE-2 and older files from my Canon 7D. Downsizing my D810 panos and other images to smaller .jpegs has enabled me to edit them with only very minor issues.
Lightroom is still my editor of choice but it needs to be functional and it's not at this point. Still waiting...
How large are these panos before you downsampled? Size in MB? Size in Pixels? At what size did you find they starter performing 'with only minor issues?
The large .dng pano is 203.5mb. All the other large images are raw files from the D810 which are around 40mb. I'm not able to reliably edit any of these files on any LR Classic 7.x version.
The downsized jpeg pano is 19.4mb. I've done some more testing since my last post and I'm not having any problems editing this file in Develop so far - I'm hesitant to be 100% because the issues have been erratic and inconsistent, but it's all looking good. The Fuji and Canon 7D files are also about the same size and also seem to be OK.
I've done more troubleshooting since my last post. I removed all of my plugins and deleted the preferences (again), deleted the program and re-installed LR Classic 7.2 (again) and created a brand new catalog and imported a few images to work with. Processing on the large .dng pano was still slow(ish) when I first started editing started - but similar to my earlier experiences ground to a halt when I started brushing adjustments. I gave up when I watched the spinning ball for over two minutes.
My activity monitor showed CPU 84.11 % Idle and "Lightroom (Not Responding)" during the entire time the ball was spinning and Lightroom was frozen. What's that all about?
Editing all of the other (smaller) files is very quick and I am not seeing any lag or spinning balls even when I added extensive brush and gradient adjustments in a "torture test".
So I guess the learning here is that Lightroom Classic 7.x on the iMac has issues dealing with D810 (and bigger) files.
I'm going to update LR to the latest version later this morning (my time) and check out the performance on these files again. I'll keep you posted.
Just so I am clear. You have many screenshots of history posted here. This is the continuous history of one file's adjustments - not multiple copies of the same screenshot?
I would like to schedule a remote session with you to watch you work an image if you are willing. Is the email address with which you've registered at this forum the correct address to contact you?
I have one comment and one question — after working in the Develop module for quite a while on an image at high magnification, brushing and panning around, sharpening , etc., when I then switch to the Library module, I have gotten on occasion 90 second beach balls, almost to the point where I was about to force quit. In contrast if I’m just arrowing around in Library and just switch back and forth to Develop, switching is very fast. Is it advisable to open a new issue about this, or should I add to existing module-switching threads?
Second, up-thread I mentioned that I had created a set of Smart Previews in addition to 1:1 Previews — is this considered “best practice” to maximize Develop module performance (even when the source files continue to be available) as well as Library performance, respectively?