P: Slow UI when using Mac and Custom Display Profile

Perhaps I read the announcement wrong but I think that Apple stopped supporting Windows in Bootcamp last year. VMWare might be an option. 

If you really want to do your editing on Windows, an alternative and much less expensive solution is a refurbished HP workstation. I paid less than $2,000 for a HP Z440 with 6-core / 12 thread, Xeon 4.0/3.6 GHz and 64GB of ECC RAM, Quadro K1200 4GB video card which runs 4k monitors just fine, 512GB Samsung Pro. Engineering companies tend to replace their systems on a 2-3 year timeline and sell them in bulk to a reseller who perform a minor refurbishment: clean the drive, reinstall the OS and a general dusting and cleaning. For a little more money, you can get them directly from HP. 

*Kevin Lawson  I am also on Big Sur. 10.1.1. My Previews are erratic. Scroll through a grid view and a several of my image previews change before your eyes: they turn desaturated and lack detail. This makes it extremely difficult to match several images when previews don't match.  Adobe needs to fix this problem for professionals on MAC. I and many others were very much hoping it was addressed in the new update.  Switching to 9.4 is not possible with a 10.1 Catalogue. For now, I have to fly blind on matching images in grid view on Big Sur. Running a Windows 10 boot camp +LRc 10.1.1 on a $10k Mac Pro might be the solution for me. As far as I know, PC users are not experiencing this. 

If you externalize all your edits to the XMPs and images then you can create a new V9.4 catalog and import all your images. All of the develop and keyword effects will be imported but you will lose organizations like albums and the individual develop steps. Example: say you adjusted slider-x 5 times, in the left panel, you'll only see the net effect in the right panel and the individual steps will not show in the left panel. 

Just a go-around to get you going again. 

*Kevin Lawson This is not a viable solution to those of us whom have added significantly to their V 10 catalog, which cannot be read by V 9.4.

Again, where does this number come from?

In fact, you do not know.

Me neither.

Less than 1 in a thousand Lightroom users are having these issues. Fairly obvious where the problem lies. 

Thank you for putting the issue in sensible perspective. 

Bill seems to be suffering from chronic cranioproctosis and should not be contradicted as this can exacerbate the condition.

Dear @Gerhard Tittel 

Take some time to read all bill's posts

And try to think about who is insulting who

What is more insulting:

- telling fooleries in every post?
- reacting to fooleries?

I get this issue on:

- Mac Pro 2020 (as other here)

- Imac Pro 2019 (as other here)

And other Macs

But Bill does not stop repeating that you need recent hardware

Bill has several times talked about "first Adobe team" working on new Mac architecture and second team with weak contractors working on current architecture.
Where do these information come from?
If he works at Adobe, then he should be fired for this kind of speech

If he does not work at Adobe, this comes only from his mind, making a disastrous confusion between his thoughts and reality.

About software companies, he repeats that it is standard that they work in  priority for 0.5% new market, neglecting 99.5% of their current market. And this is of course pure invention and BS.

So yes, this place should be relevant to get solutions for a huge bad LR development. When UI freezes, when you are obliged to reboot, then this has nothing to do with image processing. It generally comes from things as memory crushing.

In a serious software development, you are able to track every modification from V to V+1. For debug, you should be able to add modification 1 by 1, monitoring memory and ressources, and check when problems happen.
This is elementary.

Moreover, V10 catalog cannot be read by V9. Major software developments should never be associated at the same time with major irreversible input files modifications.

I may not be an expert in image processing algorithms, but I used to be a software quality assurance auditor (CMM level 5) and I can tell you, without reading any Adobe internal documentation or any source code, that quality insurance at Adobe is near 0.

Best and kind regards
Thierry

Well, when in spite of overwhelming evidence to the contrary, one person sets himself up as the sole arbiter of truth and persists in force feeding his dogma down others' throats, it gets pretty tiresome. 

I thought this forum would be a good place to discuss problems and possible solutions. Most people do, but unfortunately there are some here who post condescending and insulting comments about a post. Too bad