Skip to main content
Adobe Photoshop Family
AC

13 Messages

 • 

194 Points

Thu, Oct 22, 2020 5:05 PM

Closed

Acknowledged

Lightroom Classic: Slow UI when using Mac and Custom Display Profile

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

Responses

35 Messages

 • 

404 Points

2 months ago

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!

16 Messages

 • 

214 Points

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.

35 Messages

 • 

404 Points

I wouldn't bet on that and I hope it's not the case.

27 Messages

 • 

398 Points

That's not likely, IMO. There is a lot of very advanced skill required to develop an application like Lightroom. This skill is very hard to come by in the marketplace, so Adobe is highly unlikely to let it go. I think the case is quite the opposite: there simply may be too many fires burning (e.g. Apple M1 silicon support) and too few top-tier developers going around within the Lr-Team to extinguish them all. You might be surprised by how small the core development teams of major and well-known applications are...

(edited)

891 Messages

 • 

10.4K Points

The 1st team is working on the massive conversion to the new Apple hardware and software. That's a mammoth project. General maintenance and support for old Apple hardware / software is on the 2nd team and a bunch of new hires / contractors. Anybody who's ever worked in a large development organization can tell you that this is how it works. Fact of life folks, we are just going to have to suffer through it. 

16 Messages

 • 

214 Points

well, maybe, but one would think that the "A" team might be a bit concerned that the issue affect custom display profiles might not just go away with the migration to new hardware...

I also find Rikk's equating MacOS users who use custom display profiles with a "small group" a little complacent.

2 Messages

 • 

70 Points

2 months ago

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.

(edited)

27 Messages

 • 

398 Points

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).

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

(edited)

2 Messages

 • 

70 Points

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.

(edited)

9 Messages

 • 

232 Points

2 months ago

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

35 Messages

 • 

404 Points

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-be-installed-contemporaneously/5fa871ae0796af4b5ad82da7?commentId=5fa88db103c8ec0f52010941

DYP

69 Messages

 • 

764 Points

@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.

(edited)

9 Messages

 • 

232 Points

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

DYP

69 Messages

 • 

764 Points

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

3 Messages

 • 

82 Points

2 months ago

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.

2 Messages

 • 

70 Points

2 months ago

Hi, 

Right after install, I am having issues with extremely slow editing, scrolling through photos, adding or applying changes to images.

The laptop was new and had 16 GB but now it is upgraded to:

Device name DESKTOP-C69QGDA
Processor Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz   2.30 GHz
Installed RAM 64.0 GB (63.9 GB usable)
Device ID 455D2FFB-86F5-4D5D-9408-D46ACF0BF1E9
Product ID 00325-81810-72643-AAOEM
System type 64-bit operating system, x64-based processor


I can no understand what is causing the problem and making the lightroom almost unusable?

Can you look into issue please, if this is not improved i will ask for refund as free software does 10x faster job in editing pictures from my SONY a7ii which is pretty old and images are tiny in size.

Thanks

Note: This comment was created from a merged conversation originally titled LIghtroom Classic: Slow editing/scrolling

Adobe Administrator

 • 

1.1K Messages

 • 

18.7K Points

This thread is being merged into an existing thread for better tracking and response.

2 Messages

 • 

70 Points

2 months ago

I have the exact same problem it is unworkable, I do not want to hassle with reverting back to 9.4. Catalog is too big to export and then import from. We just need adobe to fix this bug quickly. It is impossible to get any work done in a timely manner!

Big Sur running lightroom 10.1

stuck like this until I shut it down- super frustrating!

iMac (Retina 5K, 27-inch, Late 2014)

4 GHz Quad-Core Intel Core i7

32 GB 1600 MHz DDR3

AMD Radeon R9 M290X 2 GB

149 Messages

 • 

1.5K Points

Did your IT department approve your upgrades? Oh, you don't HAVE and IT department? Did you ever see a corporate computer user without an IT Department (onsite or off)? You are your own corporation, get an IT department (there are probably inexpensive options within 50 miles)! If I was your IT, (and for 25 years, I was a Mac IT Pro), you would NEVER have moved to either Big Sur or LR Classic V.10...yet. Be conservative in your device upgrades, look hard before you leap!

I'm not trying to rub it in, merely suggesting "act like a company".

2 Messages

 • 

70 Points

got it but maybe adobe should not release updates until they are sure they will work for everyone and yes I have an IT guy I can consult with, many others are having the same issue.

891 Messages

 • 

10.4K Points

You expect Adobe to test on literally millions of combinations of hardware and software? This means that you are willing to pay $thousands per month for a Lightroom license.

 

Have you noticed that only a tiny percentage of the Lightroom customer base is having significant issues? We are not seeing tens of thousands of complaints across the various photography and Apple forums. When I search other sites, I find the same people posting on multiple sites. 

 

Further examination of the posts on this site show that the majority with issues are running antiquated versions of macOS and Mac hardware.

 

DYP

69 Messages

 • 

764 Points

Here we go with your BS again about antiquated versions of macOS and Mac hardware.

That is simply not the case. 

891 Messages

 • 

10.4K Points

Your rejection of evidence is sad. 

  

27 Messages

 • 

398 Points

I know - Catalina‘s been ‚antiquated‘ since November... :)))

DYP

69 Messages

 • 

764 Points

Yea and I am running an old 2019 MacPro.

116 Messages

 • 

2.6K Points

Sorry, Bill. I am getting a little upset too. I had posted the issue also and for one day I thought it had gone by changing resolution of the display. For any unknown reason the temporary performance boost disappeared again and I am struggling with the same performance issues again. But - and I can imagine others feel in a similar way - at some point in time you just get bored and tired and stop complaining, because - and I would love to see a change in communication from Adobe - you don't get the feeling that Adobe is really listening. An update here and there that the bug is being worked on, or questions back to the community or request for help - that is missing.  I have a MBP16 and latest LR and Big Sure - nothing outdated. Also, I have once followed all steps for a different bug - to test and reinstall and do this and that - we hear the same advises over and over again for all kinds of problems, but if you read the posts you realize that others tried this as well without success. Pushing customers to reinstall, reconfigure keeps them busy for a while or at some point in time they stop complaining, maybe stop posting issued and after a while they simply may have gone to competition.

I loved LR since the very first days and I am sure most users do like the concept and interface. Still, many don't request tons of new features and miss performance of older versions running faster on older hardware. 

I remember the day where Adobe product management rolled back after some not thought-through changes in the import interface after lots of users complained. Some recognition of customers and maybe some more update regarding status of bug fixing in case of issues which professional photographs drive mad - luckily I do not depend on LR for my work, but if would, I would be mad as well. So I will keep fingers crossed and hope we get this issue fixed soon.

I recognise the endless efforts of Adobe reps bridging customers and product management , it is a tough situation sometimes and I thank them all for doing their best in bringing our voices into the teams. I know how difficult it can be working in a company dealing with similar sized software projects.

891 Messages

 • 

10.4K Points

You said: I have a MBP16 and latest LR and Big Sure - nothing outdated.

 

My son has both a MBP16 and a M1 Pro, not only with zero issues but he cannot recreate the ones reported here. His systems are absolutely stock, no special mods to either MacOS or to Lightroom. He also has a Dell 27" 4K monitor and Lightroom runs fine on both the external monitor and the laptop display. 

 

So what is different between your system and his? Problems like this don't just randomly occur. 

 

He's boxed up his MBP16 to sell but he still can check things on his M1. As the M1 is using Rosetta, I don't think researching problems on that platform are useful until the native version is released. 

66 Messages

 • 

838 Points

Sometimes, it is better to shut up one's mouth taking the risk of appearing dumb, than opening it and leaving no doubt.

11 Messages

 • 

174 Points

Really Bill.  Enough.  Most posters are NOT using hardware that is outdated. Your rejection of the evidence is the sad part.  Not to mention unhelpful and distracting.  

16 Messages

 • 

214 Points

Bill, whoever you are, I have LrC on 3 Macs of different generations and configurations, from quite old to very new, quite modest to powerful.  All run 9.4 (and Capture One 21) quite happily.

If I install LrC 10.x, then toggling between my custom profiles and sRGB toggles this bug like turning a light on and off.  Rikk has clearly admitted to this issue in his last update.

Was your son using custom profiles? If not, (a), I guess he's not that bothered about colour fidelity and (b) just shut up and go and spread disinformation on some other thread, rather than trolling people here who are already frustrated by this 3 month old showstopper they're paying for very month.

2 Messages

 • 

70 Points

2 months ago

Depuis cette grosse mise à jour qui m'a emmenée vers Catalina je n'ai que des problèmes.

Tout d'abord mon Mac est très ralenti dès que j'ouvre un fichier Adobe et Ligthroom est devenu un cauchemar.

J'ai un Pentax K1 et je travaille en RAW jusque là je n'avais aucun problème mais à présent il peine à importer, la retouche est extrêmement lente, chaque action se fait au ralenti et à présent lorsque j'exporte mes photos il s'éteint et la relance est extrêmement lente.

Je ne vois pas comment je peux continuer à travailler dans ces conditions !

Si vous avez quelques conseils je vous en serai reconnaissante.

Google Translate: 

Since this big update that took me to Catalina I have only had problems.
First of all my Mac is very slow when I open an Adobe file and Ligthroom has become a nightmare.
I have a Pentax K1 and I work in RAW until then I had no problem but now it struggles to import, the retouching is extremely slow, every action is done in slow motion and now when I export my photos it s 'off and recovery is extremely slow.
I don't see how I can continue to work under these conditions!
If you have any advice I will appreciate it.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Problèmes à l'exportation / Export problems

Adobe Administrator

 • 

1.1K Messages

 • 

18.7K Points

This thread is being merged into an existing thread for better tracking and response.

35 Messages

 • 

404 Points

Which existing thread, please?

Adobe Administrator

 • 

1.1K Messages

 • 

18.7K Points

That refers to the post immediately above from celinezug, not this thread. This is the thread that post was merged into. 

(edited)

16 Messages

 • 

214 Points

@celinezug il y'a deux solutions: ou bien retourner au version 9.4, ou bien utiliser le profile standard sRGB.  

Ou bien attendre....

33 Messages

 • 

422 Points

a month ago

I thought I'd just chip in here in case this helps any of you. I am now (I dread typing these words) problem free!

I have a 2019 27 inch Mac. At the time I was running Catalina.

I started having the problems discussed when the new LR release was launched (beginning of November); my screen froze completely every time I opened LR and then my Mac crashed. At that time Adobe told me to uninstall and reinstall LR, which I did to no avail.  Rick then told me to go to Apple as it was probably a problem there. This I did.

Apple helped me to erase my Mac completely and reinstall it. There were a few hiccups along the way, but when I got hold of a senior member of the Apple support team, things started to improve. I'm not a technical person (! at all!) so please bear with me, but as I remember it, when the Mac operating system was reinstalled, instead of using the Time Machine, it was all done manually to avoid bringing bugs back that may have been there. And from then onwards I haven't had any problems. Sorry to be so vague about the process, but it has worked.

35 Messages

 • 

404 Points

Does this mean that with any major Lightroom update, it will be necessary to completely erase and reinstall our Mac? This is not serious.

What bothers me the most about this story is that it will give arguments to those who claim that the problems are due to old hardware or old systems (you know who I'm talking about...).

Because there are two possibilities: either the new version is given as compatible or it's not. If it is, then let's stop blaming allegedly obsolete hardware and systems.

Belinda

49 Messages

 • 

630 Points

@ann_chown So, in other words, your problem had most likely nothing to do with the LR issue but was probably something else altogether. A full system reinstal sounds like a system issue not a LR issue. Correlation does not prove causation. The human mind likes to find patterns.

16 Messages

 • 

214 Points

yes, but what colour profile are you now using? If that was reset to default, well.......

33 Messages

 • 

422 Points

a month ago

I've also subsequently upgraded to Big Sur - all fine.

9 Messages

 • 

178 Points

a month ago

During installation, the update should check whether LR works properly with the existing hardware and software after the update. If this is not the case, the update must abort the installation.

7 Messages

 • 

72 Points

@Gerhard Tittel

keep on dreaming, Gerhard

When has this ever happened ??? 

149 Messages

 • 

1.5K Points

You mean the installer should import some images, edit them, check the slider speed, export them, check for OS crashes, etc. etc. Wow, that's a smart installer! ;-P

891 Messages

 • 

10.4K Points

Like Windows started doing a couple years ago, it could check for the TRUE minimum hardware and software requirements and not the joke requirements published by Adobe. I've had Windows updates automatically delayed by as much as 6 months because of hardware in my system.

 

Not perfect but it would work well if Adobe would take the minimum requirements seriously. At least half of the Lightroom V10 issues reported on this forum would have been prevented. 

Belinda

49 Messages

 • 

630 Points

...Still banging on about hardware when everyone, including Adobe, has stated the problem lies in the software. Give yourself and everybody here a break from your nonsense. 

...And of course you have solid evidence that "at least half of the Lightroom V10 issues reported on this forum would have been prevented"?

Of course not, it's just your dogmatic and unsubstantiated 'belief' but at least it represents a slight shift towards putting the blame where it belongs - Adobe. So well done for that.

891 Messages

 • 

10.4K Points

Your ignorance is only exceeded by your arrogance. 

DYP

69 Messages

 • 

764 Points

Projection at its finest.

66 Messages

 • 

838 Points

Is there someone from Bill's family here? Because, confusion, repetitions ad nauseam, reality deny, etc, could be the signs of a medical emergency.

9 Messages

 • 

178 Points

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

Belinda

49 Messages

 • 

630 Points

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. 

66 Messages

 • 

838 Points

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

Belinda

49 Messages

 • 

630 Points

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.

891 Messages

 • 

10.4K Points

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

66 Messages

 • 

838 Points

Again, where does this number come from?

In fact, you do not know.

Me neither.

2 Messages

 • 

70 Points

a month ago

I have been on chat for 2.5 hours with Adobe help.  After much trouble shooting, Version 9 works perfectly with Big Sur.  The issue is the preview speed on Version 10.1.1.  Jan 13th, there was an update to LR Classic and it totally messed up the preview speed in the program.  If you have this issue, reinstall version 9 LR Classic.  The issue is not with the graphics card or anything else with the computer, as all other programs work fine.  Hopefully this will save you hours of aggravation.

Note: This comment was created from a merged conversation originally titled Lightroom Classic V 10.1.1 Problems with Mac

Adobe Administrator

 • 

1.1K Messages

 • 

18.7K Points

This post is being merged into an existing thread for better tracking and response.

2 Messages

 • 

76 Points

@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.

891 Messages

 • 

10.4K Points

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. 

4 Messages

 • 

92 Points

@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. 

891 Messages

 • 

10.4K Points

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. 

 

Champion

 • 

5.6K Messages

 • 

98.2K Points

"I think that Apple stopped supporting Windows in Bootcamp last year."

Apple announced they wouldn't support Bootcamp on ARM Macs, but I haven't seen any announcement they've stopped supporting Bootcamp on Intel Macs:

https://www.pcmag.com/news/arm-based-macs-wont-support-boot-camp-apple-confirms

66 Messages

 • 

838 Points

So... a "much less expensive solution" to free Bootcamp is costing $2000

891 Messages

 • 

10.4K Points

Much less expensive than "$10k Mac Pro". I probably read your response wrong, I thought you were saying that you were going to buy a $10K machine to run boot camp. Sorry. 

1 Message

 • 

60 Points

a month ago

I also have this problem ! I'll now use the Adobe RGB profile as substitute and this helps. 

iMac (Retina 5K, 27-inch, Late 2015)

3,2 GHz Quad-Core Intel Core i5

AMD Radeon R9 M380 2 GB

1 Message

 • 

60 Points

a month ago

mixed experience here:

MacPro6,1 macOS 10.14.6:

LR9 just fine

LR10 lags badly unless main display set to sRGB in System Preferences, no matter what LR hardware acceleration and preview settings

MacBookPro11,5 macOS 10.14.6:

LR9 and LR 10 just fine

2K Messages

 • 

24K Points

@user  On that Macbook Pro, try Adobe RGB (1998) instead, any better? At the very least, the color should be better as this is a wide gamut display. 

Author “Color Management for Photographers"

12 Messages

 • 

178 Points

a month ago

This problem is still going on with no end in sight. Is there anybody from Adobe that can at least assure us that they are trying to work on this problem?

As many others I have discovered that using SRGB profile is the only thing that lets lightroom work normally which of course means color calibration it’s not possible

I have discovered a semi work around in that after trying many profiles I have discovered that the Wacom Cintique pro RGB profile works with few delays and this closer to my own monitor calibration profiles but not perfect

However it is clear that it is a software problem so if you are listening Adobe please let us know that you were working on it or if not then we can move on.  

(edited)

Belinda

49 Messages

 • 

630 Points

@olga_runciman

Adobe are deaf.

Adobe don't care.

Adobe don't do customer service.

You're supposed to wait in line with your mouth shut and suck it up until they get around to it.

......Don't hold your breath.

 

(edited)

149 Messages

 • 

1.5K Points

The anger of some Adobe users is deep, but knowledge of human nature tells me they don't want to lose their homes if Adobe went under (so they do care). And some just care because they like people and want to be helpful.

Belinda

49 Messages

 • 

630 Points

Yes they care  in much the same way as banks, utility companies and other giant corporations care.

DYP

69 Messages

 • 

764 Points

You mean care about the stockholders first.

2K Messages

 • 

24K Points

You mean care about the stockholders first.

The stockholders are super happy because Adobe is making a big pile of money with some many customers. Seems they are doing something right here, even if a small group admittedly deserve bug fixes of which they will get.   

Author “Color Management for Photographers"

66 Messages

 • 

838 Points

Do you have an evaluation of what you mean by "small"?

If you have, please provide it here and provide your reliable source of information.

2K Messages

 • 

24K Points

Do you have an evaluation of what you mean by "small"?

A  small fraction of the installed user based which (from my conversations with Adobe under NDA of which I can't specifically share) is in the millions. More than a million that I can say, specifically how many more I cannot. 

If you assume even tens of thousands of users have suffered this bug, maybe you can explain why so few of that group has posted about this issue here and on many other such sites. Please attempt to gather say 100 unique customers of such reports if you can. 

(edited)

Author “Color Management for Photographers"

2K Messages

 • 

24K Points

@olga_runciman so if you are listening Adobe please let us know that you were working on it or if not then we can move on.  

They know, they are listening and, a fix is coming. I could tell you a date too, but Adobe's lawyers would have to kill me, then you <g>. 

Look Adobe didn't go out of its way to introduce this. Its really rare and nasty bug and it was difficult to pin down then fix. But again, a fix will come. There are workarounds in the meantime and posting here about it will not make the fix come any faster (kind of the opposite actually). 

(edited)

Author “Color Management for Photographers"

27 Messages

 • 

398 Points

Andrew, while it’s nice to hear from you that a fix is coming, this is information that should really come from Adobe. They need to own up to this - we are paying subscribers to a currently dysfunctional product.

Naturally they didn’t introduce this bug on purpose - but that doesn’t change the fact that they did introduce it. From reading the reports here, the bug seems easy to reproduce - it certainly was in my case, starting with a clean OS installation. So they should know by now how this bug is caused...

And even if it is a bug that arises due to underlying issues in macOS, the very least Adobe could do is to create a version of LrC that works around the issue and that is compatible with v.10 catalogues, contact users who have reported here on this forum to be affected by this issue, and provide them with an installer. That’s certainly possible, since v.9.4 was not affected. That would give them all the time they need to work on a real fix while keeping their customers happy. And I think most if not all of us affected by this bug would be happy to work with the v.9.4 feature set if we could preserve the edits we’ve done since upgrading to v.10. Now that would be customer service!

I’ve experienced exactly this kind of attitude with software vendors far, far smaller than Adobe. If they can afford to do that, Adobe certainly can!!

It‘s been over three months without a real fix - that‘s simply unacceptable in my book!

(edited)

33 Messages

 • 

410 Points

@Ron_Pfister I had made this suggestion a while back. Pull out 9.4 branch, plug in the new camera profiles, perhaps update the catalog format, change the filename of the preferences file to reflect the current version which would allow people to run 2 versions of LR w/o any major issues. Also, export picks/stacks/albums/virtual copies to the xmp so anyone can export those and rebuild a new catalog with any version of LR w/o losing data.

2K Messages

 • 

24K Points

From reading the reports here, the bug seems easy to reproduce...

Yup, very easy. IF THE BUG affects you. How many minute's did it take folks affected by the bug to see they were affected by the bug? 

ONE person in pre-release was affected among many more than that number of testers who were not. It's a rare bug, full stop. Rare in terms of the installed based of users and previously within internal and external testing groups. The fix is coming. 

You can roll back to the last version, that's why Adobe provided a catalog backup. Oh, folks updated and didn't keep their legacy catalog or kept working on the new one instead of stopping and considering going back.

You can decide not to update immediately to see if such bugs affect more users after release if you do production work, you're a real pro who can't afford not to have everything working. 

I had made this suggestion a while back. Pull out 9.4 branch, plug in the new camera profiles, perhaps update the catalog format, change the filename of the preferences file to reflect the current version which would allow people to run 2 versions of LR w/o any major issues.

“There seems to be some perverse human characteristic that likes to make easy things difficult.” -Warren Buffett

First, your suggestion is based on what knowledge of the Adobe code base? You make it sound like a very simple fix, you sure?

If Adobe detects the bug issues to branch as you suggest, why not just fix it? 

How many software packages has your company produced? 

Next, take the teams limited resources to do this IF EVEN POSSIBLE? 

This is pointless but if venting makes you feel better, you'll still be waiting just as long for a bug fix! 

Author “Color Management for Photographers"

2K Messages

 • 

24K Points

Andrew, while it’s nice to hear from you that a fix is coming, this is information that should really come from Adobe.

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

(edited)

Author “Color Management for Photographers"

11 Messages

 • 

174 Points

Andrew: phrases like "Adobe's lawyers would have to kill me, then you" undermine your believability.  If your information is correct, it should be coming from Adobe and makes me wonder why Adobe wouldn't be providing it. You go on to say: "posting here about it will not make the fix come any faster (kind of the opposite actually)", which suggests you really have no idea what you are talking about.  If posting about the problem makes Adobe purposely slow down the fix we have a far bigger problem.  Provide actual information or stick to your knitting.  Thanks. 

149 Messages

 • 

1.5K Points

Andrew was making a joke, Seth! Sheesh, lighten up Homes! We can all use a little humor here, right? Remember humor? Adobe engineers don't need more stress, I think that was his point, and on that everyone can agree!

2K Messages

 • 

24K Points

Andrew was making a joke, Seth! 

Yes I was Carlos, seems unlike you, Seth missed my deliberately placed <g> and is a bit humor im-impaired. <g> 
And for Seth, one more: <g>

Author “Color Management for Photographers"

66 Messages

 • 

838 Points

@andrew_rodney 

Hi

OK for humor, OK for NDA, even OK for "small".

But debugging is not Rocket science.

Have a computer where the bug happens
Compile with max debug level

Disable new developments one by one, or package by package
Analyse

It should take some days, not months.

The only reasonable conclusion is that this bug is absolutely not a priority for Adobe (I can understand in COVID time...)

"Hard to find" bugs is just a very romantic approach to the problem: you know what you have modified between 2 versions!!

If Adobe is able to track all modifications between V9.4 and V10, then it is very a elementary development technic.

Another possible "issue" could be Adobe has lost V9.4 sources and CVS or equivalent basis for tracking modifications. This can happen when you get serious issues at the same time on your main storage and on all you backup storage, local, and at least 2 remote storages.

If this kind of problem happened, I would be very patient and very understanding.

Kind regards
Thierry

2K Messages

 • 

24K Points

But debugging is not Rocket science.

It should take some days, not months.

Your experience and understanding the Adobe source code is exactly what sir? 

Or you're again assuming...

Again; your experience in production of this software is what?

Or you want us to believe Adobe want to have such bugs and are not taking a fix serious based on what data from Adobe? Be very specific please; no more assuming.

(edited)

Author “Color Management for Photographers"

79 Messages

 • 

1.3K Points

Reminds me of the quote:

"No job is too difficult or too expensive for the man who doesn't have to do it himself"

2K Messages

 • 

24K Points

"Hard to find" bugs is just a very romantic approach to the problem: you know what you have modified between 2 versions!!

And no ideas how the OS and enormous number of hardware differences differing users work on affect a product until you do.

I have NO SUCH bug issues today or with any build of the product: specifically tell me and Adobe why? 

You assume again, this bug is easy to find and easy to fix. Without data and experience with this issue, you're just another poster with a opinion. 

Remember that old saying about opinions? ;-)

Author “Color Management for Photographers"

66 Messages

 • 

838 Points

@andrew_rodney 

My experience is multi millions lines software developments and CMM5 software quality insurance auditor.

There are basic development principes that you just seem to ignore, that do not depend on the kind of software you develop.

If you do not understand that tracking modifications from a version to another, disabling them one by one, is a basic and simple way to track bugs, I cannot help you.

Kind regards
Thierry


2K Messages

 • 

24K Points

My experience is multi millions lines software developments and CMM5 software quality insurance auditor.

As I suspected, zero understanding of how to code for Adobe products, and their audience. Of course, your software products are utterly bug free! 

There are basic development principes that you just seem to ignore, that do not depend on the kind of software you develop.

As you've ignored the huge number of Adobe customer hardware, OS versions, 3rd party OS hacks installed, lack of updates to drivers etc. 

You've ignored that Adobe has recognized, admitted and has said they are working on a fix. 

I cannot help you.

Or Adobe. Or their customers. But if venting makes you feel better, by all means, knock yourself out. 

Author “Color Management for Photographers"

66 Messages

 • 

838 Points

You only need ONE computer where the bug happens. So please stop talking about the huge number of possible configurations.


66 Messages

 • 

838 Points

In case you do not realize, playing Adobe Advocate with void useless information and customers contempt, will hurt you, one day or another.

11 Messages

 • 

174 Points

Andrew:  I understand the sarcasm <g>, but what is the point?  You know these details about Adobe and the imminent "fix" because......????  You spout your credentials, belittle others, and provide no real information.  Thanks for your contributions <G>

2K Messages

 • 

24K Points

You only need ONE computer where the bug happens.

The absurd is the last refuge of a pundit without an argument.

You know these details about Adobe and the imminent "fix" because......????

I've been an Adobe beta site since 1991, I routinely (multiple times a month) meet with various team members, I communicate with other testers, some here WITH and testing the bug fix. 
Of course you can ignore all that and keep assuming about bugs and when a fix will result without any of the data I have and reported if that makes you happier.

Fact: rare bug. Not solely Adobe code.
Fact: bug will be fixed properly and released when Adobe feels that is prudent.
Fact: work still being done, bug fix means build needs internal then external beta testing.
Fact: rushing one fix can introduce other bugs if the process is rushed without this process. Is that what you want to see?
Fact: Patience is a virtue.

Author “Color Management for Photographers"

891 Messages

 • 

10.4K Points

Andrew,

 

You are wasting your time. Millions of Lightroom users are not having these issues while a few dozen are. We know where the problem lies.

 

Sure Lightroom, like all software, has bugs. They will be prioritized with all the other development work. What's #1, migrating to the new Apple hardware and software as that is of benefit to millions. 

  

People who think that their problem should be #1 live in a dream world. 

  

5 Messages

 • 

122 Points

a month ago

I experience the same problem with LR10 (MacPro 5.1, 64 Go RAM, Radeon RX 580 8Go).

Moreover, some colleagues of mine have the issue with Adobe Premiere Elements 2021 on new iMacs 27 using Mac OS Big Sur. The only solution is to set to sRGB in System Preferences with both softwares...

Really problematic.