P: Slow UI when using Mac and Custom Display Profile

Pardon me for butting in, but hopefully this is helpful:

You calibrate a monitor when you use its controls to change its output to more closely match your desired target output.

After calibration, you profile a monitor when you use a device to sample that monitor's already-calibrated output and compare it to the expected values.  The profiling software that comes with the device compares the sampled values to the expected values and uses the discrepancies to create a mathematical translation that the system can use to make sure its actually showing the proper colors.

Both steps--calibration & profiling--are required in a properly color-managed workflow.

Now, LR is having performance trouble with some custom-made profiles.  So Andrew and others are recommending that you temporarily use the standard sRGB profile that comes included with your OS instead of a custom-built profile.

But if you're going to use the sRGB profile, you still need to calibrate your monitor to match the conditions in which sRGB is defined that Andrew showed above: Gamma 2.2, white point of D65, and luminance of about 85 cd/m2.  Any other gamma, white point, or luminance will mean the sRGB profile will not work as well with your existing monitor settings.

Not all monitors can be calibrated to this degree.  As far as I know some popular ones like iMac screens will only allow you to change the brightness.  YMMV.  Hope that helped.

@andrew_rodney 

Maybe (I said "maybe") I have understood the meaning of your previous message.

- Calibrate your screen to sRGB

- in LR, for screen proofing, export and printing, use the sRGB profile by Adobe (not the one you have created previously).

If this is right, "for screen proofing, export and printing, use the sRGB profile by Adobe" was missing in your message.

Is there a chance that this procedure solves the UI freezing when in library module?

Regards

Same here and I agree.

No, it is set to write to XMP but I do not always trust that as I had conflicts in the past.  Also, all files imported since will need to be re-imported because they are in the new catalogue but not the old.  They come from various sources.

"reimport / index / keyword / etc" Are you only saving this in the catalog files and not in the DNG or XMP files?

@bill_3305731 

You can export with 16 bits per channel if you use TIFF

I can use 9.4 but I did a lot of work since so downgrading means I lose a lot of work and new images that I will need to reimport / index / keyword / etc.

I will also be getting a MacBook Air M1 in early Jan and will test a clean install of Big Sur + LR10.1.

You are in the same boat as me. I can't use 10 so I am using 9.4. Question do you need to use 10 or is what you need on 9.4?

In about two week I will have MP2019 to test 10 on a clean install. I will install LR10 first and see what happens as I install the rest of the software. I am inclined to think that there is some other conflict somewhere, because I shared my custom profile with someone here. On his machine neither custom profile caused a problem and on my machine both custom profiles caused the problem.

Lightroom Classic runs very slow under specific scenarios on my 16 core Mac Pro 2019, 192GB RAM, 2TB SSD with Radeon Pro Vega II 32GB GPU Card. I have an Eizo CG319X (4K) and NEC PA322UDD (4K) monitor, however LrC is set to only use the Eizo.  Specifically, I noticed two major issues since upgrading to Big Sur and LR10.0 (same issues persist in 10.1):

When in Library module, if I zoom an image to 100%, trying to pan the image is jerky and slow.  Panning the same zoomed image in develop module works smoothly as expected.  PS: Hardware GPU acceleration is set to auto.  Changing to sRGB profile makes no difference.

The second issue I have is that within 5 minutes of viewing photos, adding some adjustments like spot removal, my GPU RAM usage jumps from about 2GB to 32GB, which then causes the Apple WindowServer process to consume large amount of CPU and my whole machine becomes extremely slow and jerky.  Closing Lightroom immediately causes the RAM usage on the GPU card to drop to standard levels (2-4GB) and the performance returns to normal.

In fact, with Lightroom closed right now my GPU RAM usage is 5.7GB.  I launch Lightroom Classic, GPU RAM usage is still 5.7GB.  I open the develop module, it jumps to 9.92GB.  I then take the heal spot edit tool, use 75, 75, 100 brush and click on a photo (Sony A7R4).  GPU RAM usage jumps to 12.48GB.  Add another spot, it jumps to 14.7GB.  Add 17 more spot corrections, and my GPU usage is 100% - all 32 GB of VRAM is used.  WindowServer starts running up to 40 - 80% CPU and everything slows down.

Close Lightroom, GPU RAM usage drops to 1.9GB.

Thanks Andrew. I'll continue benefiting from calibration.