Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
24

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

Community Beginner ,
Apr 18, 2024 Apr 18, 2024

Copy link to clipboard

Copied

Hi,

 

Since just now, I've been experiencing a weird bug / crash in Lightroom Classic (on a Mac), where ALL my photos suddenly are fully covered in artefacts in the Develop module.

 

Screengrab from the develop moduleexpand image

(Screengrab from the Develop module in Lightroom Classic)

 

When I check the linked RAW + JPEG source files in Finder, they all seem ok (they don't look corrupted, nor show any artefacts here), meaning the issue is within Lightroom.

 

Screengrab from the RAW source file in Finderexpand image

(Screengrab from the RAW source file in Finder)

 

When I export images out of Lightroom (with any setting, edited or even not edited), the artefacts are also present on the export files.

 

Screengrab from the exported JPG imageexpand image

(Screengrab from the exported JPG image)

 

This problem started occuring soon after I applied the new AI noise reduction feature on just ONE (1) photo. 

 

I already tried:

 

  • Closing and re-opening Lightroom
  • Shutting down (fully), and restarting the computer after 1 minute
  • Switching the GPU accelrator setting in Lightroom on/off


MY SPECS

  • Lightroom Classic 13.0.1 - Build (202310121438-d2af310c)
  • Macbook Pro 16" - 2019
  • 2,3Ghz 8-core Intel Core i9
  • AMD Radeon Pro 5500M 8GB 
  • 32GB 2667MHz DDR4 memory
  • OS Sonoma 14.4.1

 

Any help would be greatly appreciated, because this makes the whole software unusable....

Thank you!

TOPICS
macOS

Views

27.1K
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Apr 29, 2024 Apr 29, 2024

We've investigated an issue with the macOS 14.4.1 update that affects systems running AMD series GPUs. 

 

The issue manifests as garbling of/artifacts in images in Develop/Edit views and similar artifacts in Exported images.  The problem can afflict Camera Raw (16.2.1), Lightroom Classic (13.2) and Lightroom Desktop (7.2).  Restarting the application should restore your Develop/Edit view and return you to the expected Export results. 

 

The hardware manufacturer's will need to identify the cause

...

Votes

Translate
replies 316 Replies 316
New Here ,
Sep 25, 2024 Sep 25, 2024

Copy link to clipboard

Copied

Regular Lightroom (not classic) 

Aaron36104484dbcp_0-1727262337233.pngexpand image

 

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 25, 2024 Sep 25, 2024

Copy link to clipboard

Copied

 

Screenshot 2024-09-25 at 7.08.31 AM.pngexpand image

Screenshot 2024-09-25 at 7.08.07 AM.pngexpand image

I don't know if this is helpful, but images also look different depending on how zoomed in I am.

 

Plus, each image will look normal in the preview bar on the bottom, but once in the view/edit mode, it starts looking like this

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 25, 2024 Sep 25, 2024

Copy link to clipboard

Copied

Hey there, We're sorry for the trouble.

 

Please try turning off the GPU and check if it works. (macOS) Lightroom Classic > Preferences > Performance. Then, from the Use Graphics Processor drop-down menu, select Off. Quit and relaunch Lightroom.

You can also check the details here: https://adobe.ly/3Y79o9z.

 

Let us know how it goes. 

Thanks!

Shivani 

 

 

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 27, 2024 Sep 27, 2024

Copy link to clipboard

Copied

Has anyone experienced this in Lightroom? I was editing yesterday and everything was perfect. This morning I went in and any photo I click on looks like this in 'Develop'.
I have closed out and gone back in. Same thing.
I've 'resest' the photo. Still the same.
Tried a different catalog. Still happening.
I'm stumped 🫣
Screenshot 2024-09-27 at 8.16.02 AM.pngexpand image

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 27, 2024 Sep 27, 2024

Copy link to clipboard

Copied

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 27, 2024 Sep 27, 2024

Copy link to clipboard

Copied

Thank you so much!

  • Go to "preferences" -> "Performance", and under "Camera RAW Cache settings": "Purge cache"
  • Also, under "Performance": set "Use Graphics Processor" to "Custom" instead of "Auto", and then: only "Use GPU for display", and not "Use GPU for image processing".
  • Restart LR

    This did the trick!!

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 02, 2024 Oct 02, 2024

Copy link to clipboard

Copied

Hi

I have strange artefacts only in the dev mode since the last update (13.5.1) and upgrade to Sonoma 14.7. 

Using a Intel MBP 2019. 

 

 

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 19, 2024 Nov 19, 2024

Copy link to clipboard

Copied

WhatsApp Image 2024-11-19 at 15.51.45.jpegexpand image

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 19, 2024 Nov 19, 2024

Copy link to clipboard

Copied

COMO RETIRAR ESSAS LINHAS? APARECEM ASSIM QUE CLICO NA IMAGEM PARA EDITA-LA.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 25, 2025 Feb 25, 2025

Copy link to clipboard

Copied

When i try to use Texture, Clarity and Presets I am getting this wierd color effect. Any idea what is going on or how to fix. See iimage below for details about computer.Screenshot 2025-02-25 at 9.50.43 AM.pngexpand image

Screenshot 2025-02-25 at 9.49.37 AM (3).pngexpand image

 

 

Screenshot 2025-02-25 at 9.32.34 AM (3).pngexpand image

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 24, 2024 Apr 24, 2024

Copy link to clipboard

Copied

As of a few months ago, my coworkers and I started having problems on our Intel-chip Macs where -- when editing raw-format images in Adobe Camera Raw (ACR) -- the image preview displays in a corrupted manner making it very hard to apply edits and preview edits in real time (see screen shot).  This is not happening when using ACR on my new M3-chip MacBook Pro.  The actual raw files are not corrupted and open just fine and the edits applied in ACR are showing up as applied when the files are opened in Photoshop or exported from ACR to other formats. 

It's only the working preview image that is displaying as corrupted and this happens with DNG files and with native camera files (CR2, NEF, etc.) and only when using ACR on Macs with Intel-chips like the Core i9. 

I've tried cycling through the different video card options (OpenGL and the like) to see if turning things on/off would resolve the problem on those Macs.  I've also tried changing my memory allocation and scratch disk settings.  No joy.

The initial view of the selected images is fine.  The corrupted preview image happens only after non-exposure changes are made (for example, using the scaling/crop tool or the tools for correcting parallax).  This seems to be a bug with ACR where it wasn't tested adequately on with non M-series Macs.

Is anyone else running into this?    corrupted ACR preview on Intel-chip Maccorrupted ACR preview on Intel-chip Macexpand image

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 24, 2024 Apr 24, 2024

Copy link to clipboard

Copied

This does happen now and then. Does restarting the computer fix it? I suspect that you are running out of either RAM or VRAM on the video card. You might also get white previews in ACR and failure to properly enhance images.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 24, 2024 Apr 24, 2024

Copy link to clipboard

Copied

I'm only seeing this on our Intel Macs and only in the last month or so after one of the ACR updates was pushed out.  We have 64 GB of RAM on most of those Intel Macs.  Restarting doesn't help.  Closing everything but Photoshop and Bridge doesn't help.  Changing memory allocation and video driver settings doesn't improve the situation. 

Not having any problems with my M3 chip Mac, so it seems as if the developers have made some change to ACR that doesn't play well with the Intel-based Macs.  We are not in a position to replace multiple Intel-based Macs for several years, so this is a serious problem for us.  

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 24, 2024 Apr 24, 2024

Copy link to clipboard

Copied

I have an Intel MBP at work and an M1 at home, and I have seen this on the MBP a few times, hence my post with personal experience. Have you disabled the integrated video card? That seems to cause all sorts of problems as well.

My gut feeling is that its VRAM but I only cared about a solution.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 24, 2024 Apr 24, 2024

Copy link to clipboard

Copied

I appreciate the replies and the suggestions, but I've tried everything including disabling the integrated video card and re-starting the machines between changes to the video and memory settings -- just to be extra vigilant to make sure that I was starting with a clean slate each time.   While disabling the video card can often temporarily resolve the corrupted ACR image preview, as soon as I'm back in Photoshop from ACR and try to use many tools like Liquify and certain Transform and live object edits in my PSD file then I'm out of luck until I re-check the box in the Photoshop Settings panel to use the video card again.  That's created a serious productivity hit having to constantly turn the video card back on and off dozens of times.

This happens with our work Intel Macs (which have all sorts of corporate-mandated software running in the background that I cannot disable because they are managed machines) and with my personal Intel Mac at home (which has different security products installed and running in the background) and I have complete Admin management on.  

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

I've only seen it happen twice on my work machine and restarting fixed the issue. That's all I have.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

Thanks for your replies.  I've submitted a bug report to Adobe.   My wife is having the same issues with her Intel Mac as well and she's running an earlier version of macOS (Ventura), so that rules out macOS Sonoma as the cause.  

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

On Windows, video cards and drivers are a huge headache. The Mac has avoided that, I suppose its much easier to test a limited set of hardware which is mostly from AMD. Yours is I believe the first post about this in these forums so hopefully its not a widespread issue.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 26, 2024 Apr 26, 2024

Copy link to clipboard

Copied

I had this happen again yesterday, restarting fixed it.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

If this appeared only after updating to macOS 14.4.1, then it is likely related to this: https://community.adobe.com/t5/lightroom-classic-discussions/p-gpu-develop-edit-view-and-export-arti...

 

Rikk Flohr: Adobe Photography Org

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

Yes sir it appears to be.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

I'm having this issue on multple Intel-chip Macs,using ACR rather than Lightroom.  Clearing the cache and other suggestions has been fruitless as a permanent solution.  Turning off the GPU processing resolves the issue for the ACR modifications, but once I'm in Photoshop proper I have to enable GPU processing again in order to make additional edits to images using options such as the Liquify tool.  The constant process of turning the GPU on and off and on and off is a productivity killer.  

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

ACR has separate settings from Photoshop vis GPU use.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

Yep.  As I've noted, the solutions posted to this thread apply only to Lightroom so I'm still out of luck, so the suggestion that a bad (or non-updated) video driver is the culprit seems to be correct.  Another difference is that when I'm encountering the corruption in ACR, only the large preview is corrupted.  I can make additional edits in ACR (although purely via guesswork) before opening the images and the images are opening intact in Photoshop.  Folks using Lightroom are reporting the corruption in their processed files and not just the preview images.

One thing I've tried since my first post last week about this issue has been to completely clear out all my caches via Adobe Bridge.  While it didn't resolve the corrupted previews issue for me*, flushing all my caches appears to have solved a different problem I was having with the AI Denoise tool in ACR (on our Intel chip Macs) that was causing every image to take 20 minutes to process and often failing at the last minute due to some unknown error.  After the cache flush, the same images are taking less than a minute each and (so far) they completing the Denoise process every time again.   

*the first few images allowed me to make edits as expected without a corrupted preview, but then the corrupted preview issue re-appeared by the fourth image and every subsequent image until I restarted the Mac.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 29, 2024 Apr 29, 2024

Copy link to clipboard

Copied

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

Jay@TeamPurple, "As I've noted, the solutions posted to this thread apply only to Lightroom"

 

Have you tried setting CR's Preferences > Performance > Use Graphics Processor to Custom and unchecking Use GPU For Image Processing?

 

johnrellis_0-1714429618649.pngexpand image

 

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines