Camera Raw

The lens profile for the Tamron 35-150 f2-2.8 for Sony is not compatible with the Tamron 35-150 f2-2.8 for Nikon Z due to incompatible distortion.

This post applies to Camera Raw. Lightroom Classic and Lightroom Ecosystem feedback can be found here. Previous Early Access Feedback can be found here.   Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size.    Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now.    We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed.    Batch updating is also now supported for Generative Remove spots. As Generative AI analyzes portions of the image that have been cropped out, Camera Raw has the ability to tog

This post applies to Adobe Camera Raw plug-in.     Adobe Camera Raw team is sharing an early look of our new Reflection Removal feature, which removes reflections caused by plate glass surfaces from photos.    Note:  The feature currently only works on raw photos. Support for JPEGs & HEICs is added in the April 24 Update. There is a known issue on some Windows machines where the feature may produce a corrupt image. We are working on a fix for the upcoming release.    Check out HelpX for more detailed usage information. For more technical information on the underlying technology, please refer to this Blog post.    Getting started with the Reflection Removal feature:  Make sure you have the “New AI Features and Settings Panel” Technology Preview enabled in the Camera Raw plug-in Preferences dialog (requires restarting the host application to activate).  Go to the Remove panel [B] , and in the “Distraction Re

I have never had an issue with ACR before.18.3 freezing saying not responding saving files took twenty minutes instead of seconds everything was super laging, when I disabled the GPU acceleration it improved I see on the other pages I am not alone I'm using the most up to date windows, Nvidia drivers ETC: I have a 7950x, 5090, 64GB and NVME drives. Please fix as soon as possible or at least give a link to the previous version which I had no issues with.Solution:Update following the instructions in this link:  

Announcing a new feature now in Adobe Camera Raw (17.2) – Removal of Distracting PeopleUnder the Remove dialog, under Distraction Removal, we have added an item called “People”.   This feature supports faster and easier detection and removal of distracting people in an image. It is offered as a Tech Preview in the Adobe Camera Raw Plugin-only and is available now. Please try it out and let us know what works well, what doesn’t work well, and anything that might improve the experience.   Thank you! Peter Baust - Dir, Product Management   Posted by Rikk Flohr  

Hasselblad’s FFF. formats are not supported anymoreProblem occurs in both Mac OS 15.5 (24F74)  & Windows 11 pro (Betriebssystembuild: 26100.7840)When opening fff. files in the newest Bridge (16.0.3), Camera RAW Plugin (18.3.) opens and creates an error, claiming the file format is not supported. Same Problem occurs with  the newest Lightroom Classic (15.3). The Import is not possible cause the file format is not supported.Thank you for your help!

how solve my issue

There is a persistent bug when synchronizing "Spot Removal" (Heal/Clone) adjustments across images that involve HDR merges in vertical orientation. The adjustment coordinates are not being mapped correctly between standard RAW/DNG files and the DNG files generated by Lightroom's HDR Merge feature.Steps to reproduce: Take a series of vertical (portrait orientation) RAW images. Perform an HDR Merge to create a new DNG file. Apply a spot removal adjustment (e.g., to clean sensor dust) on one of the nont merged files. Sync that adjustment to the newly created HDR DNG file. Expected result: The spot removal should be applied to the exact same visual coordinates in both the source and the target HDR image.Actual result: In vertical images, the spot removal adjustment is shifted to an incorrect position on the HDR file. This does not happen with horizontal (landscape) images.Additional notes: The issue occurs regardless of the camera brand/model. The offset happens both ways: from RAW

At the moment I don’t shoot in raw and do not want Photoshop to open in Camera Raw. I have tried the various suggestions and rebooted both photoshop and my Mac laptop but it still opens my jpeg files in Camera Raw. Any suggestions on how I can top Photoshop opening in Camera Raw would be greatly appreciated. Thank you.

Hello everyone, I recognized a strange behaviour in Camera RAW. I opened Photoshop, then opened about 20 RAW files waiting for Camera RAW to load. So it does. I start working in CR, but after a few minutes CR is getting very laggy, my mouse pointer is sometimes freezing, and every change, for example exposure or any other parameter, leads into a delayed output for about 5 or 6 seconds. A smooth working is not possible anymore. So I made some tests. It doesn't matter if I open just one oder 50 RAW files, always the same. I figured out that this behaviour first occures when I use AI masking for automatically choosing the background or the main object in my picture. As soon as I choose a mask with AI feature, I see that my RAM is slowly filling up until it is completely used. From this point, the described delays happen. I have Windows 10, 32 GB RAM (should be enough, at least for one RAW file?), Ryzen 7600X and Geforce 4070S. I don't know when this started, becau

Please can someone explain the changes to the crop tool in Camera Raw (18.3)?When using the gemoetry options I cannot crop to the edge of the image no matter what I do - this was no problem before. When the crop area is maximised, the crop tool no longer drags the cropped area, it only draws a new area to crop.This is incredibly frustrating. Please can someone tell me how to get the legacy crop tool back? This wasn’t included in any “What’s New” content I have seen.

This post is to collect in-app customer feedback from Camera Raw for the Technology Preview of the Generative Expand feature.    Generative Expand seamlessly blends the edges of your existing image with newly generated content that naturally fits into the background without taking away from your photo’s original subject. Some use cases for Generative Expand are: Expand the canvas for images that were accidentally cropped  Fill in the edges of a panorama  Adjust the aspect ratio of a photo for social media    This feature is currently a Technology Preview, and we are still working to ensure it meets your needs. We'd love to hear what it does well, what it doesn't do well, and how you'd like it to work.    Please also include the following details in your post:  Camera raw version System details Example image(s) if you wish to share   Our team continually monitors this thread. Thanks! Thanks!Peter Baust - Dir, Product

In building a python library to write and render DNG files (https://github.com/mu-files/mu-image/tree/main/muimg) we noticed that 10bit raw data is handled inconsistently between uncompressed DNG and JXL DNG.In the DNG SDK: - For uncompressed data - 10bit data is packed in the tiff ifd, then gets unpacked in the decoder and goes through the DNG renderer as values in the lower 10 lower bits of a 16 bit buffer.- For the JXL path, our initial attempt was to tell the JXL encoder to store 10 bit data. The inconsistency we ran into is that the DNG SDK code requests this bitstream as JXL_BIT_DEPTH_FROM_PIXEL_FORMAT - which tells the JXL decoder to shift the 10bit data up to the full 16 bit depth of the buffer being used.So from the DNG encoder side we cannot treat 10 bit data the same if it is being encoded as uncompressed or as JXL. If the DNG SDK code requested the data from jxl decoder using JXL_BIT_DEPTH_FROM_CODESTREAM then the decoder would return the 10bit data that the encoder intende

Die KI-basierte Entrauschungsfunktion in Lightroom Classic hat mit HDR-Bildern, die in Lightroom generiert wurden (dng-Format) erhebliche Probleme in Zusammenhang mit Fenstern. Es entstehen im Bereich von Fenstern regelmäßig sehr unschöne Karo-Muster. Anhängend jeweils JPG-Output mit aktivierter und deaktivierter Entrauschungsfunktion.Die DNG-Dateien sind abrufbar unter: LR-Denoise-Bug The AI-based denoising feature in Lightroom Classic has significant issues with HDR images generated in Lightroom (DNG format) related to windows. Regularly, unattractive checkerboard patterns occur in the window areas. Attached are JPG outputs with the denoising feature both enabled and disabled.The DNG files can be accessed here: LR-Denoise-Bug 

using bridge to adobe camera raw and edit going to photoshop using open as object does not carry the file location with it as it does with just open. If this would be correct it would appreciate it as I use this feature. It would be helpful as well having the selection to open and open as object to until changed in other edits.

I've been looking to test out the new dust removal feature in Camera Raw and couldn't find it. Turns out, the entire "Distraction Removal" section is missing from my Camera Raw app. I've gone into settings and enabled "New AI features" as directed in many instructional guides. Restarted Photoshop, and it's still not present. I even tried downloading the latest Photoshop beta (26.11), and I don't have this section at all. What am I doing wrong? I've screenshot the relevant sections for visual aid. Versions:Photoshop 26.9Windows 11 24H2Snapdragon X Elite PC

1. Description of the Issue After opening a photo and attempting to use the "Select People" mask, the error message "Unable to select people in the photo" appears, and the feature fails to function.2. Camera Raw Version(s) 18.3, 17.5 3. OS Version macOS Tahoe 26.3.1 4. Steps Taken & Troubleshooting Performed (Reproducible) The following steps were taken, but the issue persists: Changed Performance settings in Camera Raw Preferences. Reset Camera Raw Preferences. Reset Host application settings. Reset UXP and CEP folders. Deleted System Fonts. Granted Full Disk Access to Adobe applications in macOS settings. Performed a clean reinstallation of all Adobe apps and downgraded Photoshop to 26.11.4. Downgraded Camera Raw to 17.5. Switched Image Processing settings between "Cloud" and "More Stable". Tested on a New User Account (macOS). Note: The user confirmed this issue began immediately after updating to the latest macOS version. 5. Expected Result The AI should det