P: Slow UI when using Mac and Custom Display Profile

[adamcrowe]

Hello,

Since upgrading to Lightroom Classic v10.0, all UI-related functionality is painfully slow. All editing functions are working correctly and quickly but scrolling through the catalogue or even scrolling a side panel is taking many long seconds to refresh. Unreasonably long.

Disabling GPU Accellaration has no affect on my Lightroom's performance.

macOS Mojave 10.14.6

Mac Pro (Late 2013)

3 GHz 8-Core Intel Xeon E5

32 GB 1866 MHz DDR3

AMD FirePro D700 6 GB

[FeedbackCommunityMember]

Lightroom truly sucks right now!

Same issue of slow scrolling to freezing the computer when in Develop mode.

Dreadful and should have been fixed by now.

[R-16]

A new (at least to me) wrinkle in this saga—I had the same behavior happen yesterday in ACR. I adjusted a slider and my system froze so that I had to do a hard re-boot. Even a force-quit was not possible. 

This is the same behavior I experienced with Lightroom until I disabled GPU acceleration.

[Chris Kern]

No inside information, but my instinct (as someone with software development experience) suggests this may be a bug that is triggered by some attribute of the MacOS environment—maybe a MacOS (Metal?) link library—which requires Apple's assistance to fix.  If so, I suspect the lack of transparency from Adobe may reflect its contractual obligations to Apple, a notoriously secretive company.  Several posters here and elsewhere who apparently are working with Adobe subject to nondisclosure agreements have indicated that the issue is being seriously addressed.  I don't know any reason to doubt them.  I'm sticking with a Lightroom rev that works fine in my environment (2013 Mac Pro, MacOS 10.15.7, NEC Spectraview monitors) and I really don't feel seriously inconvenienced as I wait for the problem to be resolved.

[COBill]

As others have discovered, a bug in macOS was causing some of these problems. Upgrading to 11.2 has been a boon for some of us. 

[donnafowler81]

yep anything I try and do in the develop Module takes for ages since this upgrade, my work flow is taking substation longer. very frustrating. 

[Lhotka]

@Rikk Count me in here too, but downgrading isn't an option because of the 16" mbp performance problems in the older version (though it would also fix the slideshow bug in the other thread).

Color managed workflow is critical, so I guess we're stuck?  I'm rather surprised that this made it through QA without being caught.

[jlehet]

Lightroom Classic has been intermittently like walking in drying glue since I guess last fall. I'm on a 2019 16" Macbook Pro, 32GB RAM, 2.3GHZ 8 Core i9, AMD Radeon Pro 5500M. Catalina 10.15.7

Sometimes it performs well, but when it slows down everything is slow. Some things are slower than others in those slow Lightroom times, but even working with keywords can try my patience. The switch to the crop tool seems about the slowest. This relatively high end computer is performing worse with Lightroom than my previous 2013 Macbook Pro did with Lightroom Classic in early 2019. In fact I'm pretty sure it's much worse than the first beta of the first Lightroom I used on my ancient G4 or G5 mac tower 13 or 14 years ago or whenever. If I had to wait for every task with several deep breaths before Lightroom responded, I never would have started using it. I've used every version of Lightroom ever released and it's been fantastic until the last months. Of course I have a custom profile for my monitors, and I need that. I can't go back to before V10 because I've done so much work on the catalog. Quitting and restarting Lightroom sometimes helps for a while. I optimize/backup the catalog about every day.

[COBill]

Same machine, my son has none of your problems so my guess is that the custom profile is the difference. He doesn't use one.  

[FeedbackCommunityMember]

So that makes it OK?

[COBill]

Didn't say that. Adobe is working on the custom profile problem but it appears to be complex. As they haven't announced a fix date or for which brand of custom profiles the fix(es) will apply too, in the interim all we can do is either avoid Lightroom V10 or avoid custom profiles. 

[TheDigitalDog]

Who said it was OK? It's a known bug, it's  getting fixed, there's a 'hack' until then as Bill outlined; use sRGB or Adobe RGB (1998) for the display profile. 

[FeedbackCommunityMember]

Ah, so it's no longer our fault for using creaky old hardware? Now, (at last) it's a known bug which is getting fixed. The question is, when? I know we are all being completely unreasonable; after all, it's been a mere 4 months and counting. Oh yes, we can employ a 'hack'. We can accept inaccurate colour for colour critical work. Great advice from a colour management expert. Or according to bill underscore, we can avoid the software we paid for and/or muddle along with crap colour. Brilliant.

[jlehet]

Probably not new info in the general pile-on, but I use two monitors at my desk, or just the laptop screen at other times. I had thought the problem is much worse at my desk, but today I'm just on the laptop screen and it was so awful I had to quit LR. However, after restarting it, it's fine again (still laptop). The calibration device is a Colormunki, and I can't remember if this profile was made with the X Rite software or DisplayCal. Probably about time to do it again.

[TheDigitalDog]

Ah, so it's no longer our fault for using creaky old hardware?

No. 

When, I can't tell you, my NDA doesn't allow it. It IS coming. 

I know we are all being completely unreasonable; after all, it's been a mere 4 months and counting.

Yes, a bit. This was again, a very rare bug that absolutely didn't affect the majority, and in fact, none in pre-release. It's also a bit of a moving target, thanks to Apple, more I can't say. 

You can keep complaining if that makes you feel better. It will not speed up the fix. 

We can accept inaccurate colour for colour critical work

Actually you can. When you calm down and want to know, ask. It's more work but it does work. In the meantime; which is the ONLY choice you have, other than complaining which is rather pointless.

[thierryn48516695]

It IS coming > /dev/null

[TheDigitalDog]

It IS coming > /dev/null

Those that know, can't say specifically. 

Those that don't know make statements seen above. 

[thierryn48516695]

If I remember my english lessons, "IS coming" means something that is currently happening.

If within one week, there is no new debugged version, maybe you will need to apologize and stop posting useless no information post for ever.

If within one week, there is a new debuged version, I will apologize for my geek joke and I will send you a bottle of (french) Champagne.

Deal?

[TheDigitalDog]

If I remember my english lessons, "IS coming" means something that is currently happening.

It is currently happening. Not for you however.

If within one week, there is no new debugged version, maybe you will need to apologize and stop posting useless no information post for ever.

Nope. Doesn't work that way. 

[thierryn48516695]

As English is not my mother language, could you explain, please, why it is not coming for me?

Referring to my English grammar book, IS COMING, means that it is currently happening at the moment it is said or written.

So, one week seems a confortable timing.

[TheDigitalDog]

@photostudiotnk As English is not my mother language, could you explain, please, why it is not coming for me?

That isn't what I wrote.

The fix IS currently happening. Not for you however: not CURRENTLY. Capeesh?

[thierryn48516695]

Verba volant, scripta manent

[Lhotka]

A true color managed workflow in lightroom isn't possible without accurate monitor and printer profiles.  Full Stop.  All it takes is comparing the custom profile to the stock one, and it's completely obvious how far they are off (and my two monitors are off in different ways!).  The only color-managed workaround option is to do all your edits in Photoshop/CR, which kind of defeats the purpose of lightroom.  If I just wanted a DAM tool, I'd have one.

There's been a suspicion that Adobe has shifted most lightroom resources towards the consumer/cloud version of the product and that classic isn't getting much love.  Unresolved performance issues (it's slower than 8 on my 2018 MGP, even with a stock profile), broken slideshow module, delays in camera support, and now this color management all point in that direction.

We should have guessed about the future when it was renamed 'classic' instead of 'desktop'.  Classic implied out of date, legacy, and destined for the scrap heap.  Unfortunately for anyone with a library or images at any scale, cloud simply isn't an option, nor will it be for a long time in the future.  Ubiquitous uncapped fiber to the house (and hotels in remote locations) remains a pipe dream.  

At some point the friction caused by all this will drive me (and a lot of other users) to find an alternative.  Until then, we're stuck.

[TheDigitalDog]

A true color managed workflow in lightroom isn't possible without accurate monitor and printer profiles.  Full Stop.  All it takes is comparing the custom profile to the stock one, and it's completely obvious how far they are off (and my two monitors are off indifferent ways!). 

They don't have to be and one can calibrate the display to sRGB target and use Adobes sRGB profile (or on a wide gamut display, Adobe RGB (1998) )till the bug fix. Result: true color managed workflow. That is one workaround. 

[FeedbackCommunityMember]

You may have a non-disclosure agreement with Adobe but as far as I know, there is no non-disclosure agreement between Adobe and their customers. 

I am perfectly calm by the way (even in the face of passive-aggressive comments) but don't feel I should have to ask a third party for workarounds involving 'more work' to a problem which should never got past the first round of quality control in the first place.

Finally, complaining is not pointless as without it Adobe would not be aware of the extent of the problem let alone be stirred into doing something about it.

[FeedbackCommunityMember]

English is my mother tongue and I can't make neither head nor tail of Rodney's cryptic witticisms either.

And using a term like 'capeesh' to someone who is not a native English speaker is condescending verging on insulting. Good manners cost nothing.