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

[Nikolaus Netzer]

Yes I know that this works but this makes no sense on a 6k XDR display.

[FeedbackCommunityMember]

I am curious as to why no hint of a bug fix being a bit closer, seems to be mentioned by Adobe? Is there a solution on the horizon? Like within the next month? Next week? Maybe even tomorrow? 

[donmonte]

This is frankly ridiculous, I also went back to 9.4 and the speed difference is massive, it’s smooth like butter compared to 10.1

Would be nice if Adobe could enable the new Raw camera update for that version as well so those of us that have the new Nikon Z6ii or Z7ii can use them, instead of having to change the Exif data through a third party program to trick Lightroom into thinking it’s a Z6 or Z7. 
Mac Pro 2013 Mojave 

64GB RAM

D700 GPU 6GB

[Victoria Bampton LR Queen]

*olga_runciman They won't announce that they've fixed it until they've fixed it, and it's clearly proving a tricky one to find and fix. Any kind of timeline they give would just be a wild guess until they've actually found a solution. It is immensely frustrating for all concerned, and rolling back to 9.4 is the best solution right now.

[FloCal]

I totally agree, but after all these months it might be time for Adobe to officially acknowledge the problem and announce that they are working to find a solution instead of sheltering in a near-denial (and offering unsatisfactory fixes). Why is sincerity becoming so rare nowadays?

[FloCal]

You can maybe try to open your Z6ii/Z7ii raw images in Photoshop 22 with the last camera raw plug-in, then convert them in .dng raw files (choosing a the 12.4 camera raw version which is suitable for Lightroom 9.4 in the camera raw compatibility dropdown menu of the conversion window) and finally import them in Lightroom 9.4. This is a bit time consuming but maybe less than changing the Exif…

I tried with Photoshop 21.2 (CR 13.1) and Lightroom 9.4 (CR 12.4) and it worked. Should work as well with Photoshop 22.

[donmonte]

Thanks for the response, but I actually change the Exif data in batch so it doesn’t take that much time, but it still is an unnecessary step. Hopefully they fix Lightroom in 10.2 otherwise it would seriously be time to look at alternatives even though 9.4 works like a dream. 

[FloCal]

Ok, if you take it for granted that the Z6ii/7ii raw images will be processed correctly with the previous version of camera raw (which is not supposed to be suitable to them).

The advantage of using the right plugin and the intermediate dmg is that it is not a concern anymore. Anyway, please keep us posted about it.

[donmonte]

Lightroom 10.1.1 is here, did anyone try it ?

[FeedbackCommunityMember]

Yes, I just did - no change. What gives, Adobe?

[FeedbackCommunityMember]

Really? Unbelievable.

[FloCal]

According to Victoria Bampton (the Lightroom Queen), the only change in this release is a fix for "an issue for specific files missing Lens Metadata […] causing the sync to Adobe cloud to stall".

Unfortunately, I'm afraid it will take much longer for our big problem to be solved…

[FeedbackCommunityMember]

I just saw the update and am updating now. I was so excited... How disappointing. 

Could we just get a confirmation that Adobe is working on this huge bug? Or are we in reality too few that they can't be bothered?

Again how disappointing I thought here was the fix...

[FeedbackCommunityMember]

@Victoria_Bampton_Lightroom_Queen I just saw you answered my above question further up the thread. Thanks for that and sorry for repeating myself!

[FloCal]

Adobe's silence is disturbing. It may mean that they are assessing the need to work on this issue based on the impact it has on customers combined with the work it takes to fix it (its cost effectiveness, if you have to call it by name). And if it turns out that it is limited to a few users (which would surprise me, however), the risk is that it will not be taken into account, betting on its disappearance over time as the material and the users' work context evolve. Let's hope that many of us will complain and consider changing software even if it's unpleasant (for me, it would be, but I have to keep working with updated tools).

So, Adobe, please do something for Lightroom lovers!

[FeedbackCommunityMember]

I am using an EIZO CS2370 display, a custom color profile and macOS 10.14.6. Lightroom 10.1 makes macOS completely unresponsive as soon as I enter the development module. I cannot even shut the system down other than pressing the power button. Lightroom 10.0 works fine, though.

[FeedbackCommunityMember]

This is just a hunch, but I believe there are two different issues at play here:

- Slow-downs of the LrC UI caused by the use of custom ICC profiles that are present independent of GPU-acceleration settings and which don't affect the stability of the host system. That's what I'm experiencing all the time since I've upgraded to v.10 and when using any other profile than sRGB.

- GPU-related artefacts, instability and lock-ups caused by LrC that affect the entire host system. I've had a couple of such lock-ups early on while running v.10.0 on Mojave, but they've since then disappeared completely for me (I'm not entirely certain whether the upgrade to Catalina or v.10.1 were responsible, but I believe it was the latter).

@redreini_weather: if you still have 10.1 installed, are the issues you describe still present when disabling GPU-acceleration?

[ketzaldev]

Hey, I'd like to know if it's possible to have LR CC 9.4 and LR CC 10.0 installed to the same computer, side by side ?
Thanks

[kurt765]

10.1.1 is out with no mention of this problem being addressed.

https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html

January 2021 release (version 10.1.1)

    Specific files missing Lens Metadata do not sync and cause sync to stop completely.

[FloCal]

Unfortunately, no. Whereas it is possible with many other Adobe applications, like Photoshop, Illustrator, InDesign… I don't know why.

See : https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-allow-multiple-versions-to-...

[Was DYP]

@louis_brunet Yes it is, but of course you can't use the same library files. And, you can have both open at the same time. One thing to be aware of is that they will share the same preferences, which I have not found to be a problem. Things like the GPU setting will be the same for each.

Before install 10.0 make sure you have two copies of the 9.4 folder. Of if 10.0 back to 9.4 make sure you have two copies of the 10.0. You can copy them some where else and the copy them back to the Application folder. Just rename the folder Adobe Lightroom Classic by adding 94 to the end of it and 10 to the 10.x folder.

[ketzaldev]

OK, thanks @DYP.
My issue is that I figured out too late about the issue we all have, and I'm working with 10.0.0 since 3 months. Now, this problem pisses me off too much, and I just want to have a 9.4 installed on the same system, to manipulated ongoing images, and then load them to my big 10.0.0 lib.
As a workaround, it should work

[Was DYP]

Yes that should work as long as the edits/manipulations are not saved in the 9.4 library. 

[FeedbackCommunityMember]

Hi,

thanks a lot for your reply. I donot have 10.1 installed anymore but will give your suggestion a try, soon. I never had a single problem with any version of LR before 10.1 and always had GPU-acceleration enabled.

I will report back here.

Edit: Just had a look at your website, I really like your work.

[David Mantripp]

Of course the other reason might be that they've optimised revenue by reducing costs, i.e. fired all the (expensive) competent programmers and replaced them with offshore bodyshops. 

And nobody has the first clue how to fix it.