Camera Raw

J'ai un problème. Toutes les versions depuis Camera RAW 18.4.1 à la dernière échoue de fonctionner sur ma machine. J'ai une RTX 3070 Ventus, Je suis sur Windows 10 22h2 entièrement à jour. J'ai 32 Go de Ram. J'ai la dernière mise à jour du driver NVIDIA. C'est à dire la 610.88. Mais à partir de la 18.4.1 de Camera RAW, il ne reconnait plus mon GPU. Impossible de l'ouvrir dans Photoshop. Un message indiquant que "Camera Raw nécessite l'accélération du processeur graphique pour retoucher les photos". Donc pour lui, c'est comme ci je n'avais pas de GPU. Dans les paramètres de Photoshop pour aller dans les propriétés de Camera Raw, au niveau performance, je vois ce message "L'accélération graphique Camera Raw n'est pas prise en charge par votre système". J'ai déjà cliqué sur "Réinitialiser la prise en charge GPU", "Purger la mémoire cache". Redémarrer Photoshop. Mais sans résultat positif. Pourtant Photoshop lui-même détecte bien mon GPU et il est bien utilisé. Pour le moment, je suis obli

I’m trying to remove the reflection from the shop window (see attached screenshot), but the related tool in Camera Raw seems not work. Any suggestion?Many thanks for helpRoberto

Hi,Please can Adobe add the DJI Mini 5 Pro Profiles in Camera Raw, so that I can use Adobe Standard. Adobe Landscape, Adobe Vivid profiles when I import the DJI Mini 5 Pro .DNG files Thanks in advance, NickDJI Mini 5 ProLightroom release: 15.6Camera Raw release: 18.7

Avec les courbes choisir d’agir sur la luminosité uniquement et pas sur RVB comme chez tous vos concurrents.

Adobe Camera Raw 18.5This problem occurs on both Nikon D850 and D500 raw files which have been opened in ACR by right clicking on the files in the Mac finder and selecting open in photoshop.  The files have not been previously processed in any way.When I right click on the image in Camera Raw, the option for “Show Autofocus Points” is greyed out and not responsive.  I have repeated this with multiple files from both cameras taken using different autofocus modes.I have checked two of the files (one D500, and one D850) in Raw Digger to examine the EXIF data, and both show values for “Focus Position” (0x11 on a D500 file) and “AF Points in Focus” (E9 on the same file), so this metadata information should be available to Camera Raw.Are these cameras supposed to be supported by this feature?  Adobe’s documentation says nothing about what cameras are supported.I watched a video today showing someone using this feature (although with a different camera’s files), so I know that I was looking a

After upgrading to 15.4, several, but not all, of my hdr pano photos report the above error, along with “The file appears to be unsupported or damaged”. Restored these “damaged” photos from versioned backup on Backblaze from versions several months old and still received the error. Reverted to 15.3.1 and these files no-longer show the error. So, 15.4-->Broken; 15.3.1-->Working

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.]

Using an R6III with en EF 11-24 F4L via an EF to RF adapter, and I am noticing significant barrel distortion at the wide end that the profile in Adobe Camera Raw isn’t taking out.The strange thing is that I used the exact same lens and adapter on my R6 mark 1, using the same lens profile in ACR and it corrects the distortion well.Anyone have any insights?I can correct manually but it gets tedious (shooting real estate)

Issue: Camera Raw 18.6 on Windows gets stuck in the Zoom tool. When I select Masking and create a new Brush mask, the Brush cursor does not become active over the image. The Zoom tool remains active and prevents me from painting the mask.Camera Raw version: 18.6Operating system: WindowsGPU: NVIDIA GeForce GTX 1650, 4 GBSteps to reproduce:1. Open an image in Camera Raw 18.6.2. Select Masking.3. Create a new Brush mask.4. Move the cursor over the image.Expected result:The Brush cursor should appear over the image and allow me to paint the mask.Actual result:The Zoom tool remains active and appears to "capture" the cursor. The Brush cursor sometimes appears intermittently while moving the mouse, but disappears as soon as the cursor reaches the image. I cannot paint or create the mask normally.Troubleshooting already performed:- Restarted Photoshop.- Reset GPU compatibility.- Tested the GPU settings in both Automatic and Custom modes.- GPU is detected as NVIDIA GeForce GTX 1650 (4 GB).- Ca

I can’t help noticing that some Canon models render colors much warmer, more lively and “deep” in ACR/Lightroom despite using the same camera matching profile as my EOS R8 - for example “Camera Standard”If I compare it to EOS R50, R100 or even some older model such as EOS 70D or 6D the colors, tone and contrast is dramatically different. The R8 seems more “anemic” in comparison.My question is (and I guess only Adobe will be able to tell): I wonder if Adobe uses other color tables for entry models to “please” the target? 

After updated my Mac OS versions of Photoshop and ACR this past week I have encountered a problem when attempting to open edited ACR files in Photoshop using the “Open Object” button. (Same issue if I choose “Open” instead of “Open Object” in ACR.The problem only affects files that have been edited in ACR. An unedited file will open correctly in Photoshop.When I click the button, ACR simply closes and takes me back to Bridge. My ACR edits are not lost, but I still cannot open the file. Double-clicking the image in Bridge re-opens in in ACR with the previous ACR edits intact, but clicking the Open Object button still will not open in into Photoshop.If I instead go back to Bridge, click to select the image in the slideshow, it opens a camera raw edit window like the one that I had seen in ACR, though with a different layout form my default ACR layout. If I click DONE or Open Object, the window simply closes and I’m in Photoshop by my file has not opened. Photoshop version is 27.10.0Bridg

Hoping for some type of solution. I have an R5 MK2. I shoot raw and convert to tiff with pro photo rbg 16 bit, then further edit the tif. What I see in ACR during the edit and the later saved result in Bridge are not the same. I like what I see in ACR and not so much the saved result in Bridge. Any light shed on this would be much appreciated.

I did a new install of photoshop and lightroom classic on a new Mac.Lightroom classic release 15.5.1 with camera raw 18.5.1The new photoshop version is 27.10.0The camera raw version is 18.6The mismatch in camera raw is causing issues with the round trip from lightroom to photoshop. How do I either update the camera raw version in Lightroom classic or roll back camera raw, and if I do does that screw up photoshop?system infoAdobe Photoshop Version: 27.10.0 20260824.r.26 9d9635d  arm64 (final, Release) Number of Launches: 4 Operating System: Mac OS 27.0.0 System architecture: Apple M5 Max, NEON, DOTPROD, HybridCPU(6:12) Physical processor count: 18 Built-in memory: 65536 MB Free memory: 39805 MB Memory available to Photoshop: 60716 MB Memory used by Photoshop: 70 % Crash Handler: Adobe DCX Version: 9.22.0 SAM SDK Version: 15.1.5 ACPL.next Status:  - SDK Version: 5.11.6  - Sync Engine Status: Reachable and compatible  - Sync Engine Running: 4.0.0  - Min Sync Engine Required: 4.0.0 Live Ed

I am the poster this threands. That is not the question!!! That is totally bug!! But the manager classify my threads as Question!SOOC of Lumix S9 with Vlog color profileRW2 of Lumix S9 was opened in ACR 18.6It can be clearly observed that the consistency of color is severely inaccurate!This condition is identical with Lumix S1M2SOOC of Lumix S1M2 with Vlog color profileRW2 of Lumix S1M2 was opened in ACR 18.6It can be clearly observed that the consistency of color is severely inaccurate and red is supersaturation.Besides the bug I reported above, there is another thing that Adobe needs to improve. I hope Adobe can introduce a layered and graded color grading workflow, similar to the color grading interface in DaVinci Resolve. Because in either ACR or LR, once a color profile is applied, you cannot apply another color profile on top of it. This also means that Panasonic RAW files in ACR cannot have V-Log applied and then have LUTs applied afterward.

any help would be good i am wasting so much time 

When using ACR image menu and selecting Export Settings to XMP then closing image with Done button DNG preview is not being updated. ACR only updates preview if any change happens, after Export Settings to XMP being used.Sometimes i do a lot of Export Settings to XMP as precaution because ACR crash frequently and i might loose all the progress i made and if i don’t remember to use Export Settings to XMP then preview never updates. Please fix to update preview after Export Settings to XMP being used.

Please Bring Back the “Constrain Crop” Option in Adobe Camera RawPlease bring back the “Constrain Crop” option that was available in previous versions of Adobe Camera Raw.This feature automatically adjusted the crop boundary when an image was rotated, preventing empty or transparent areas from appearing around the edges. It was extremely useful for photographers who need to straighten and crop large numbers of images quickly.In the latest version, this option is no longer available, which makes the cropping workflow much slower and less convenient. Users now have to manually adjust the crop after every rotation, even though the previous feature handled this automatically with a single checkbox.Removing this option feels like a significant step backward, especially for professional photographers who process hundreds or thousands of images at a time. Please restore the original “Constrain Crop” checkbox, or provide an equivalent option that users can enable or disable depending on their

Adobe Lens Profiles are written in XML format, allowing anyone to create or modify them. Since values ​​such as vignetting correction vary significantly depending on the aperture setting (f-number), it is common practice to include correction values ​​for multiple f-numbers. The "stCamera:ApertureValue" parameter is used to identify these settings; for a given f-number *N*, the value is calculated as 2×log2(*N*). However, an error occurs if *N* is 1 or less—meaning the "stCamera:ApertureValue" is 0 or less. While setting the value to a tiny figure like 0.001 avoids the error, the profile will not be applied to photos taken at f/1.0.Consequently, for ultra-fast lenses with apertures like f/1.0, f/0.95, or f/0.8, the system cannot automatically apply the appropriate profile to shots taken at f/1.0 or wider. The current workaround is to manually apply separate profiles for each specific f-number—effectively bypassing the use of "stCamera:ApertureValue" altogether.I would like to see a fun

 After batch cropping in raw to a specific shape (3000x2216), when converting and saving I specify a long edge of 3000 pixels, but resulting images are 3000x2203. This only started happening in the new version of Raw (18.6). In the past this workflow always resulted in image exports with a 3000x2216 resolution.Crop for all images set to 3000x2216export shape does not match crop shape