Bug Reports

Hi, using latest Lightroom Classic on MacOS 26. I have found that sometimes LRC gets confused about the exposure. I have a two image example where the images are exposed exactly the same but the resulting pano is messed up. One half of the resulting pano is exposed correctly, the other half is light. I've only seen this in iPhone RAW HDR images. The one I kept was from Apple Camera but I've also seen it using Project Indigo camera. On the Indigo forum, another person was complaining about pano issues (black bars ending up in panos). I've also seen this issue and have example RAW images.https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-introducing-the-project-indigo-camera-app/m-p/15440106/page/21#M106426I tried attaching example files but that failed. How can I get images to the Lightroom team?   [moved from bugs to discussions according to the community rules - Mod.]

The most recent firmware update 10.08.03.67 for the DJI FC8282 Air3 broke the ability of LR / Camera Raw to recognize its camera as a supported camera, and the Adobe camera profiles are no longer available for the camera's DNGs.   The update changed EXIF:UniqueCameraModel from "DJI FC8282 Air3" to "DJI FC8282". But "DJI FC8282 Air3 Adobe Standard.dcp" is defined on the former camera-model name and doesn't recognize the new one.   You can download two sample DNGs from here: https://www.dropbox.com/scl/fi/is3vqeiyatkfe0m73or87/not_works_DJI_20240101111934_0001_D.DNG?rlkey=olocbbemz6vzg8l32yqsqosg2&dl=0 https://www.dropbox.com/scl/fi/4e3dgl8p5s66a9lk3lv4l/works_DJI_20231210105602_0005_D.DNG?rlkey=22xdldkjdmrbxb0i0ag0vo982&dl=0    When you import them into LR 13.1, observe that the Adobe camera profiles are available for the "works" DNG but not the "not_works" DNG. Here is the relevant output from Exiftool:     ======== not_works_DJI_2024010111193

DNGs from Google Pixel 6, 6a, 7a, and 7 Pro don't show the Adobe camera profiles in LR 13.2 and CR 16.2:  See this sample Pixel 6 photo:https://drive.google.com/file/d/1nTj7ZfUSYKXA9N3KIv22eTXnzDpBAFoy/view?usp=sharing and this Pixel 6 Pro photo:https://drive.google.com/drive/folders/144rrzLqVr7agPSGKxQOe4cgqsGCbf8LF and this Pixel 6a photo:https://www.dropbox.com/scl/fo/drz2yq2yk4q9sxd3pvn46/h?rlkey=gh1wa65jtyud6ll1mp5l33eg5&dl=0 and this Pixel 7a photo:https://www.dropbox.com/scl/fi/vsuob87pogxmj22rq0w1t/20240127.1729-Pixel-7a-3.DNG?rlkey=1yg1f0vo5x5zli1r7znorhems&dl=0  and these Pixel 7 Pro photos:https://drive.google.com/drive/folders/1NnOJ7WfKzgtKKLuPZVAOOJaqWJBb73cr?usp=sharing A similar bug was fixed in LR 13.2 for the Pixel 7:https://community.adobe.com/t5/camera-raw-bugs/p-imported-dng-files-from-a-google-pixel-7-phone-do-not-have-adobe-raw-profiles/idc-p/14446671

Description:When applying Noise Reduction in Lightroom Classic 14.4 to ARW files from my Sony A7C2, I encounter persistent green borders appearing along the left, right, or bottom edge of the image. This happens specifically when I enable the “Noise Reduction” checkbox in the “Detail” panel. Lightroom then automatically processes the image using AI-based noise reduction. Once the processing finishes, a slider appears to adjust the strength (default is in the middle). Regardless of whether I increase or decrease the slider, the green border always appears—only the intensity of the green varies (e.g. sometimes a very bright green, other times more subtle). This issue: Occurs only on Sony A7C2 .ARW files. Does not occur on Olympus .ORF files tested with the exact same steps. Does not exist in the original image (confirmed with ACR, Capture One, and FastRawViewer). Can be slightly reduced by disabling GPU acceleration or converting the file to DNG. Is clearly related to how Light

When I use the AI denoise feature a very distracting purple streak/band appears on the lower edge of the image (see screenshots). I expect Camera Raw to not produce a purple streak on the onage after using AI denoise. I was looking back at some files with AI denoise that I created with earlier versions of camera raw and I do not see this happening. The original file of which the screenshots have been taken after adding denoise AI is available here.   I´m using the AI denoise feature in the latest version of camera raw (17.4.1) , same happens in Lightroom Classic in the latest version (14.4). MacOs version is Sequoia 15.5 (24F74). The camera used to shoot the attached dng  is a Leica SL2.Many thanks for your quick help/action on this!

If multiple images are selected with different specific settings (say, Exposure) the Exposure field will be blank to indicate that there are differing settings across those images. However, if two images with different Denoise amounts are selected, the amount field is not blank and will display an incorrect value for at least some of the images.

As much as I love the Dehaze slider, there is one thing about it that I absolutely HATE and that is when it decides to go psycho in altering the color-balance/white-balance of photos.These example photos may not show up (I've had issues with photos disappearing from being uploaded), but here is one pair from earlier today... the tint setting on WB is just 50k apart, one click on the arrow key.. but the difference is HUGE.All settings are identical between the 2 photos, the only change was hovering the mouse over the WB tint slider and pressing the up/down key once.. changing from 5850k to 5800kI often get similar shifts going from consecutive, continuous-high photos from frame to frame with the exact same settings, no changes in wb settings, and it all seems related to the dehaze slider and the way it analyzes the photos.Years ago, I thought I actually had a defective camera, as the photos would change biggly even using the same exact settings 0.1sec apart.  Eventually, I tracked

Right now the 12 bit raw files of the Lumix S1RII are about 2 stops underexposed. I was hoping that with the latest Camera Raw update 17.3 a full support would be added, but it seems like it didn't happen. Will this support come in the near future? Attached is a comparision of Capture One and Lightrom, both adjusted to almost same exposure. C1 i had to increase by .5 while I had to bump up the exposure in Lightroon by 2.5, resulting in a higher noise. Shooting in 14 bit, Raw files are correctly exposed. but higher burst rates are only achieved by 12 bit.

In most cases, exporting AVIF and JPEG XL with corresponding settings produces files of fairly similar size. There's some variance as expected, some images compress a bit better with one format than another.   But certain raw files inexplicably compress very, very poorly with JXL. Here's a sample DNG file that exhibits the problem. https://drive.google.com/file/d/1Cs7TiY7LeA3CGUVCAzqKUl9pLSK6ek7X/view?usp=sharing   It seems common to DNGs produced by the AI denoising function or HDR merge tool, but that is not universal (I've found raws from the same camera that can be enhanced or made into HDR stacks and still compress normally on export)   The settings in the attached screenshot barely compress it at all from the original DNG! Despite said DNG containing over double the amount of pixels, and ostensibly less compression. The AVIF version with the same resolution and quality setting is over 80% smaller than either one. Again, on most images switching to AVIF at the same

Steps to reproduce: 1. load image in ACR 2. choose the crop tool (C)  3. enlarge the canvas (check "enable expand" first) 4. apply a manual transformation   Result: the stretched image is confined by the dimension of the imageExpected result: the stretched image is only restricted by the size of the canvas   Workaround: Export image with enlarged canvas and use ACR from there

I have a camera converted to super color IR by Life Pixel. The method Life Pixel recommends to create a white balance profile is to export a raw file created with the IR camera as DNG. Next, run the DNG Profile Editor, open the file, click the Color Matrices tab, move the temperature slider all the way to the left, then export the profile for use in LR and ACR. This is necessary because the DNG Profile Editor lets you select a much lower color temperature than the Temperature sliders in LR/ACR.The DNG Profile Editor has been abandoned by Adobe. It runs on Windows but does not scale on high resolution monitors. I read online that it does not run at all on Mac High Sierra or later.The new Adobe Profile SDK, which is Adobe's replacement for the DNG Profile Editor, let's us create profiles in ACR. Unfortunately that does not work for those of us with IR cameras because the Temperature slider in ACR does not have the range of the Temperature slider in DNG Profile Editor as stated above.Yes,

I am using Camera RAW v16.4 and LrC v13.4. A recent RAW photo had a particular item of purple colour but it shows as more like blue when imported to LrC - when using 'Camera Standard' profile. I Have not observed other colours to be quite so obviously different. Shown below, camera faithful, camera standard, and the out-of-camera JPG : Observe the centre image (camera standard profile) is more blue'ish than purple.   Looking at the Adobe profiles and all the camera profiles shows that only camera standard, portrait and landscape have this colour shift - I also included the Canon G9x standard (tweaked to show for the G7x), as I understand this uses the same sensor, it too resembles the JPG colour much better: Whilst I can certainly work around this, I thought I'd report the issue as I expected camera matching profiles to be close to the out-of-camera JPG, as it appears to be with the G9 profile.

When I edit a RAW file in Lightroom, which creates an XMP file, and then convert that to DNG using the DNG Converter v11.2, all the edits get carried over to the new DNG file except the color profile.  This has recently become an issue for me because I am using the new Adobe Adaptive color profile much more.   Thanks, David  

Hi, it appears like, after applying Denoise to a raw file, the TAT (with HSL) is not working as expected. I haven't been able to find a previous report on this same issue, sorry if someone did and I couldn't find it.   The following video shows the issue more clearly (normal TAT behavior, then Denoise, then the problem):   https://youtu.be/zC9rlF9am9M   I'm using ACR 17.2 and Windows. ACR is being hosted by Photoshop 26.3.

I have some 16 bit scans that I have been working on in ACR 17.2. I have done very extensive retouching of the damage to the negative using the Generative Ai removal tool because this is easily the best result. File size is about 158MB. However it is incredibly slow in a way that it isn't when I do this on my DNG camera files. Now, returning to the file it won't open again in ACR, I just get a beachball. I left one "opening" overnight and it was open the next morning but I don't know how long it took to open. The file that has the very extensive spotting wouldn't build a preview unless left overnight and now will not open.  I am bewildered as to what is going on. System is Macbook Pro M3 Max running Sequoia 15.3.1 with 36GB ram 1TB internal and accessing the files on an external NVME 4TB SSD 

Sony FE 50mm F1.2 (Camera α1)   CamerRAW17.2、Lightroom Classic14.2、Lightroom8.2 Win11   The distortion correction level when lens correction is applied is different between normal RAW and DNG with super resolution applied.I think this is a problem with the lens profile. （Reports from users）   @Rikk Flohr: Photography , please check.   https://community.adobe.com/t5/lightroom-classic-discussions/%EC%8A%88%ED%8D%BC%ED%95%B4%EC%83%81%EB%8F%84-%EC%82%AC%EC%9A%A9%EC%8B%9C-%EB%A0%8C%EC%A6%88%EA%B5%90%EC%A0%95%EC%9D%B4-%EC%A0%81%EC%9A%A9%EB%90%98%EC%A7%80-%EC%95%8A%EC%8A%B5%EB%8B%88%EB%8B%A4/m-p/15173175?profile.language=ko

Hello Adobe Team, I would like to report an issue with the Polish translation in Adobe Camera Raw 17.2. Currently, the "Light" panel is translated as "Jasny", which is incorrect. In the context of photography, "Light" should be translated as "Światło" to accurately represent the concept of illumination. This mistranslation might cause confusion for Polish-speaking users. I kindly request that this be reviewed and corrected in a future update to improve the overall user experience. Thank you for your attention to this matter. Best regards,Paweł Słowik www.slowik.eu

I was editing some events photos and started noticed a strange pattern with low light files, and with the Lens Correction feature activated. I increase the exp so you can see better the lines. ISO 6400. Check the file

Adobe Camera Raw 17.1 "New AI Features and Settings Panel" is checked.   Steps to reproduce: 1. Open a raw file in ACR. 2. Right click on the histogram and check "Show Lab Color Readouts". 3. Press "s" to sample a random color. 4. Check "Raw Details" or "Denoise" from the side panel under "Details". 5. Notice that the sampled color values shift (drastically).   I understand this is a beta feature and is still under developement. But LAB color readouts is crucial to my retouching workflow. I can't afford to let this slip through.

After the update, all panels in camera raw in Russian began to be displayed incorrectly, the columns shifted greatly. Macbook pro 2018     

First and last points in a curve setting don't scale properly when Preset Amount slider is used:   1. Before preset:   2. Applying preset:   3. Amount slider to 0%:   Windows, LR Classic 13.4.

On the latest Lightroom Classic release version 13.5 there is a new lens profile (v3) for the Canon 24-240 lens. It has reintroduced the "bad borders" bug. Workaround is simply to select the older v2 profile.

The Google Pixel 7 over-processes the camera images, making them artificially sharp and cold, which can sometimes ruin the results.So I tried using RAW files for shots that could have been good but were badly ruined by the processing. However, there was a problem with the RAW files as well: lens distortion, which is not present in the JPG files, is quite noticeable in the Camera Raw processed RAW files.At first I suspected that the Built-in Lens Profile was not being applied, but it seems that the Google Pixel does some processing on the RAW files as well, and the profile is already applied to them. RAW file processed in Capture One with zero lens distortion correction is in fact already corrected and has no distortion.   Attachments: PXL_20241017_060725238_JPG.jpg - original JPG; PXL_20241017_060725238_RAW_CameraRaw.jpg - RAW-file processed by Camera Raw, has lens distortion; PXL_20241017_060725238_RAW_CaptureOne.jpg - RAW-file processed by Capture One, no lens distortion added (

To replciate: 1) Start in full screen mode2) Apply a custom white balance to a number of images. 3) Select all images 4) Press "F" to exit full screen mode 5) Note how white balance from first image is applied to all images.   HUGE PROBLEM. Please fix!See attached video.

The most recent firmware update 10.08.05.77 for the DJI FC8284 Air3 broke the ability of LR / Camera Raw to recognize its camera as a supported camera, and the Adobe camera profiles are no longer available for the camera's DNGs.   Please note I can apply Auto lens correction where the Make, Model, and Profile are correctly applied, but unfortunately, I cannot use any Adobe Color profiles. -In my editing, I prefer to start in Adobe Color Neutral and build from there.   Example file: https://www.dropbox.com/scl/fi/el8y5li4k5u7q8muztq2h/DJI_20240628110415_0361_D.DNG?rlkey=ul8l3q9lhy9neb4xrp44t7s7a&dl=0   File EXIF data:   Device make: DJI Device model: FC8284 Software: 10.08.05.77 Lens: 70.0 mm f/2.8