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

[Andrej Michelcich]

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.

[helennium]

LR 13 does not fix the issue and I am increasingly regretting having installed it. I have had such bad experiences downloading new version .0 releases of LR I usually wait until they're at .1 before updating. I can't work like this. It's frustrating and I see I'm not the only one.

[defaultyotvxy3nwfkw]

why does this keep happening when I go to edit anything in the Develp Module - help! It's impossible to edit correctly.

[kglad]

what app?

[defaultyotvxy3nwfkw]

Lightroom Classic 12.5

[defaultyotvxy3nwfkw]

wow I should've read some threads first because I found a previous post that fixed it so posting it here -

 

[kglad]

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.

<"moved from using the community">

[dholt8569]

Using lightroom classic on a macOS Monterey:

I have started having an issue where my images look like clipping is turned on the shadows but it isnt. I will be editing and sometimes it will fix itself but a majority of the time the screen shows distortions in the shadows. When the image is exported though it looks fine. Anyone encountered this or know how to fix? Could it be a computer issue?

[John R Ellis]

@dholt8569, the driver for your computer's graphics processor may be old and no longer supported by the manufacturer. 

1. 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/

2. As a workaround, set Preferences > Performance > Use Graphics Processor to Off.

[dholt8569]

Now I understand, thank you. That worked!

[g.a.d20504080]

I have strange colors. Mostly during the developer mode.

What am I doing wrong.

I can’t find it.

Version 12.5 and also 13.0 

[John R Ellis]

@g.a.d20504080, please see this previous post:

https://community.adobe.com/t5/lightroom-classic-discussions/p-artifacts-resembling-clipping-odd-col...

[Darren32963392ix6n]

Anyone else having an issue where the image looks fine in Library mode, but the second you switch to Develope mode everything gets wonky? Would be fine, except the exports are all messed up too.

[Darren32963392ix6n]

Turning off the GPU fixed the issue for viewing and editing the images. It even correctly exports for PNG formats. But JPEGs are still messed up.

Is there a known fix for that?  Or is there a way to roll back to a previous version of Lightroom that actually works?

[daveRedShed9UK]

What issue are you seeing with JPG exports?  Thanks

[Darren32963392ix6n]

Same issue that pops up in the Dev display. Except deisabling the GPU wouldn't resolve it. 

I had to roll back to 12.5 from 13 to to fix the issue.

[Malcolm15C3]

I guess you figured it out.  But for others who might come after you who don't know how to do this.  Backup your catalogue before you do this.  Or duplicate the files afterwards if you prefer.  Note that you might have a problem going from a much newer version to a much older one - check your catalogue backups for one that's more compatible if possible, although that'll lose any incremental work since it was created.

1) Launch the Creative Cloud app:

2) Navigate to Apps > All Apps > Three dot menu after Lr Cl > Select "Other Versions":

3) Select the version you want.  It works pretty well.

[daveRedShed9UK]

Hi 

When I am editing in Develop mode my disply goes bonkers and is becoming unusable.  It happens on my Macbook screen and the attached monitor.  I know it's not clipping.  I am wondering if I have enabled some weird setting or if I have a bug or hardware issue.  I have attached files of view vs develop

Thanks in advance.  It's drving me nuts!

[Pamelaann]

Hello 

Does anyone know why all of a sudden I get this overlay/artifacts on my images in the Develop pannel?  Showing underexposed areas.  Does not show up in the Library view side.  How can I get rid of it?  It will come out on Jpegs when exporting from the Develop side.

TY

Pamela 

[daveRedShed9UK]

Looks like a known issue.  I disabled my graphics processor.  Problem gone but slower.  Re-enabled to demonstrate the issue.  Still no problem.  Worth a try?  Restart between settings changes.  Good luck

[John R Ellis]

@daveRedShed9UK, "Mid 2015 MacBook Pro"

Please do the LR command Help > System Info and paste the output here so we can see the exact graphics processor and graphics memory you've got.  That will help identify the precise boundaries of the problem.

[daveRedShed9UK]

Lightroom Classic version: 12.5 [ 202308091523-68a7abd6 ]

License: Creative Cloud

Language setting: en-GB

Operating system: Mac OS 12

Version: 12.2.1 [21D62]

Application architecture: x64

Logical processor count: 8

Processor speed: 2.5GHz

SqLite Version: 3.36.0

Built-in memory: 16,384.0 MB

Real memory available to Lightroom: 16,384.0 MB

Real memory used by Lightroom: 940.3 MB (5.7%)

Virtual memory used by Lightroom: 36,874.4 MB

Memory cache size: 54.5MB

Internal Camera Raw version: 15.5 [ 1595 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 256MB / 8191MB (3%)

Camera Raw real memory: 261MB / 16384MB (1%)

Standard Preview Size: 2880 pixels

Displays: 1) 2880x1800, 2) 1920x1200



Graphics Processor Info:

Metal: AMD Radeon R9 M370X

Init State: GPU for Image Processing supported by default with custom export support

User Preference: Auto



Application folder: /Applications/Adobe Lightroom Classic

Library Path: /Users/Dave/Pictures/ATTICUS/ATTICUS-v12.lrcat

Settings Folder: /Users/Dave/Library/Application Support/Adobe/Lightroom



Installed Plugins:

1) AdobeStock

2) Aperture/iPhoto Importer Plug-in

3) Aurora HDR

4) DNA Pentax and Samsung Tether Plugin for Lightroom 5

5) Flickr

6) Luminar AI

7) Nikon Tether Plugin



Config.lua flags: None

[daveRedShed9UK]

Hi John

The problem is back now!

Lightroom Classic version: 12.5 [ 202308091523-68a7abd6 ]
License: Creative Cloud
Language setting: en-GB
Operating system: Mac OS 12
Version: 12.2.1 [21D62]
Application architecture: x64
Logical processor count: 8
Processor speed: 2.5GHz
SqLite Version: 3.36.0
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 940.3 MB (5.7%)
Virtual memory used by Lightroom: 36,874.4 MB
Memory cache size: 54.5MB
Internal Camera Raw version: 15.5 [ 1595 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 256MB / 8191MB (3%)
Camera Raw real memory: 261MB / 16384MB (1%)
Standard Preview Size: 2880 pixels
Displays: 1) 2880x1800, 2) 1920x1200

Graphics Processor Info:
Metal: AMD Radeon R9 M370X
Init State: GPU for Image Processing supported by default with custom export support
User Preference: Auto

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/Dave/Pictures/ATTICUS/ATTICUS-v12.lrcat
Settings Folder: /Users/Dave/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Aurora HDR
4) DNA Pentax and Samsung Tether Plugin for Lightroom 5
5) Flickr
6) Luminar AI
7) Nikon Tether Plugin

Config.lua flags: None

[John R Ellis]

@daveRedShed9UK, "Mid 2015 MacBook Pro"

Metal: AMD Radeon R9 M370X"

AMD no longer provides updates to the drivers for that graphics processor. Of the people with these symptoms who have reported their detailed hardware here, they've all been on older Macs running on the AMD FirePro D500 (2013), the AMD Radeon R9 M390 (2015), and the AMD Radeon R9 M370X (2015), all of which were moved to AMD's "legacy support" at least a year or two ago.  

Given these symptoms appear limited to a small set of older Mac models/graphics processors with no-longer supported drivers, given that LR codes to the Mac OS APIs and not to specific GPUs, and given the hundreds of problem reports on the forums addressed by upgrading drivers (on Mac, by upgrading Mac OS), Occam's Razor strongly suggests this is a bug in the graphics driver rather than LR.   Adobe is constantly changing LR and Camera Raw's use of the GPU to provide better performance and more features, so it's likely that a code change to LR 12.4 trips over a driver bug in a way that the older code in LR 12.3 doesn't.  It's certainly possible that the code change in LR 12.4 was itself buggy, but given all the evidence presented so far, that seems less likely.

As you've already learned, setting Preferences > Performance > Use Graphics Processor to Off works around the problem. You could try setting Preferences > Performance > Use Graphics Processor to Custom and then select just Use GPU For Display -- that might perform better. I haven't seen reports here whether that works with these particular symptoms.

You've also indicated you're aware that people have reported rolling back to an earlier version of LR avoids the problem.

[daveRedShed9UK]

I understand yout thinking John, but you are missing a key point here.  This should have either been regression tested properly or Adobe should be clear about what is not supported by them any more in terms of legacy / deprecated platforms and acted accordingly in terms of customer contact and options.  

It's fundamentally a problem with the subscription model we are locked in to, and as such I think it is Adobe's problem.  If there were the option to just purchase the last working version as a one off rather than a contract I would happily do that as I know it is stable.

I guess an analogy would be - If you have a smart TV and watch netflix then discover no new content works on your TV but your still tied in to a contract would the issue lie with the TV manufacturer?   

To their credit I am speaking to a support engineer and sending him data and files so hopefully there will be progress.

I am in the middle of a large edit at the moment so don't want to risk upgrading or regressing.  I have another MBP and when I can find it I will test it on that.

Regards

[Malcolm15C3]

> To their credit I am speaking to a support engineer and sending him data and files so hopefully there will be progress.

Thank you.  I hope something comes of it.