Bug Reports

I have updated Vietnamese for photoshop, but why is camera raw still not in Vietnamese?

When I use Denoise on RAW images, the images are putting strange squares on the DNG once it is created.  this was after the latest update on both mac and adobe lightroom.  I've spent HOURS on adobe customer service, don't know how to fix this.  I love that feature.    

To recreate bug: Part one: normal editing. Edit a photo in LR. Edit in Photoshop, using layers, adjustment layers etc.  Save / close Go back to LR.   Part two: further edits. Edit PSD photo more in lightroom using select Subject Mask / Select Background mask. 'Edit in Photoshop' Generative expand background. Save / close. Return to LR and find this:   Once this happens AI masking can't be used with the image. its consistently masks the image incorrectly, and the only way to resolve this is to delete the image and start over again.

Hey there,   I hope you can help me with this, it's driving me insane.   I noticed the problem first when shooting into a blue sky with clouds at a wedding, then I saw the problem on a table the next shoot as well. Now I checked with a white wall and found that Lightroom actually does this to my newly picked up Tamron 17-70 2.8 (on a Fuji XT-4)   I'm having crazy rings and vignetting with the Tamron lens, first thought it's the lens, but it's Lightroom adding the crazy rings. Since when I'm importing there's nothing, but when i hover over the image and select it, it takes a second and then Lightroom adds them to the picture, as if it where implementing a lens correction, but horribly wrong. Turning off Lens Profile / Correction doesn't do anything, once it's there it's there. Also the JPEG looks fine, it's only the raw file.    Attached are the two images, it's easy to tell which one is the JPEG sooc and which is the RAW file out of Lightroom with the "vig

Hint: Originally I posted at the wrong forum part (Camera Raw) and therefore my post got lost (I think). The symptoms are purple lines on the AI improved DNG files in lets say each 10th processed *.dng file. In the link at the end of this text you will find 3 files: _DSF2201.dng _DSF2201-Enhanced-NR.dng and LrC_12.4_2023-06-15.png 1. is a *.raf file which got converted to *.dng. (I do this with all my Fujifilm RAW files.) 2. is the AI enhanced / processed file with purple line at the top edge as well as the right edge. Default settings used at enhancement. 3. is my LrC system information. LrC is running on Win 10 V22H2, on two (very) different machines. Both show the same purple line artifacts. The fix made at LrC 12.4 may help for the original provided X-H1 *.raf files (from user Japhotofin) but not for my files. Can someone confirm my finding? Thank you! AI Noise reduction bug, Fujifilm X-T2 

Hello all,   The following problem with my combination "X-H2 + Lightroom Classic + Mac / iPad (software, Mac and camera on the latest SW/FW version)": actually I thought LR did not support the HEIF format, so took a few test shots, the files are recognised. Great. I think HEIF is the future-proof format (10-bit).   However, every now and then files are marked as unreadable. I currently have 15 files on the SD card (Sandisk Extreme Pro 300MBit/s). LR Classic on the MacBook Pro recognises 13 files, LR on the iPad recognises 14 files. In the Finder's preview view I can look at all 15 files.   So the problem is probably more with LR. Under these conditions, I'll probably have to switch back to JPG.   I have already formatted the memory card several times (in the camera), but the problem always occurs sporadically.   Thank you very much in advance for your tips and/or suggestions.   Many greetings Marco

Title: Inconsistency in Lens Corrections for Different File Formats   The Lens Corrections results in Lightroom Classic/ACR are inconsistent across different file formats, particularly between raw files (eg.ARW) and HDR files (-HDR.dng), where Distortion Corrections and Vignetting Corrections differ, leading to imperfect alignment during further post-processing. This issue is especially pronounced in photos taken with zoom lenses.   RAW files： - - -   HDR files： - - -   50%+50%： - - -   A typical example:In the same cityscape night scene, I took a series of [bracketed exposure photos] for creating a [High Dynamic Range background] and a series of [time-lapse photos] for maximum value synthesis of [TAIL LIGHT TRAILS]. I merged the [bracketed exposure photos] to generate a -HDR.dng, made slight adjustments, and then synchronized the photo settings with the [time-lapse photos], exporting all as TIF files for manual post-synthesis.   However, when I overlap

BUG: Amount Slider for Mask in Camera Raw Filter Smart Object doesn't update the preview on click   Version of the app:Camera Raw 16.3 and 16.3.1 / Photoshop 25.9.0 20240516.r.573 296f739 x64same issue also in Beta Adobe Photoshop Version: 25.10.0 20240606.m.2655 bf45eb0 x64 Platform and OS version: x64, Windows 10 Pro 22H2 19045.4412 Severity: high. significantly disrupts my workflow and irritates me a lot. Expected result and actual result:Actual: I have to release mouse button or move the cursor slightly to see updated preview.Expected: image should update on mouse click, even when I do not move the mouse or do not release the button. All other sliders update preview on click. Only Amount behaves differently. Basic steps to reproduce the problem:   Open any RAW file as a Smart Object Double click the Smart Object to open Camera RAW dialog Create a radial mask, set exposure to +1 Activate the text field for the amount slider (click on the number 100). Set

The Iphone 15 Pro Max main camera supposedly has a physical focal length of 6.86 mm, according to this dpreview.com article.  LR / Camera Raw provide a lens profile for the 6.86 mm lens:   But it appears that the Apple Camera app (17.4.1) is recording the lens in EXIF metadata as 6.765 mm when the app zoom is set to 1x, and thus LR doesn't find an automatically matched lens profile:   The same problem probably occurs with the Iphone 15 Pro.   Sample photo: https://www.icloud.com/iclouddrive/01eJKdmufw5yLvYtvxsJ8o5Dw#Photos   

I have gone back to images I have been workiing on in ACR prior to the Early Access generative remove and found all my heals & clones blown away. Some images have literally a hundred heals (dust bunnies, specks in snow, etc.) that are now gone.   How do I get back to the prior version? I don't like the early release!!!!!

Since I have updated to Lightroom Classic 12.4, the retouch circle automatically becomes smaller every time I use it in the same picture. For example, I put the width of the circle on 20 and use it, then I go to another spot in the picture to use the same tool and automatically LR has changed the width to 19. Then to 18, 17, 16 and so on. Anyone having the same problem? This looks like a bug? Thank you for any comments.

Dng files I import from a Pixel 7 phone do not have the Adobe Raw profiles available, they only have the profiles that JPGs have. This has started happening since the latest Google update in December 2023, and appears to occur on all Lightroom platforms, Classic, Lightroom, Lightroom Mobile for Android etc.  Previously Lightroom was able to handle DNG files from my Pixel phone  with these profiles available.  Can anyone throw any light on this? Is it a Lightroom problem or a Google issue?  Thanks for any help!

If you make or modify any mask using the Brush tool, then you leave ACR and then open it again, the brush tool's work is not retained. Other masking tools like gradients and person selection seem ok on their own, however if you try to modify ANY mask with the Brush, it disregards the mods made with the brush when saving and relaunching ACR. e.g., use the Masking brush tool to brighten a face; close ACR. Return to ACR to make other adjustments, and realize the face you masked and it's brighter settings are not there, so you have to repeat your work and immediately export it in order to keep the results. However, any return to ACR requires starting over... This was with Canon .CR3 files, but it also failed with a .NEF used for testing purposes.   I've tested on 2 mac computers with the same results. On my older mac, I tested before I updated from ACR 16.2.1 to 16.3 and the other mac was already on 16.3 when I noticed the problem. (Newer) M1 MBPro Mac's Adobe apps are current: ACR 16

Issue: Constrain Crop when checked does not actually constrain to the image boundries. Camera Raw Version: 16.3OS: MacOS, Sonoma 14.4.1Expected Result: Camera Raw Crop should contrain to the image boundries when "constrain crop" is checked if different Geometry options are selected Actual Result: Nothing Changes, Crop stays the same.   

Hi there!   I'm a Panasonic Lumix S5 user and I tend to prefer the camera matching profiles instead of the Adobe ones. I noticed however that when I use the camera matching monochrome profiles they all have a weird red hue mostly in shadow areas and the histogram confirms this. The problem is not present with Adobe Monochrome and is very subtle. I attached an example where I increased the saturation to make the red hue issue even more visible.

RF 14-35 4f & EOS R image artefacts in Adobe LR and PS   Images taken with EOS R body firmware v1.8.0 and RF 14-35 f4 recently purchased from reputable nationwide bricks and mortar shop exhibit stretched/repeated pixels along an edge in the corners.  This seems only to occur from around the 24mm mark, predominantly 26mm to 28mm and occassionally at 32mm.  Turning off lens profile correction causes artefacts to go away.  Moving Distortion slider to zero when the lens profile is enabled corrects the issue.  The issue occurs with RAW, DNG in Adobe RAW, PS and LRc but does not occur in Canon DPP, DXO DNG converter and Rawtherapee or when viewed in camera at max magnification.  The issue does not exist on an R7 body at any focal length.   All Adobe products are up to date.  This is also not LR previews as any exported file, regardless of format contains the artefacts. I saw one older post on the forums which looked to describe a similar natur

Hello, I have the Canon EOS R50 with the RF-S 18-45 lens. When I import the photo (CR3) into Lightroom and use the lens profile, I see dark corners. Vignetting is what they call it. It's gone if I zoom in a bit, by the way, but that's not so desirable, of course. After importing and applying the lens profile, I still see it. So I need to crop the photo.   It is strange that when I use the Canon software, Digital Photo Professional 4 - Version 4.18.10.0, there is no vignetting in the corners.   Can you please check the Canon lens profile because it is very annoying and not what I expected from professional software like Lightroom.Here are some sceenshots and examples. https://drive.google.com/drive/folders/1fS5voTcUIicB25Mbku6HzMkKHZRVemrp?usp=drive_linkPeace, love and beats from the Netherlands. Latest Lightroom Classic paid, WIndows 10 all updates.

Hi,   I am facing a bug when using Enhance Denoise AI in lightroom on RAW photos. Enhance is set to 50% Two purple lines appear at the short edge of the photo. See the top of the photo attached below:   Image format: CR3 Capture camera: Canon R8 Lens used: Canon RF 16mm f/2.8   Please find Lightroom version attached:     OS version attached:    Original image:         After image:   Thanks

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!