Camera Raw

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.

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

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  

I see solutions for prior versions. I’m trying to uninstall the latest Camera Raw (18.2) because it is supposedly a workaround-fix to allow the prior version of Photoshop to open WEBP images like it did just few days ago. Every solution I have found suggests to click the 3 dots next to Camera Raw in the Creative Cloud desktop app, but those dots do not appear next to Camera Raw. I also could not find the file within the Adobe CC Suite in Finder. I do not have “Bridge” installed either.I went through the trouble of completely uninstalling Photoshop to try and remove Camera Raw, but no luck. Appreciate anyone who can provide factual information with clear steps.Thanks.

ACR 18.6 – Arrow-key image navigation stops after zoomingWindows 11, Photoshop 2026, Camera Raw 18.6.    Went to post this in the Camera Raw forum here and it just hung on “ looking for suggestions” so Im posting it here.  Very frustrated this morning.  ↑/↓ normally navigate between images in the Camera Raw filmstrip. After zooming into an image to inspect focus and then returning to the previous zoom level, ↑/↓ stop navigating completely. Clicking anywhere in the main image does not restore navigation. Clicking an image in the filmstrip immediately restores ↑/↓ navigation.Restarting Camera Raw, restarting Photoshop, and restarting Windows do not resolve the issue.This is reproducible consistently.  This “ bug” was new as of today. I was using it normally 3 days ago.  

I locally integrated Adobe DNG SDK into the open source SW Darktable(see https://github.com/darktable-org/darktable).It is done via the Adobe DNG SDK intergation of libraw(see https://www.libraw.org/).Before I publish I like to get an official confirmation from Adobe that this is covered by the Adobe DNG SDK license.Who and how can I ask to get this approval?

Recent Camera RAW update… when I access the Geometry panel  Shift T, the default is collapsed, I always have to click it to expand. Used to not be this way… any fix?  

Description of IssueAdobe Camera Raw repeatedly encounters a GPU out-of-memory error during normal GPU-accelerated image editing, particularly when working with masks.The error displayed is:“The graphics processor has encountered an out-of-memory error. Due to a run-time error, GPU acceleration has been reverted to Limited for the remainder of the session.”This occurs on a very high-end workstation with an NVIDIA RTX PRO 6000 Blackwell Workstation Edition with approximately 96 GB of dedicated VRAM.Importantly, the Camera Raw diagnostic log shows that GPU initialization completes successfully and that approximately 100 GB of GPU memory budget is detected. The actual failure occurs later when Camera Raw attempts to allocate/render an image mask texture.The relevant Camera Raw log entries are:Determined GPU3 hard status: success*** GL Error: E_OUTOFMEMORY (hr=0x8007000e): imageMaskTex ****** GL Error: imageMaskTex ****** Error: dng_exception (200025) in cr_gpu_tile_render_task ***TrimFoot

In order to optimize storage space I convert pictures from NEF to DNG. Unfortunately the Adobe DNG Converter is almost unusable. The software works fine on older PCs with four core processors. On my newer PC with 8 cores and 16 threads it is impossible to use. It seems like a memory problem. Sometimes it works but most of the time it renders the whole PC unusable, often crashes Windoes Explorer. Even restarts won’t solve the tangled up DNG Converter. Frustrating. 

Hello Adobe Team,In a series of identical tripod shots, a manually created mask does not synchronize correctly.When I copy the mask to a single image, it is positioned correctly. When I synchronize it to multiple images simultaneously, the mask appears shifted—even though the camera, subject, framing, and image dimensions remain unchanged. Is this a known issue?Thanks - Michael

 The updates for the versions I mentioned in the title don't work. Camera Raw keeps claiming my RTX 3070 GPU isn't supported. So, I can't use it. Only version 18.4.0.0 works.Here are screenshots of the messages I receive with the latest versions. And here with version 18.6.0.0Apart from Photoshop itself, which does support my GPU:Therefore, I cannot take advantage of the latest Camera RAW features. This is unacceptable.I already submitted a bug report for versions 18.4.1 to 18.5, but without success. You haven't fixed the problem in this version.Here are the logs for version 18.6.0.0As well as those of the version that works for comparison.I also upload my dxdiag file for analysis.I even got another NVIDIA GeForce Studio driver update today, version 616.56. But it didn't fix the Camera RAW issue. So I'm still stuck on the working version 18.4. It's really frustrating 😤 knowing that I'm paying for the software.