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

[David Mantripp]

Bill, whoever you are, I have LrC on 3 Macs of different generations and configurations, from quite old to very new, quite modest to powerful.  All run 9.4 (and Capture One 21) quite happily.

If I install LrC 10.x, then toggling between my custom profiles and sRGB toggles this bug like turning a light on and off.  Rikk has clearly admitted to this issue in his last update.

Was your son using custom profiles? If not, (a), I guess he's not that bothered about colour fidelity and (b) just shut up and go and spread disinformation on some other thread, rather than trolling people here who are already frustrated by this 3 month old showstopper they're paying for very month.

[David Mantripp]

*celinezug il y'a deux solutions: ou bien retourner au version 9.4, ou bien utiliser le profile standard sRGB.  

Ou bien attendre....

[David Mantripp]

yes, but what colour profile are you now using? If that was reset to default, well.......

[FeedbackCommunityMember]

I also have this problem ! I'll now use the Adobe RGB profile as substitute and this helps. 

iMac (Retina 5K, 27-inch, Late 2015)

3,2 GHz Quad-Core Intel Core i5

AMD Radeon R9 M380 2 GB

[FeedbackCommunityMember]

mixed experience here:

MacPro6,1 macOS 10.14.6:

LR9 just fine

LR10 lags badly unless main display set to sRGB in System Preferences, no matter what LR hardware acceleration and preview settings

MacBookPro11,5 macOS 10.14.6:

LR9 and LR 10 just fine

[FeedbackCommunityMember]

@Rikk  Exactly my issue - 28"Samsung 4k monitor calibrated by i1 Profiler. Painfully slow - 2-3 sec to render each photo using custom profile, move Lightroom over to 2nd 1080p monitor and photos render immediately - even though it also has a custom calibration profile. Switching the 4k to sRGB speeds things up greatly, but not as fast as the 1080p - expected. Opening LR in low-res mode also helps even with custom profile.

OSX 10.14.6 with i7-3770, 16GB RAM, AMD RX580 8GB, photo library on external SSD through USB3. Internal drive also SSD on SATA6 bus.

[MayerD]

I have the same problem.....

Mac Pro mid 2013 

RAM 64GB

Double AMD Radeon D300 3GB

The problem star when I use Texture......in LR Classic

I Must disable GPU Accel.

[COBill]

Your GPU lacks sufficient RAM for Lightroom V10 if your monitor is higher resolution than FHD. Only one of the cards is used by Lightroom BTW. 

[MayerD]

No lacks...

I’ve monitored GPU RAM and GPU:

GPU RAM: 35% used only

GPU:  5-10%

I downgrade to LR 10.0 And Now work again smoothly. 
The Upgrade is the problem. 

[FeedbackCommunityMember]

This problem is still going on with no end in sight. Is there anybody from Adobe that can at least assure us that they are trying to work on this problem?

As many others I have discovered that using SRGB profile is the only thing that lets lightroom work normally which of course means color calibration it’s not possible

I have discovered a semi work around in that after trying many profiles I have discovered that the Wacom Cintique pro RGB profile works with few delays and this closer to my own monitor calibration profiles but not perfect

However it is clear that it is a software problem so if you are listening Adobe please let us know that you were working on it or if not then we can move on.  

[patriceb40935673]

I experience the same problem with LR10 (MacPro 5.1, 64 Go RAM, Radeon RX 580 8Go).

Moreover, some colleagues of mine have the issue with Adobe Premiere Elements 2021 on new iMacs 27 using Mac OS Big Sur. The only solution is to set to sRGB in System Preferences with both softwares...

Really problematic.

[FeedbackCommunityMember]

*olga_runciman

Adobe are deaf.

Adobe don't care.

Adobe don't do customer service.

You're supposed to wait in line with your mouth shut and suck it up until they get around to it.

......Don't hold your breath.

[FeedbackCommunityMember]

The anger of some Adobe users is deep, but knowledge of human nature tells me they don't want to lose their homes if Adobe went under (so they do care). And some just care because they like people and want to be helpful.

[TheDigitalDog]

*user  On that Macbook Pro, try Adobe RGB (1998) instead, any better? At the very least, the color should be better as this is a wide gamut display. 

[FeedbackCommunityMember]

Yes they care  in much the same way as banks, utility companies and other giant corporations care.

[Was DYP]

You mean care about the stockholders first.

[TheDigitalDog]

You mean care about the stockholders first.

The stockholders are super happy because Adobe is making a big pile of money with some many customers. Seems they are doing something right here, even if a small group admittedly deserve bug fixes of which they will get.   

[thierryn48516695]

Do you have an evaluation of what you mean by "small"?

If you have, please provide it here and provide your reliable source of information.

[TheDigitalDog]

Do you have an evaluation of what you mean by "small"?

A  small fraction of the installed user based which (from my conversations with Adobe under NDA of which I can't specifically share) is in the millions. More than a million that I can say, specifically how many more I cannot. 

If you assume even tens of thousands of users have suffered this bug, maybe you can explain why so few of that group has posted about this issue here and on many other such sites. Please attempt to gather say 100 unique customers of such reports if you can. 

[TheDigitalDog]

*olga_runciman so if you are listening Adobe please let us know that you were working on it or if not then we can move on.  

They know, they are listening and, a fix is coming. I could tell you a date too, but Adobe's lawyers would have to kill me, then you <g>. 

Look Adobe didn't go out of its way to introduce this. Its really rare and nasty bug and it was difficult to pin down then fix. But again, a fix will come. There are workarounds in the meantime and posting here about it will not make the fix come any faster (kind of the opposite actually). 

[FeedbackCommunityMember]

Andrew, while it’s nice to hear from you that a fix is coming, this is information that should really come from Adobe. They need to own up to this - we are paying subscribers to a currently dysfunctional product.

Naturally they didn’t introduce this bug on purpose - but that doesn’t change the fact that they did introduce it. From reading the reports here, the bug seems easy to reproduce - it certainly was in my case, starting with a clean OS installation. So they should know by now how this bug is caused...

And even if it is a bug that arises due to underlying issues in macOS, the very least Adobe could do is to create a version of LrC that works around the issue and that is compatible with v.10 catalogues, contact users who have reported here on this forum to be affected by this issue, and provide them with an installer. That’s certainly possible, since v.9.4 was not affected. That would give them all the time they need to work on a real fix while keeping their customers happy. And I think most if not all of us affected by this bug would be happy to work with the v.9.4 feature set if we could preserve the edits we’ve done since upgrading to v.10. Now that would be customer service!

I’ve experienced exactly this kind of attitude with software vendors far, far smaller than Adobe. If they can afford to do that, Adobe certainly can!!

It‘s been over three months without a real fix - that‘s simply unacceptable in my book!

[FeedbackCommunityMember]

andrew@acerte.co.uk Rodney  When I was in business, no customer was 'too small'. It's called customer care.

So yes, the shareholders may be happy (for now) but it demonstrates a rotten attitude which in the long run tends to bite back.

[nitin.chandra]

*Ron_Pfister I had made this suggestion a while back. Pull out 9.4 branch, plug in the new camera profiles, perhaps update the catalog format, change the filename of the preferences file to reflect the current version which would allow people to run 2 versions of LR w/o any major issues. Also, export picks/stacks/albums/virtual copies to the xmp so anyone can export those and rebuild a new catalog with any version of LR w/o losing data.

[TheDigitalDog]

From reading the reports here, the bug seems easy to reproduce...

Yup, very easy. IF THE BUG affects you. How many minute's did it take folks affected by the bug to see they were affected by the bug? 

ONE person in pre-release was affected among many more than that number of testers who were not. It's a rare bug, full stop. Rare in terms of the installed based of users and previously within internal and external testing groups. The fix is coming. 

You can roll back to the last version, that's why Adobe provided a catalog backup. Oh, folks updated and didn't keep their legacy catalog or kept working on the new one instead of stopping and considering going back.

You can decide not to update immediately to see if such bugs affect more users after release if you do production work, you're a real pro who can't afford not to have everything working. 

I had made this suggestion a while back. Pull out 9.4 branch, plug in the new camera profiles, perhaps update the catalog format, change the filename of the preferences file to reflect the current version which would allow people to run 2 versions of LR w/o any major issues.

“There seems to be some perverse human characteristic that likes to make easy things difficult.” -Warren Buffett

First, your suggestion is based on what knowledge of the Adobe code base? You make it sound like a very simple fix, you sure?

If Adobe detects the bug issues to branch as you suggest, why not just fix it? 

How many software packages has your company produced? 

Next, take the teams limited resources to do this IF EVEN POSSIBLE? 

This is pointless but if venting makes you feel better, you'll still be waiting just as long for a bug fix! 

[TheDigitalDog]

Andrew, while it’s nice to hear from you that a fix is coming, this is information that should really come from Adobe.

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-slow-ui-when-using-...