Copy link to clipboard
Copied
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.
Summary:
We can still not replicate this failure on test or production machines at Adobe. This appears to occur on Lightroom 12.4/Camera Raw 15.4 and later on very old Macs (8 Years and older) and is likely due to out-of-date video drivers on no longer-supported or updated GPUs.
The issue manifests as visual color artifacts in the Develop view only but doesn't always appear on exported images. It can also manifest as less-than-black deep shadow areas.
Copy link to clipboard
Copied
correction:
1. Uninstall Lightroom
Copy link to clipboard
Copied
Do your exports render correctly? There are some comments in this report that 13 has a bug and GPU is used for exports even if it is disabled in the settings.
Copy link to clipboard
Copied
After exporting about 1000 photos, I did not notice the artifacts.
Copy link to clipboard
Copied
I came to this experimentally. Maybe it depends on the computer configuration. LR version 12 will not read the catalog from version 13. It works for now.
Copy link to clipboard
Copied
I’ve got an issue with Lightroom that I can't seem to resolve. I'll be using Lightroom with no issues, then all of a sudden all the blacks that are clipped will start showing up as clipped. Only problem is, I don't have that setting selected. If I hit 'J' the clipping marks don't go away. If I export the images the clipping marks are there. If I restart Lightroom and export the clipping marks are there.
I can get the marks to go away by restarting Lightroom, but I'm going mad constantly restarting. Sometimes the problem will happen immediately again and sometimes it won't happen again for 24 hours or so. Here is an exaple of what an exported image looks like when the marks are there.
I'm a professional photographer so I'm no stranger to Lightroom, but I can't seem to resolve this problem. Someone please help save my sanity!
Copy link to clipboard
Copied
Did you ever resolve this problem? I'm dealing with the same exact thing.
Copy link to clipboard
Copied
Help! I have a new Nikon Z6ii that I just bought new from Abe's of Maine Dec.1st to repace my old Nikon D4.
I primarily shoot action/sports photos. Last weekend at the tournament I took lots of photos.
I went to download onto my MacBook pro into LightRoom Classic and LR Classic needed to update.
I updated to LR Classic 13.0.2 and then downladed my first set of photos from my new camera.
As I am editing them I'm noticing weird pixelation in a bunch of photos.
Is this pixelation from my new Z6ii or the LR update? I can't find anything on the web addressing this.
I need to figure out so I can return my camera by Jan.1, 2024 if it's that's the problem. Thanks
Copy link to clipboard
Copied
I'm shooting Canon. So if you are infact having the same problem it has nothing to do with your camera. I really think it's a LR issue.
Copy link to clipboard
Copied
you can check your camera files in Adobe camera raw (photoshop) or nikon studio nx (free program).
Copy link to clipboard
Copied
>Is this pixelation from my new Z6ii or the LR update?
the artefacts you show here is the bug addressed in the thread your question got moved into. It is caused by the update to LR and not your camera. As you can see lots of people experiencing this due to an issue with the new code in LR 13 interacting with the graphics card driver of certain older graphics cards on older Macs and some windows machines apparently. SOme people are able to fix it by turning off graphics card aceleration in Classic but others have had to (temporaril) revert to LR 12. Read through the thread to see how this is being done.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I did a screeshare and sent logs last week. It's been radio silence since then....
it would be nice if they put a statement out considering the monthly costs to use this software
Copy link to clipboard
Copied
Please read the message sent by Lisa4BOYS on 9 december, it contains a real solution to this issue:
"you have to fully edit the image and then go to CALIBRATION and change it to Version 4 (it is set to Version 6). You will see the weird pixelation go away."
Copy link to clipboard
Copied
While I apprecitate the work around this isn't really feisable or sustainable. There has to be another way.
Copy link to clipboard
Copied
There is no other way until Adobe provides a workaround for the bug apparently present in the drivers for the GPU cards in these older macs. The drivers are never going to be updated (machines and GPUs are too old) so only way is if Adobe finds a workaround for the driver bugs that works with the new code introduced for the v6 process version. Barring that only feasible fix might be for Adobe to competely disable the GPU for these machines which would make Lightroom really slow or they might simply declare Lightroom incompatible with these machines. Not sure if this will ever get fixed therefore but hopefully Adobe surprises us.
Copy link to clipboard
Copied
Assuming Adobe fixes the LR 13 bug where Export ignores the setting of Preferences > Performance > Use Graphics Processor, then a workaround will be to disable use of the GPU. For many (but certainly not all) users on older Macs with less powerful graphics processors and smaller displays, this won't make much of a difference to performance, even for AI masking. (Denoise would go from excruciatingly slow to intolerably slow.)
Copy link to clipboard
Copied
I do not trust till now the new release 13.1., because it is not clear for me, whether this subject is solved or not. Would be godd, to get a clear statement.
Thx and greeting
Copy link to clipboard
Copied
I do not trust till now the new release 13.1., because it is not clear for me, whether this subject is solved or not. Would be godd, to get a clear statement.
Thx and greeting
By @oldpiefke
The release notes for 13.1 say that the issue "Image Export always uses GPU even when the preference is unset" is resolved:
https://helpx.adobe.com/uk/lightroom-classic/kb/fixed-issues.html
Copy link to clipboard
Copied
There is no other way until Adobe provides a workaround for the bug apparently present in the drivers for the GPU cards in these older macs. The drivers are never going to be updated (machines and GPUs are too old) so only way is if Adobe finds a workaround for the driver bugs that works with the new code introduced for the v6 process version. Barring that only feasible fix might be for Adobe to competely disable the GPU for these machines which would make Lightroom really slow or they might simply declare Lightroom incompatible with these machines. Not sure if this will ever get fixed therefore but hopefully Adobe surprises us.
By @Jao vdL
Wrong focus. Please ignore speculation about whether it's an issue with old drivers having bugs. Lr Classic 12.3 can use the GPU without a problem. Lr Classic 12.4 cannot. I.e. this is a bug that Adobe introduced. They can choose to debug/bisect their code and find what they did to cause the problem, or, as you suggest, they can choose to disable GPU support or the feature of GPU support that causes the problem on these devices.
Adobe can fix things quickly if they want to. This discussion has been going on for half a year, so clearly Adobe have decided not to prioritise it. They've tried to cut off people on older systems in Lr Classic 13 by requiring macOS versions that were only released in the last couple of years, but that's hasn't worked. It's amazing how many people continue to popup with this problem, but maybe in the grand scheme of things these are small numbers and somebody at Adobe has decided they're not worth spending money/time on and it won't sufficiently hurt their profits, reputation or shareholder value, or the risk of a law suit is too low. Meanwhile, they're continuing to take a monthly fee from people and giving nothing back. It's criminal, and they should either fix this or convert people on old versions that they won't fix to permanent licenses instead of continuing to take their money.
Copy link to clipboard
Copied
The arrogance and indifference shown by Adobe in relation to this problem is remarkable.
Copy link to clipboard
Copied
The arrogance and indifference shown by Adobe in relation to this problem is remarkable.
By @michaelk2309
Perhaps even contempt towards their users? We're just here to provide money for their shareholders.
Copy link to clipboard
Copied
That's not a solution it's a workaround and infeasible if you are working with a lot of images
Copy link to clipboard
Copied