Bug Reports

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

ISSUE:  Lightroom V 5.3 and LRC V 11.3.1. with CR 14.2 (all for Mac OSX) and LR for IOS V 7.3.2 all have a bug that menas that lens corrections do not work for  the lenses listed as Supported if the camer used is the Leica M11.   Step 1: open any DNG file shot using the Leica M11.  Step 2: go to Lens Corrections Step 3: enable lens corrections (process differs depending on version and platform but result is the same across all   Expected result: Lens corrections for that particular lens should be applied if that lens is listed as Supported   Actual Result: Lens corrections are not applied.   Additional information 1: This has been confirmed by many experienced users.   Additional information 2: If I use the DNG Cleaner app to alter the DNG file so that the EXOF shows the camera as Leica M10-R or Leica M9 and then follow the exact process above, the lens corrections are applied.   Additional Information 3: two examples of lenses that are list

Prior to this ACR release, the curve mode selected was always the last mode used.  With this update, it always starts in Parametric Curve mode.  Even when opening a previously edited file with changes only in the Point Curve, ACR starts in Parametric mode.   Why?  This is new behavior.  Having to select the point curve button every time I edit a file is a waste of time, and I believe is a bug.   ACR 15.0.0.1264

The profile for the Canon RF16mm 2.8 STM was created with an error. The very edges of the frames are bent. At the same time, JPG from the camera and conversion through DPP completely corrects these distortions. This lens has mustache distortion. I am an architectural and interior photographer and I see it right away. Please make corrections!

In the last version ACR V15.0 is no longer possible to enable Lab color readouts right clicking (windows) in the Histogram. How can I get color samples in LAB remaining in my default color space?  

ACR version 15.0.0.1264  Windows 10 when selecting a person the different body parts can be used as mask (new feature).  The last one proposed in the list is the person's hair. This has been translated in French as fibre. IMHO cheveux or chevelure would be a better translation.

1) Open a file in Camera Raw hosted by Bridge 2) Create a mask using the new "People" feature, or use the new Content Aware tool (I guess other new features will trigger the same error, but these two are the ones I've tested) 3) Click open   When Photoshop opens, this errors message appears (and the file doesn't open):     "Could not open "(file name) because the file-format module cannot parse the file"   I'm using Windows 10 and the lastest Bridge/ACR/PS versions at the time of writing, but more people have reported this to me on my blog/YT channel.

As the title says.  The hotkey is the y-key and works with the mask functions but not with the visualize spots while the tool tip still says it's the y-key. Does anyone else notice this?   Cheers, Ben.

Win 10 - LrC 11.4This issue was raised at the lightroomqueen.com forum, see this thread: https://www.lightroomqueen.com/community/threads/lr-ver-11-4-bug.45631/   I have tested this myself on several different pano sets, and often (though not always) I can reproduce the reported issue. Using one particular set of 5 images, the problem is immediately apparent when using the Cylindrical projection - the preview is fine, but as soon as the boundary warp slider is brought into use one can see the preview is vertically cropped from the top, as per these screenshots:   First at 40%     Then at 60%:     Then at 80%:     And so on. Completing the merge in that preview state produces the same cropped file.   The problem does not initially appear to occur when using the Spherical projection, as the preview correctly updates when applying the boundary warp slider, however when completing the merge the result is still the same vertically cropped

My previews and thumbnails of DNG files have a pink cast but the original CR2 files don't. All DNG files read fine when opened in Adobe software (Lightroom, Raw & Photoshop)   I've been keeping the CR2 until I understand what's going on but it takes up a lot of extra storage space and some I already deleted before realizing the issue.   I'm shooting with CANON 5D IV & II (2 different cameras) and the files are coming from various SanDisk cards. This has never happened and only started in April 2018. Images I shot in March didn't have this issues. YET there were some images in March I didn't upload until April and they are pink. It seems to be something that has happened during the conversion from CR2 to DNG.   I use Lightroom CC with Raw 9.12

Using Canon R7, CR3 RAW files: I have discovered vertical bands when I shot in low light using higher ISO (ISO 1600 and up), when I process using the latest Camera RAW Using Windows 11. When I process using Canons latest DPP software the bands are not there.  This is with standard settings, no exposure change or other changes except standard sharpening.