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

[thierryn48516695]

Or maybe you are not able to admit having made an error or a typo.

[TheDigitalDog]

@photostudiotnk Ok for first point, my error,

Not the first error. 

Or maybe you are not able to admit having made an error or a typo.

There's another error. 

Adiós 

[thierryn48516695]

https://www.amazon.fr/Etiquette-Dummies-Sue-Fox/dp/0470106727

[Was DYP]

Give it up.

A calibration of the display is not the same as a profile. It is no different than printing where calibrating a printer is not the same as a paper profile. 

A profile is built on top of that calibration, which should be a what software uses. The question in using sRGB will be how close it is to a monitor set to sRGB and calibrated. Obvoiusly not the same as profiling (custom profile) the sRGB calibrated monitor but is it close enough.

Probably most of use would prefer a wider gamut for photo editing and probably most of our monitors are wider than sRGB. 

[COBill]

Question 

As Lightroom exports at 8-bits per color channel, does it matter whether Lightroom is set to sRGB or RGB? Perhaps I'm not even wording the question correctly?

For several years, my monitors have been 10 bit, always calibrated and with about 75% RGB / 99% sRGB and when a bit flush, 99% RGB. While the differences were subtle, images on the 99% RGB monitors were usually superior when compared side by side with the lesser monitor.

I always assumed it was due to the monitors and that Lightroom didn't "know" the difference. 

Have I got this right or am I missing something (or even missing a lot)? 

[TheDigitalDog]

@bill_3305731 As Lightroom exports at 8-bits per color channel, does it matter whether Lightroom is set to sRGB or RGB?

RGB what? 

sRGB is a well defined color space. RGB is a color model. 

I always assumed it was due to the monitors and that Lightroom didn't "know" the difference. 

All ICC aware applications are aware of a display profile that defines a behavior (a calibration if you will). The profile does as the name implies; profiles device behavior. 

[COBill]

Thanks Andrew. I'll continue benefiting from calibration. 

[wnell]

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.

[Was DYP]

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.

[wnell]

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.

[Bob Somrak]

@bill_3305731 

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

[Was DYP]

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

[wnell]

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.

[Was DYP]

Same here and I agree.

[thierryn48516695]

@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

[kimballisms]

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.

[TheDigitalDog]

I'll continue benefiting from calibration. 

You will. But it's important to know that a profile that reflects that calibration has to be used with all ICC aware applications for producing a preview. It's calibration (or a state of behavior) and a profile used to describe that behavior to ICC aware applications to produce a color managed preview. 

If you were to calibrate a display to sRGB specifications, any sRGB profile that also defines that behavior could be used as suggested. 

[Was DYP]

"Now, LR is having performance trouble with some custom-made profiles."

But there is something else that triggers this. The same custom-made profiles do not make LR10 behave the same on different systems.

[David Mantripp]

I see exactly the same thing on my MacPro 2013.  Add a few local adjustments, and the whole system freezes. Only recourse is power cycle.  This is a new bug in 10.1, it isn't there in 10.0.  GPU Acceleration off seems to fix it, but I'm done taking risks.  Seriously thinking about being done throwing money at Adobe too.  This is getting beyond a joke.

Note, I'm running many other applications, including several Lr rivals, and other GPU accelerated apps, and seeing no issue whatsoever.  It's only Adobe. Well, actually, it's only LrC.

[David Mantripp]

@Victoria_Bampton_Lightroom_Queen

...10.1 may well fix "other issues".  But it INTRODUCED this one - it isn't there in 10.0.

[kimballisms]

I have no opinion on the deep-rooted cause of the performance problem as I do not experience it myself.  Just trying to help folks understand the temporary workaround recommended above.

[FeedbackCommunityMember]

@bill_3305731 I think you may be missing quite a lot - like the difference between sRGB and RGB as Andrew pointed out. Also, you say, you have for several years had 10-bit monitors. That is no doubt true but what might be in doubt is whether you have been experiencing 10-bit display. A number of very specific conditions have to be fulfilled for that to happen. Many users are blithely unaware that what they are seeing on their '10-bit monitor' is just a dithered 8-bit simulation. You might like to check that out. Sorry to be a bit off-topic

.

[COBill]

Yes I realize that I've been seeing a dithered simulation. But my target for viewing is a 4K QLED (not OLED) TV so I doubt whether the difference matters. 2019 Samsung Q80. 

[FeedbackCommunityMember]

Apparently, LR V10.1 has at least 14 identified significant bugs and a whole bunch of crash reports. The latest release doesn't fix the bug being discussed here even though it's of fundamental importance to photographers. If I had run my business in a similarly cavalier fashion, I would have lost all my clients and gone bust before you could say Jack Robinson. Staggering incompetence made all the worse by staggering complacency.

[fastjedi]

I moved to Capture one today. I know and realize all softwares have bugs and sometimes major ones slip through. ( I have been a developer for years), But as a person whose business relies on Photo editing software (We deliver close to 75000 images to clients every year), I couldn't afford to play beta tester for Adobe anymore. I know downgrading to 9.4 was a good option, but to do that on 12 ongoing projects with over 1500-4000 images in each project, and creating a new catalogues for 9.4 (cause it does not allow downgrading for obvious reasons), losing all edits and culls, redoing stuff is just way to much time and money wasted as a full time business. I lost more man hours than 5 years worth of subscription. 

I sincerely hoped the update would fix issues, but no. I am keeping the subscription of course as Photoshop is indispensable for now. But that is all that remains in my Adobe software catalogue. So sad.....