P: Slow UI when using Mac and Custom Display Profile

I'm running LRC 10.1.1 on Mac 27 Catalina and it's almost impossible to use sensibly. Adobe, what are you doing to sort out this bug? Rolling back to an earlier version loses hours and hours of edits so is not a realistic proposition. I think I will just have to move to Capture One Pro unless this gets sorted soon.

We have seen a steady degradation in software quality and performance and speed of resolution of issues since they announced the cloud version after many years of steady improvements.  That's a clear indication that resources have been shifted from the desktop product towards the cloud version.  That's fine - it's a business decision.  But Adobe needs to step up and acknowledge it, and set appropriate expectations for future releases and defect resolution timelines.  

Adobe has a mature SDLC, which means that once identified, isolating and identifying what code changes caused the defect (this is an introduced bug after all), is straightforward even if it take some time (but guarantee it didn't take 3 months to find and revert out the change).  Great so far.  They also likely have an automated build process, including creating the installers, so that part isn't an obstacle either.  I'll grant that they don't have a robust automated regression test program, so doing manual QA on it is probably taking time, but that's also predictable.  The point is that with a mature SDLC, they'll have a pretty darn good idea of how long the fix will take.  Maybe not three months ago, but at this point, I'm confident they have a target release date.

We are where we are, and what we need is an ETA - after all, it's their bug that caused this, and if we're going to have to spend our time and money and take risks to work around their bug, we need to know if it's worth it.  If it's 6 months, then it probably is.  If, at this point, it's 6 days, well no, it's probably not.   It'd have been a lot better to have known the ETA two or three months ago, but they still need to share it now.   It's never too late to do the right thing.

Ultimately, we've all been boiled frogs, and we're grousing now because we just realized how hot the water is.

The last update was 37 days ago. 01/12/2021.

The problem is getting fixed, as quickly as can be done without producing other bugs in the process or not fixing it completely. Here is how software is developed (I have a bit of experience doing this in my own company and with Adobe).

Bug is reported. 

Bug has to be verified internally, on multiple kinds of hardware with multiple operating systems. 

But has to be fixed and tested. Internally, externally and to some here on this actual forum! 

Fix has to be documented, new installers have to be built then tested. 

This takes time. Unless you believe, without any data, Adobe is deliberating taking time to delay this because their goal is to upset you personally. 

Now, you're upset. You have every reason to be. Do something constructive about it, a number of options have been provided until the fix arrives. No further posting here from you or I will make this process go any faster. 

And please, put this also into some perspective:

In Texas, 3 million have no electricity, some no water and are freezing. 

The USA is close to half a million dead from Covid-19 and getting my vaccine is not on the horizon. 

Adobe has take 3 months to fix a bug that affects a small subset of the entire user base. 

You still have no idea about customer service.

There is no apology.

Rule No 1 - If it's your fault, always apologise.

The first (and last) 'update' is 4 months old.

Rule No 2 - Communicate in a timely manner.

Rule No 3 - Get the problem fixed fast - no matter what the cost. There is nothing more costly than an unhappy client.

And an estimate is always possible - even if it has to be amended. (Rule No 3 - see Rules No 1 and 2)

That's how a company builds trust and a loyal following - instead of becoming mired in complaints and losing the trust and eventually the subscriptions, of its customer base.

Personal Anecdote:

Once upon a time, I let down a client really badly due to a technical defect which was difficult and costly to track down. Because of the way that problem was handled, that customer not only stuck with us but subsequently became one of our greatest evangelists.

That's what outstanding customer service can do. 

1. Admitted and apologised for the error straight away.

2. Provided those affected with regular status updates and advice on how best to manage.

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-slow-ui-when-using-mac-and-custom-display-profile/5f91bbf7917fbb3a9935742e?page=1

Update 01/12/2021

3. Provided an ETA on a fix.

Not possible. 

"Predictions are hard, especially about the future."- Yogi Berra

Yes, exactly. If Adobe had

1. Admitted and apologised for the error straight away.

2. Provided those affected with regular status updates and advice on how best to manage.

3. Provided an ETA on a fix.

most, if not all, of the frustration and recrimination would never have happened.

There is nothing worse than being disempowered by a faceless corporate entity and being left in the dark with no idea whether or when a solution will be forthcoming.

Good customer relations build good customer relationships. Much is readily forgiven when a problem is honestly declared and progress on a fix regularly provided. And vice versa.

It's such a simple thing, yet so rarely practised.

Yup, just not willing to find out the hard way, and then have to spend time and energy to recover from a corrupt environment.  Can't go back to 9 because of performance problems and also lose the work done since upgrading. Can't effectively use 10 because of the profile issues - and to be clear, 10 even with a standard profile is still having slow performance too: roughly what 9 is, which is noticeably slower than 8 was on an older machine.

And definitely don't have time/energy/money to change entire workflow to use standard profile and then spend more time/energy/money to change back, and hope I don't break the workflow in the meantime.

I've looked into alternatives on and off, but haven't found anything as viable unfortunately (though might go take a look again if this continues). Just have to hope that Adobe will actually release a fix soon.  

@Rikk It would be really helpful to have Adobe share more frequent status updates and an ETA on a fix so we can plan ahead.

"I suspect that there are common components that conflict"

Yes that is the case although I haven't seen a conflict it just that they will share the same things including preferences. Does it have to be that way? NO. It is not that way with PS, IL, ID or others.

There's a reason Adobe doesn't support it, so I suspect that there are common components that conflict, and I'm not going to risk my catalog finding out.

The reason? 

Again, some of us can and are doing this. 

Yes, I agree it's moot in respect to this issue; if you are one of the few Mac users with this bug and if you don't want to use another profile for the display, or calibrate to that and use it, don't use V10 until the fix arrives. 

As I said, the updater only allows one version to be installed at a time.  Hacking around it to force multiple versions isn't supported. There's a reason Adobe doesn't support it, so I suspect that there are common components that conflict, and I'm not going to risk my catalog finding out.

In any case, it's largely a moot point, because 9 has significant performance problems as well on the 16" MBP, so we're stuck until Adobe releases a fix unfortunately.