Bug Reports

Hello! Never had a need to post here so hope this is the right place.I'm the proud owner of Sony's new a7III, so I've been shooting a lot recently putting it through it's paces. Lightroom finally got support for the camera with v7.3, so I've been digging through my RAWs. Very happy except I did notice a few odd artefacts on a few shots, but nothing that caused too much concern... UNTIL NOW!!Basically, it seems that either my versions of the Camera Profiles or indeed Lightroom's overall are broken. At first I thought it could be to do with compressed vs. uncompressed RAW, but Sony's own RAW viewing software does not exhibit these issues. OBSERVE!Exhibit A:This is unprocessed in Lightroom with the Camera Standard profile applied.Exhibit B:This is the same shot using the Adobe Color profile. All the horrendous image noise/compression/whatever has gone, and the detail and smooth gradients are fine, the same as Sony's software. So, not a camera or RAW issue and this persists across all

HiToday I encountered strange behavior of the Mask panel in Adobe Camera Raw. A different mask is created if we open a file in Photoshop and Adobe Camera Raw opens automatically, and another mask is created if we invoke ACR from the Filter menu in Photoshop. Take a look at the video I recorded. I am also attaching a link to the RAW file on which this happens. https://youtu.be/0cT_zEGitu0Zipped RAW File: https://www.slowik.eu/download/lr-community/M3_00961-HDR.zip

Hello,I've been getting a red line on the bottom edge of my photos when I apply AI Denoise to them (screenshot attached of the bottom corner of one image).The photos in question come from a Canon 6D. I've used the AI Denoise feature on images from other cameras with no red line issues. It's not happening on every Canon 6D photo I've tried it on, but it's happened on a few different photos and always along the bottom edge of the image.   This is my system info from the Help menu:   Lightroom Classic version: 13.1 [ 202312111226-41a494e8 ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 14Version: 14.2.1 [23C71]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Built-in memory: 24,576.0 MBReal memory available to Lightroom: 24,576.0 MBReal memory used by Lightroom: 4,070.1 MB (16.5%)Virtual memory used by Lightroom: 422,276.7 MBMemory cache size: 384.3MBInternal Camera Raw version: 16.1 [ 1728 ]Maximum thread

Dear Adobe Support   Use Case & Setup I own a Nikon Z 7 II with a kit lens, the Nikkor Z f/4 24-70mm, which I use a lot when travelling. Typically, I would shoot a lot of images at 70mm and build panoramas, which is why I need vignetting to be eliminated completely, as the bright, respectively dark vignetting on the original pictures can otherwise be seen in the final resulting panorama.   The problem It seems like there is no way currently to automatically correct the lens profile to remove vignetting using the NIKKOR Z f/4 24-70mm kit lens.   The process I typically import my images in .NEF and first convert the to .dng (with lossy compression). I assume this step has no impact but I'm mentioning it here for completeness. I have seen similar posts on this forum but they don't seem to answer exactly this question. More on this later. Here is what I see, to give you an example: After importing and without profile corrections enabled, you can clearly see vignetting j

Issue: Lightroom claims a DNG file is damaged yet it can be processed in other applications. Provide Lightroom Classic version: 11.3 Release Camera Raw 14.3Build [202204051513-7a25c809]Provide OS and version:macOS MontereyVersion 12.3.1iMac (Retina 5K, 27-inch, 2019)Processor 3.6 GHz 8-Core Intel Core i9Memory 64 GB 2667 MHz DDR4Startup Disk Macintosh HDGraphics Radeon Pro 575X 4 GB Issue:When attempting to edit a handful of DNG images in my library Lightroom claims:"The file appears to be unsupported or damaged."That message appears in a popover on an imbedded preview.Of interest: Mac finder can process the image. Mac Preview.app can process the image. Affinity Photo can process the image. Exiftool can read the image metadata   My workaround is to convert the image to another format using Finder or Preview or Affinity Photo.Also of interest: Every damaged DNG was created by a Leica  camera and subsequently modified by an older version of Lightroom Classic, specif

When opening a Canon's CR2 file it opens camera RAW and I don't have any ways to close the windows. Full Screen Screenshot attached.

The most recent version of ACR broke this function again. Zooming while using Option + Scroll Wheel doesn't work when using the Adjustment Brush (k). It works okay with other tools (Spot Removal (b)  gradient (g) and (j) tools). But when the adjustment brush (k) is active, the scroll wheel adjusts the brush size *regardless* of whether the Option key is pressed or not.This issue was addressed about a year ago, but one of the recent updates broke it again. Please let me know what else you need to know to get this bug fixed again. Thanks in advance!

Hi,I've spotted latest Camera Raw breaking the values when I convert and tonemap my HDRIs with Camera Raw from 32bit to 16bit.Once you touch Highlights or Shadows slider, it makes black values go crazy. They actually do not work at all. In the other hand Curve panel works fine: I used to use Camera Raw to tone map my HDRIs for the past 5 years...  

Schon in der Version 16 gab es keine Möglichkeit, ein Bild in Photoshop aus dem Camera Raw zu öffnen, da es dafür einfach keine Buttons gibt.  Egal, wie ich das Bild unten erweitere, sehe ich die nicht. Sind die nun einfach woanders? 😄 Help. Kann das Bild weder in PS öffnen, noch schließen und muss Photoshop per Taskmanager zumachen.      

With macOS Sonoma 14.1, Photoshop 2014 (ps ver 25.1) and Camera Raw 16.0 in Full Screen Mode, the bottom part of the Panel space as marked below doesn't allow clicks or moving of the sliders in the Edit, Profile and Presets panels or any panel that the controls extend down into that area.  

Hello, I would like to let you know that currently the lens profile of the Sigma 14-24 dg dn in Lightroom leads to a visible overcorrection of vignetting, especially at 14 or 15mm.This happens when you just enable the automatic lens correction, with distortion and vignetting values set to standard values of 100.I have attached an image taken at 14mm, the automatic lens correction in Lightroom being enabled.One can clearly observe a white area including a thin white curve in the left and right corner of the image which is kind of disturbing.Currently I am able to adjust this by significantly reducing the vignetting value to approximately 30-50, but it is only a workaround and it also depends what value for the distortion is set.It would be very helpful if you could have a look at this and modify the lens correction profile of the Sigma 14-24 for Sony. Thanks.

White patches been occurring on RAW photos shot with the Google pixel 6a ever since the last camera update of Android 14. What I have seen is that this occurs only in "google pixel" profile and doesn't occur in Adobe color profile. RAW photos are totally unusable now unless you switch to Adobe color profile. There is no problem with the jpegs or while shooting with apps like Instagram.   I have attached an screenshot of what the problem is. First image is the RAW file with google pixel profile and second is the pre processed jpeg straight out of camera      

Using ACR 15.4 with Windows 11: As soon as I enter a number into "angle" the crop selection changes to outside the picture. This error does not happen when the angle is changed in a different way (e.g. double click on level tool).

I have been using Expert Raw on my new S23 Ultra and transfered several raw pictures to Lightroom(mobile) and edited them there. But for some reason it wont accept astrophotography photos. They are also in raw file and not even that big of a file. A few was taken with the main 1x camera and a few in 3x camera. But when i try to import them to lightroom i get the message "Failed to import 1 photo"   I asked in other forums for Samsung phones but doesn't seem other people have the same problem.   Any ideas?

Hello   I'm a long time LR classic user but a recent Leica M shooter. Until now, I was used to correcting my lenses (mainly Sony) through the lens correction tab, adjusting the Adobe provided lense profile, and especially the vignetting slider.   To my surprise, when LR detects a Leica M lens in the  EXIF data (in my case a 35/2, a 18/3.8, or a 90/2.8) it loads the correct Adobe lens profile (yeah) but the vignetting slider becomes greyed out, the vignetting is not corrected, and I cannot adjust it. I need to switch to a manual lens profile - and loose all the pre-configured corrections - if I want to adjust vignetting (which is quite significant on the 35 and 18).   Does anybody know: - If LR is working as expected in this case? - Why does not Adobe proposes vignetting correction for Leica M lenses? - If there is a workaround for this behaviour?   Thank you in advance for your wisdom.

Issue: Lens correction not correctly applied to super resolution raw Camera Raw Version Number: Camera Raw v14.1 OS Version Number: Windows 10 21H2 Steps to reproduce: Use a raw image like this one https://www.dpreview.com/sample-galleries/1514562719/sony-fe-16-35mm-f2-8-gm-sample-gallery/2104950891 Apply Super Resolution to the raw image in Camera Raw to obtain a super resolution DNG. Enable lens correction from "Optics" -> "use profile corrections". Expected result: When zoomed out, the two image should appear identical.Actual result: The two images are not identical when zoomed out. The same lens correction profile appears to have different effect on the two images. The differences are not huge, but when quickly going between the two images, it can easily shows the amount of geometric distortion correction applied is different.   I found this issue appears on Sony 16-35/2.8 GM and 28/2 lens, but does not seem to appear on Tamron 28-200 lens.. I haven't tes

  Version of the app: Camera Raw 15.4 Platform and OS version: Windows 10 Pro Basic steps to reproduce the problem: Run AI Denoise at 50% on a Sony ILCE-7R raw file Expected result and actual result: Clean image / purple lines on right sides of the image

Using the new AI Denoise feature seems to darken my images and strip almost all the color out of them. Files are from a Nikon D500 being processed by a Ryzen 5 3600, 32GB RAM, and Intel A750 video card on Windows 11. Tried to create virtual copy of file and reset all other adjustments and it makes no difference. Still dark and almost completely black and white.

Hey all,   I just updated to the new 12.3 version of LRC and tested it out with a couple of files from my Fuji X-H1 for both images the resulting DNG-file has purple lines going across the top and right sides of the image.   Version of the app: LRC 12.3 Platform and OS version: Windows 10 Pro Basic steps to reproduce the problem: Run AI Denoise at 50% on a Fuji X-H1 file Expected result and actual result: Clean image / purple lines on top and right sides of the image   I'll attach a few screen captures to showcase the issue.

Hi. When I run ACR 15.3 from Bridge it shows me following message: "Graphics processor acceleration is currently disabled. Please be aware that Camera Raw will soon require GPU support to edit photos. You can manage GPU settings in the Performance section of the Preferences dialog." This is not an issue because my GPU is indeed below system requirements - it's fine for me. I just click ok, message closes and I can work - can close ACR and open once again without this message, can even restart Bridge and open ACR without this message. But the next day first time I open ACR I get the exact same message once again. And this happens every day first time I open ACR. My GPU is unsupported, you showed me the warning - ok, I get it. But what's the point in showing it every day? This is super annoying to say the least. Can this be be disabled?

The LocalAdjustment Color Range Mask appears to be calculated using the image data before Chromatic Aberration (CA) and Defringe are applied. This causes the Color Range Mask adjustments to be applied to image edges that have chromatic aberration. It creates a visible edge outline of size and color dependent on the type and severity of the lens chromatic aberrations. I tested this using a Canon EF 16-35mm F/4L IS lens that has very low CA and the Canon EF-S 18-35mmF/3.5-5.6 IS II, which has much higher CA. To confirm this analysis I created Export TIFF copies of the raw image file with Lens Corrections> Profile> ‘Remove Chromatic Aberration’ unchecked and checked. The TIFF with ‘Remove Chromatic Aberration’ unchecked appears identical to the raw file and exhibits the same edge artifacts. The TIFF with‘Remove Chromatic Aberration’ checked displays almost NO artifacts. EDIT: The Adjustment Brush ‘Auto Mask’ control exhibits the same behavior as the ‘ColorRange Mask’ control when 'R

Use DNG 15.2 to convert Panasonic Lumix DC-S3M2 to DNG with Lossy Compression enabled. Attempt to import into CR 15.2 or LrC 12.2File is not readableBug in LRC 12.2 und Camera Raw 15.2 bei der DNG-Konvertierung von Lumix DC-S5M2 Raw Dateien (*.RW2). Nach Konvertierung der RAW Dateien in das DNG-Format zeigt LRC einen Fehler an und die Dateien lassen sich nicht weiterverarbeiten. Auch PS und Bridge sind betroffen.

Hello! Mac Studio M1 Max after upgrading to Ventura 13.0.1 noticed such a thing. Photoshop 24 starts normally, but when you try to open any file (no matter raw or jpeg), it crashes. Presumably this is due to Camera Raw 15, since downgrading to 13 can open files without crashing. Also Lightroom 12.1 does not even start, it immediately crashes. Someone faced a similar problem? At the same time, on a MacBook Air M1 on Ventura 13.0.1, Photoshop and Lightroom work fine. Maybe the problem is in the camera is equal to 15 and Apple M1 Max? And when you manage to open a file with version 13 of the camera raw and try to make enhanced detailing, an inscription appears that my video card (and this is on a mac studio) is not compatible with the metal chip. Maybe there are owners of mac studio who can help me? 

Hi. I've just tested the AVIF HDR output on ACR 15.1 on Apple Silicon Macbook Pro. It seems broken when GPU acceleration is enabled. The exported images are distorted. When GPU acceleration is disabled in ACR, the HDR content cannot be displayed, but when exported it's correct - it is correctly display by supported browser (Chrome 108+)   Br, Pawel

Hi All,   First time posting, this issue has been annoying me since I picked up this new camera. Sony A7IV with sigma 24-70 2.8 DG DN A019 is under correcting vignette on wide 24mm end and over correcting on 70mm end. Almost like the vignette correction profile is backwards. See attached shots at 24, 35, 50 and 70. Lightroom is latest 12.0.1 release, camera is latest 1.11 firmware and lens is v.03 (tried updating to v.04 but sigma software wasn't cooperating, sigma says this update just allows MF assist).  What I have tried:   Turning all compensations on in camera Turning all except shading compensation on in camera (suggested on other posts) Turning all off in camera and selecting in lightroom once imported   All give the same result. I have also tried switching correction profile versions which sometimes yields a better result at a certain focal length but it's hit and miss.    Any one else having this issue or know of something I might be missing? &n