Skip to main content
Andrej Michelcich
Known Participant
June 14, 2023
Question

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

  • 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.

This topic has been closed for replies.

173 replies

irenat33389049
Participant
November 27, 2023

Hi Rikk and thank you for reply. I have tried to use the V5 in the callibration pannel but the unwanted results looks even more evident. I scrolled down and tried version 4 and 3 which worked for me. So far, this is the best solution to this issue. Thank you.

Participating Frequently
November 26, 2023

Anyone having issues with the Lightroom update?  There is a soapy film on my images when I boost up shadows.  So hard to get rid of it.

 

{Title edited by Moderator}

 

kglad
Community Expert
Community Expert
November 26, 2023

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 cc desktop">
oldpiefke
Known Participant
November 25, 2023

Hey dear all,

 I have gone back to vers 12.3. and it works

some short question, which somebody could for shure answer, because I did perhaps some mistakes

missing things after going back to vers 12.3

- latest installed collections

- some picture are imported, which I have already deleted

- keyword section is a bit unsorted, but latest keywords are in

Thx in advance for a feedback

best regards from Cadolzburg to all 

Participating Frequently
November 25, 2023

Yes, it is as you say. If you have version 12 installed, you will have to fall back to a correspondingly older catalog, which hopefully is still stored on your computer. Of course, it only contains the pictures you took before version 13 was released and updated. I hope not too much is lost.

johnrellis
Legend
November 25, 2023

"What happens if your edits use features that aren't available in the older version?  Are those edits ignored?  Lr 12.3 (the only version that really seems to work) supports up to process version 5, yet photos from Lr 12.5 and 13 might be using process version 6."

 

Unsupported Develop settings will be ignored (e.g. Point Color), and the process version will automatically change from 6 back to 5. Most people likely won't notice the change from 6 to 5, which, according to the Lightroom Queen, is "a relatively minor change, this time with the aim of reducing banding. ...  The changes are small enough that you won’t likely want to update older photos in bulk."

 

If you don't save metadata changes back to file (manually or via the preference setting), then the LR 13 settings will remain in the .xmp files, ready to be read back in whenever LR 13 becomes compatible again.

 

But as I said, the "method is fraught with danger and limitations and easy to make mistakes."

 

Some have reported that the artifacts in display and export go away in LR 12.5 if you disable the graphics processor. If you want to retain the use of the graphics processor, then LR 12.3 is the latest version that consistently works.

Participating Frequently
November 24, 2023

What happens if your edits use features that aren't available in the older version?  Are those edits ignored?  Lr 12.3 (the only version that really seems to work) supports up to process version 5, yet photos from Lr 12.5 and 13 might be using process version 6.  I suppose the approach of saving changes in the metadata will work up to a point, and maybe will be good in most cases or will save a lot of effort/time over redoing the work from scratch, but any edits will need to be reviewed.

johnrellis
Legend
November 24, 2023

"Go back to version 12.x cannot work, because all archiv activities issued in 13 are from my point of view not reversable to vers 12. "

 

LR 12 can't read a LR 13 catalog. What some people do: In LR 13, select all the photos you've added or modified since upgrading to LR13 and do Metadata > Save Metadata To File. Then open LR 12, and synchronize the folders were you've placed new photos imported into LR13, to import them into LR 12. Finally, use the Library Filter bar to find all photos whose metadata status indicates "changed on disk". Select them and do Metadata > Read From File to bring in all the changes you made in LR 13.

 

This tedious method is fraught with danger and limitations and easy to make mistakes. So make sure you have working backups first!

oldpiefke
Known Participant
November 24, 2023

Go back to version 12.x cannot work, because all archiv activities issued in 13 are from my point of view not reversable to vers 12. If I am not right, please let me know.

oldpiefke
Known Participant
November 24, 2023

I can confirm. The exported files do have still the mistakes

johnrellis
Legend
November 24, 2023

@joshc58792239, "The majority of this thread seems to be focused on this issue appearing in the Develop module."

 

There are also many posts here of problems with export. Many report success with the following workarounds:

 

- Roll back to LR 12.3 with Preferences > Performance > Use Graphics Processor set to Auto.

 

- Roll back to LR 12.5 with Preferences > Performance > Use Graphics Processor set to Off.

 

Unfortunately, due to another bug, you can't disable the use of the graphics processor for export in LR 13.0.1. Hopefully, at a minimum Adobe will fix that bug in LR 13.1 (due in a few weeks), and then you'll be able to disable the graphics processor and work around the bug.