Known Participant

Question

P: Colored "pixel" artifacts/subdued blacks in shadow areas (older Macs) (also visible on CR)

Forum|Forum|2 years ago
June 14, 2023
173 replies
111536 views

I updated LrC to 12.4 yesyerday. Since then a number of pixels in multiple colors appear appear quite often on the image, mostly in the areas of blacks/darks and when using Tone Curve commands. It's similar to the red/blue pixels which denoted clipping in the areas of blacks/whites, but they appear in very many different other colors. Sometimes they disappear, or decrease, after actioning the commands again, sometimes they do not. Is anybody else facing the same problem which I encounter now for the vey first time after many years of use of LrC? Thank you in advance for your advise.

macOS

This topic has been closed for replies.

Show previous replies

bgranofsky

Participant

Hi--fairly longtime LR user here. I'm running classic 13.0.1 on a MBP running 12.6.5 (it's a 2015 model so I don't think I can upgrade any further). Tonight, I experienced the seemingly common issue where blacks/shadows in my images were rendering lighter in the Develop module than in the Library module. I checked my Preferences and shut off the GPU as explained in other threads. That seems to have fixed the issue in the Develop module. However, when I export the images, the shadows and blacks do not render how they should--there is a lot of noise and those areas are generally lighter than they should be. You can see the difference in the background of the images below. I figured out a workaround where I sent the images to PS and exported from there (images were rendered fine that way) but that's a lot of extra work that I shouldn't have to do.

Is this a known issue? And will moving back to an earlier version of LR fix this issue? I shot/processed a few times this week without any similar issues. It only popped up tonight. Have also tried restarting/rebooting and nothing fixes it.

johnrellis

Legend

Lots of reports about this on older Macs (e.g. 8 years old) with graphics processors whose drivers are no longer supported by the manufacturer, and Adobe is actively investigating. Click the Apple icon in the upper-left corner and do About This Mac. Post a full-resolution screenshot (not a phone pic) of the About window so we can see precisely which hardware you're running.

Some report that setting Preferences > Performance > Use Graphics Processor to Off helps with the Export problem, while others report that it does not. There are many reports that rolling back to LR 12.3 works around the issue, with no reports I know of to the contrary.

johnrellis

Legend

Moderators, @Rikk Flohr: Photography, please merge with this bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-artifacts-resembling-clipping-warnings-odd-bright-colored-pixels-in-shadow-areas-older-macs/idi-p/13865745

W

wideshot photography

Participating Frequently

return to Lightroom v12

W

wideshot photography

Participating Frequently

@ouiouiphoto en effet ça ne change absolument rien !!

ouiouiphoto

Known Participant

Hello. Just for info disabling GPU does not seem to work when exporting. I have some users with GPU disable that have this problem when exporting. I have just tested in 13.0.1. Even if you disable the GPU, the GPU seem to be used when exporting.

.Sheepdog trying to help Lightroom and Photoshop beginners

R

Robin33383504l30q

Participant

Thanks JohnRellis,

Many have reported that setting Preferences > Performance > Use Graphics Processor to Off helps. This helps! Can't go back to LR12.3 because the library with a huge project is made in a newer version and is not accepted. Work around till problem solved. Hope it stays like this.

W

wideshot photography

Participating Frequently

Here we have all the same problem

Return on Lightroom 12

TheMatia

Inspiring

For a while, I've intermittently had lots of noise showing up in the image. I thought it was shadows/highlight clipping (different colours showing different colour channels), but I then turned them off (or thought I did) and they still showed up (see image below).

This developed a bit more today - I had the clipping/noise, but for the first time it has continued to the export and I had this horrible noise all over the shadows in the image. (see image below).

Is this a feature/bug? Does anyone know a fix?

Thanks,

Matt

johnrellis

Legend

Lots of reports about this on older Macs (e.g. 8 years old) with graphics processors whose drivers are no longer supported by the manufacturer, and Adobe is actively investigating. Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

Click the Apple icon in the upper-left corner and do About This Mac. Post a full-resolution screenshot (not a phone pic) of the About window.
https://www.lightroomqueen.com/community/help/createscreenshot/

Many have reported that setting Preferences > Performance > Use Graphics Processor to Off helps, as does rolling back to LR 12.3.

johnrellis

Legend

Moderators, @Rikk Flohr: Photography, please merge with the existing bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-artifacts-resembling-clipping-warnings-odd-bright-colored-pixels-in-shadow-areas-older-macs/idi-p/13865745

A

Amichai33409419e6fr

Participant

Hi,
I am using lightroom with a 2015 macbook pro 15". I keep it up to date. I am having a weird issue where there is shadow clipping in all my photos. I pressed J and toggled it on and off and it is always there. The clipping is even showing up in my exported photos. I cannot figure this out. Has anyone had this issue before? I attatched a photo that has been exported with normal presets that has the clipping in the shadow

H

helennium

Known Participant

If it's any consolation, they're actively working on it. After I responded on the forum to a post by Rick F. asking for people willing to interact with Adobe techs, I was contacted and last week I spent an hour on a videoconference with 2 techs and demonstrated the problem to them. At their request, I continue sending them logs when it happens again, as it did the day after I spoke with them. I share your frustration at having this wrench thrown into the Develop workflow, but I believe they are sincerely trying to figure it out.