Raw file in ACR 15.3 looks nothing like it should be when opened

[davew68773894]

Hi, thumbnails in ACR 15.3 appear normal, but when opened in ACR 15.3 they look over contrasted and over saturated. When you open the file with zero adjustments in Photoshop, they revert back to the same image as the thumbnail in ACR 15.3.

[TheDigitalDog]

Thumbnails viewed outside of Lightroom Classic? The processing of anything in Lightroom Classic is proprietary and based on the import settings used. Thumbnails are built outside LR (perhaps by the camera using its JPEG conversions or the OS). Never expect a match. 

Also, the only way to evaluate color and tone is when the image is viewed in Develop at 1:1 or greater zoom, not elsewhere or zoomed out as the data is subsampled. 

If you view the image at 1:1 in Develop and Photoshop at 100%, you should see a perfect match. If not, we can look into issues like a display profile or GPU issue. 

[davew68773894]

Hi, thanks for the reply. Switching off the graphics processor solves the problem, but I get a prompt to switch it back on when I blend multiple images for HDR. I gave permission for Adobe support to share my laptop and their only solution is to update to Windows 11, which is not simething I want to do. However, if that's the only solution, then I will give it a go.
Watch this space 🙂

[D Fosse]

Uppdating to Win 11 won't solve anything. Updating your GPU driver should, assuming they've fixed the bug.

Which GPU are you using?

[davew68773894]

NVIDIA GeForce RTX 3070 Laptop GPU, Intel(R) UHD Graphics.

[TheDigitalDog]

First, try disabling GPU in the preferences (Performance) or alter the settings. Any better?


If turning OFF the GPU works, it's a GPU bug, and you need to contact the manufacturer or find out if there's an updated driver for it. This is why disabling GPU is an option as more and more functionality moves to the GPU in newer versions of many Adobe products. Disable third-party graphics accelerators. Third-party GPU overclocking utilities and haxies aren't supported.


Also see: https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html

Check to see that your GPU meets system requirements.

[bitzoid]

This is a real issue, ever since the update to Adobe Camera Raw version 15.3 "three days ago" (4/20/23?) which added AI noise reduction (and mucked-up the Detail adjustment tab UI, fwiw).  Thumbnails in Adobe Bridge 13.0.3.693 are fine, but if opened in Camera Raw 15.3 "AI", the result is a verk dark image to work with, even if it has been previously developed correctly in Camera Raw.  Attempting to boost the the apparent darkeness via Shadow or Exposure results in the dark areas lightening, but with extreme banding, such as with low bit-depth.  But when exported, such as to .jpg, the images display higher bit depth (smoother darks); but are misadjusted because the image in Raw is fundamentally wrong.  This only began a couple days ago with the update to Raw 15.3 "AI".  Attached are screen shots showing Bridge in the background, selected thumbnails on the right, with Camera Raw on top to the left.  Compare Camera Raw view to the top right selected thumbnail (as well as all the tumbnails in Raw at the bottom). 

Windows 10 (21H2), Intel UHD Graphics (30.0.101.1069), desktop HDR 32 Bits.  Adobe Raw, standard Adobe Color, Space Rec. 2020, 16 Bits/Channel (non-HDR demo mode). 

Attached screenshots:

20230423_PS_Raw_borked.jpg - Raw on top of Bridge, no adjustments.

20230423_RAW-Preview_borked_20230416_Prev_Adjusted.jpg - Raw on top of Bridge, image previously processed in Raw

[Fotomaker01RA]

These two Win 10 users seem to be having similar issues. Has anyone using Win 11 updated to ACR 15.3? And, if so are you experiencing similar thumbnail issues? Thx.

[D Fosse]

Attempting to use Denoise with Intel UHD 630 integrated graphics won't work. You need a newer and more powerful dedicated video card.

Like it or not, but Denoise is by good margin the most GPU-intensive function introduced so far in Photoshop/ACR/Lightroom. It won't run properly on old GPUs, and it won't run properly on integrated GPUs with limited resources. It doesn't require a very expensive high-end GPU, but it does need to be fairly recent, mid-range and up.

[bitzoid]

This issue started with the recent inclusion of *the option* to use AI noise reduction in 15.3, not its actual usage. It appears the Camera Raw "Auto" setting for GPU usage now invokes the nVidia 3080 GPU from the start of a Raw session, and there is a (Gamma?!) mismatch between the two GPUs; which seems crazy for a handoff like this these days.

So I can confirm this setting "works", to get back to basic functionality:

Settings | Performance | Use Graphics Processor: Off

Intel UHD Graphics (30.0.101.1069)
Graphics acceleration is disabled.

While the "Auto" (default) or "Custom" settings result in the issue:

Settings | Performance | Use Graphics Processor: Auto

Intel UHD Graphics (30.0.101.1069)
Your system automatically supports limited acceleration

System is a GigaByte AERO 4K Pantone OLED, i9-10980HK, nVidia RTX 3080, 64GB, etc.; not exactly low-end.

Note:  Windows 11 is not an option, as it will break other very expensive professional software that is istalled.

[davew68773894]

I've decided to give up on 15.3. If the best Adobe can do is to suggest moving to Windows 11, then there's no point contacting them again.

[D Fosse]

You can use 15.3, you just need to completely disable the UHD 630. It's well known with Photoshop that dual GPUs will conflict, and now, when ACR/Ligtroom are also stepping up to extensive GPU computing, the same applies there.

Dual GPUs are intended for simple one-way downstream data flows. It works there. But this is different! You can't send data to one GPU and get it back from the other. There can only be one GPU in this equation. The GPU is part of the actual processing pipeline, it goes both ways.

[davew68773894]

Thank you so much for your advice. I'll let you know how I get on when I return home. Much appreciated.