Skip to main content
Participating Frequently
November 11, 2022
Question

Crippled Lightroom on MacBook Pro

  • November 11, 2022
  • 2 replies
  • 1238 views

Dear Adobe... Why the hell did you cripple older Macs (2+ years old) with the latest "improvements" of Lightroom Classic? Seriously. The new AI features were great while they worked, but I'd trade them in a heartbeat for an upgrade that actually served the needs of all users from those with baseline specs to the most expensive models.

 

Given that I can't upgrade the VRAM without upgrading my computer (not an option when I'm trying to budget for new lenses), does anyone have workarounds to deal with the crash-happy LR12's VRAM issues?

This topic has been closed for replies.

2 replies

Community Expert
November 11, 2022

My main Mac Book Pro machine is 5 years old and all the AI features work just fine. What is happening to yours? It should work on a 2 year old machine - whichever one it is - just fine. Can you put the results of Help->System info?

Participating Frequently
November 11, 2022

Interesting. Here's the system info. If I've read the bug reports correctly, there is no solution other than buying a new machine or installing the last version. 

Community Expert
November 11, 2022

What will it not do and what are the bug reports you are talking about? This machine should work just fine but perhaps not have GPU support for using the GPU for export. Perhaps not super crazy fast but should work. Perhaps I am not aware of an issue.

TheDigitalDog
Inspiring
November 11, 2022

If you wish to roll back to an older version, use the Creative Cloud application, click on the three dots (...) and select “Other Versions”.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Participating Frequently
November 11, 2022

Cool idea, except that the upgrade also upgraded the catalog... and I've done a lot of work since that time. This means I either lose a ton of photos or try to rebuild it. What's your advice then?

 

Community Expert
November 11, 2022

Apparently downgrading to 12.0 instead of 12.0.1 might solve the issue for now so worth a try. That should be able to read your current catalog