P: (GPU) Develop/Edit view & Export artifacts after 14.4.1 Update (AMD-only) (affects Cr, LrC & LrD)

I use a similar Intel MacBook Pro at work and its plenty fast, although the CPU and Radeon are aging, they still hold their own. Switching to Apple Silicon is going to be the next best move, my (much cheaper) M1 Mac mini at home is quite a bit faster.

My LR 16.4 either runs very slowly or crashes on me multiple times. This is particularly true if I try to use the mask tool or the lens blur tool. I'm on a MacBook Pro 2019 and Sonoma 14.5. Thank you.


<Mod: Updated thread Subject line to correct the version number)

@defaultc1yqic8abtjh its definitely, like the rest of us, your GPU in your Mac. Have you tried disabling GPU in the Lightroom settings? This was a bypass for me and I just made sure I had smart previews made with my imported photos. This gets me by for now until a fix is made.

Help us out a little. What computer/OS do you have? Have you looked at these files in another viewer?

You might be seeing the jpeg previews embedded in the RAW files. 

Just to add - if anyone is in a critical situation and need a workaround, please try this as it has worked for me:

My Specs Before I proceed: 

2.3 GHz 8-Core Intel Core i9

AMD Radeon Pro 5500M 4 GB

Intel UHD Graphics 630 1536 MB

16 GB 2667 MHz DDR4

macOS: 14.5 (23F79) (Sonoma)

Workaround

I turned off GPU accelaration (leavng display ticked seemed fine) and made sure to have smart previews made for the files in question. You do this in library module, very easy to do. And make sure you have it ticked in the options that it uses the smart previews for the edit which should give you a good jump in performance. 

This is working for me and I am able to continue working on my jobs. Good luck to you all until the fix drops. 

Minus the RAM, I have the exact laptop as you and I am also having the eact same issues. I am VERY glad this is a widespread issue, albeit sad there's an issue at all, because I was envisioning having to buy a new laptop or move to my gaming system for edits. 

I noticed fully turning off (minus display tickbox) the GPU option let me edit without corruptions.

I am attempting to use Lightroom Classic to develop film photos. 

I took the photos on a Fujifilm X-T5 with 30mm f2.8 @ f11 ISO125. I have scanned, converted, and edited many hundreds of film frames with this process and this is the first time I am having this issue.

After importing the photos into lightroom I wanted to crop the photos before I converted the negatives using Negative Lab Pro. I opened my usual catalog and when the photos opened in the library tab they seemed normal but when I clicked the develop tab, they became this digital pixel mess. I've added photos with and without Negative Lab Pro conversion. 

I changed the names on the files and deleted the JPEG equivalent before importing the photos. I also imported them directly from the SD card from the camera. I did delete the photos and reimport them but no luck. 

Any clue why this happening?

@Lumigraphics- "I'm using a 2019 MacBook Pro with a 4GB AMD Radeon and haven't seen this since the 14.5 update. I just processed and enhanced 28 Canon RAW files and didn't have any issues. So this IS real (I've seen it) but its also intermittent and not affecting everyone."

Yes, we get that, but it's a very nasty bug that affects the Adobe flagship AI features and disabling the GFX acceleration essentially cripples the system performance so for the people it does affect, it really hampers their workflow.  Hopefully Apple does an OS update w/updated driver soon.  

>At some point it is not AMD's fault but Adobe's for not properly testing their updates out on what seems to be a pretty common system configuration prior to releasing it.

See RIkk's pinned reply. The problem was caused by the Mac OS 14.4.1 update. Not by any Lightroom update. Adobe cannot fix this as far as I can tell. There really has to be a Mac OS update for this to get fixed unfortunately and unfortunately Apple is not the most responsive in fixing problems in my experience but hopefully Adobe has a way to make sure the APple engineers pay attention to this one.