Camera Raw

Camera Raw 18.6 – Local Mask Sharpening/NR values become incorrectly shared between saved ISO presetsI believe I have found a reproducible bug in Adobe Camera Raw when used directly through Photoshop.Environment Photoshop 27.10 Adobe Camera Raw 18.6 Testing performed directly through Photoshop → Camera Raw, not through Bridge or Lightroom. Important troubleshooting already performedI purged the Camera Raw cache and deleted relevant .xmp files between tests as necessary, so I was starting each test from as clean a state as practical. The problem remained reproducible.Reproduction Create an ISO 1600 LNR+MASK preset with: Local Background Mask Sharpening = −10 Local Background Mask Noise Reduction = 40 Test the ISO 1600 preset on multiple different ISO 1600 photos. All photos correctly receive −10 / 40. Create a second ISO 3200 LNR+MASK preset with: Local Background Mask Sharpening = −20 Local Background Mask Noise Reduction = 60 Test the ISO 3200 preset on

The reflection removal tool works well until adding denoise filter to the image. the reflection returns to the image once denoise is finished. it does not matter in what order the two tools are added to the image, the reflection returns.

Hello Adobe Team,I have found a reproducible issue with Camera Raw 18.x.System configuration:Windows 10 Pro 64-bit Adobe Photoshop 27.8 (official Creative Cloud version) Camera Raw  18.4.1 NVIDIA GeForce GTX 1050 Ti (latest Studio and Game Ready drivers tested) Intel Core i7-8700K 32 GB RAMIssue:Simply opening the Presets panel in Camera Raw causes the following error:"The graphics processor has encountered an unrecoverable error. Due to a run-time error, GPU acceleration has been disabled for the remainder of the session."After this message appears, Camera Raw becomes unstable and continues to display the same error until Photoshop is restarted.Important findings:Camera Raw 17.5 works perfectly on the same computer. Camera Raw 18.0, 18.3, 18.4, and 18.4.1 all reproduce the problem. Lightroom Classic works perfectly with the same RAW files and the same presets. The problem occurs only in Camera Raw Filter inside Photoshop. The error appears simply by opening the Presets panel. In many

camera raw 18.5 randomly freezes, doesn't crash very slow compared to past few releases

Since a few versions (18.x) DNG Converter started to not only convert my raw files, but accompanying JPEGs as well. That is not the described and expected behaviour and is somewhat annoying, because now I need to mv my raw files to a separate folder before converting and then move the results back.Since my JPEGs have a different pixel resolution than the raw files, and also from the file size, I can clearly see which DNGs derive from which source. Obviously, the JPEG is converted first and gets the basename from that. Then the raw files is converted—as expected—and gets an additional `_1` added to the basename.I have not found any setting to control this behaviour.I use Olympus cameras.DNG Converter 18.5.0.2673macOS 26.6.1, Apple silicon

I want to convert a folder full of HEIC files to JPEG and I was hoping Bridge could do this as a batch process.I am getting the following error message in Bridge (which spawns Photoshop CC in the process) when I try to open an HEIC image file:"Photoshop Camera Raw does not support HEIC files on windows". The Adobe Help page titled HEIC and HEVC media files support in Lightroom and Camera Raw says:"In the Camera Raw Preferences dialog box, ensure that the JPEG/HEIC field is set to either Automatically open JPEGs and HEICs with settings or Automatically open all supported JPEGs and HEICs. To access Camera Raw Preferences, click the Open Preferences Dialog button  in the Camera Raw dialog box." Whether from Bridge or PS I do not see the above text in my Camera Raw Preferences dialog box even though I just updated LR Classic CC, PS CC 2019 and Camera Raw this morning. Camera Raw Prefs ver 11.3.9.197Bridge ver 9.0.3.279 x64Adobe Photoshop Version: 20.0.4 20190227.r.76 2019/02/27: 1205

Error when creating in ACR 18.5.0.2673 a ‘Merge to Panorama’ with 6 NEF files, preview is OK, then saving the result to DNG : error. Lost the work, this error don’t appear with all previous version.Please advise, thanks. W11 Home 25H2 64GB RAM - Nvidia RTX-3070 8GB Studio driver 610.88PS 27.9.1 - ACR 18.5.0.2673Graphics Processor Compatibilty CheckPass:    DirectX availablePass:    DirectX feature level 12.2 available, feature level 12.0 requiredPass:    Above required VRAM (8018 MB of 1500 MB required)GPU Detected: NVIDIA GeForce RTX 3070 (NVIDIA)System infoAdobe Photoshop Version: 27.9.1 20260803.r.1 65900e1  x64 (final, Release)Number of Launches: 164Operating System: Windows 11 64-bitVersion: 11 or greater 10.0.26200.9168System architecture: Intel CPU Family:6, Model:7, Stepping:1, AVX2, AVX-512, HyperThreadingPhysical processor count: 8Logical processor count: 16Processor speed: 2496 MHzBuilt-in memory: 65408 MBFree memory: 41949 MBMemory available to Photoshop: 51302 MBMemory use

It seems like selection zoom has been removed entirely. I mean, seriously? Whose bright idea was this? I HATE scrubby zoom, and don't want to be forced to use it.

This is the kind of message I get from version 18.4.1 to version 18.5.0 when I launch the module from Photoshop. 

Xiaomi 17 Ultra Telephoto DNG is not correctly identified by Camera RawEnvironmentAdobe Camera Raw / Lightroom Classic 15.4.1 Xiaomi 17 Ultra Native DNG files captured directly by the phoneSummaryThe Telephoto camera of the Xiaomi 17 Ultra appears not to be identified correctly by Camera Raw.This causes two independent features to fail:Automatic Lens Profile matching. Automatic DCP camera profile matching.The Wide and Ultra Wide cameras of the same device work correctly.Steps to reproduceOpen a native DNG captured with the Wide camera. The correct Adobe Lens Profile is automatically selected. A custom DCP profile whose UniqueCameraModel matches the DNG is correctly listed and can be selected. Open a native DNG captured with the Ultra Wide camera. Same correct behaviour. Open a native DNG captured with the Telephoto camera. No Lens Profile is automatically selected, although the correct profile exists and can be selected manually. A custom DCP profile with the matching UniqueCameraM

Every time I try to edit raw NEF files from my Nikon camera, camera raw feels unusable. It is so slow and feels like it is going crash or freeze.Looking at other users, these issues are continuous, going back 6 years plus.I was getting so frustrated that I spent a lot of money on a new PC. and its no better.Processor    Intel(R) Core(TM) i7-14700 (2.10 GHz)Installed RAM    32.0 GB (31.8 GB usable)Graphics card    AMD Radeon RX 9060 XT (16 GB)Storage    277 GB of 2.73 TB usedSystem type    64-bit operating system, x64-based processor Camera Raw 18 what is going on? 

I have a 100 year old photo that was oil painted and framed in an oval with bowed glass. I tried very hard to light it without having a reflection of the light in the photo, but because the glass is bowed, I still had some reflections. The distraction remove tool, even at Best quality, doesn’t seem to do much. Honestly, I can’t see any significant different between before and after. Before distraction removalAfter distraction removal at BestYes, I realize the image is dark, but I thought I would brighten it after removing the glare. Any ideas? Is this tool not going to work on bowed glass? 

In the latest Camera Raw update, it stopped accessing graphics acceleration, and I can't activate it.My setup:Windows 11NVidia RTX 5070 Ti 16 GBI've tried absolutely everything: cleaning the card driver and reinstalling it, adding .old to the folders, resetting the graphics card, etc., and finally contacting Adobe technical support... who started by saying that the card was "old" and not suitable for Camera Raw... Adobe, if that's the case, please indicate it on your website, because supposedly my card is suitable (and if it isn't, few people will be able to continue using Adobe products). Lightroom handles everything without a problem, and the other programs that require GPU resources do too (Da Vinci, Topaz, etc.). After saying this, the card is suitable; the problem is with Windows. I honestly don't think so; it seems like a bug in Camera Raw. That's the only thing that has problems. I don't know, maybe it's a credentials issue or something.I'm mentioning this because I think it's a

It seems the “guidelines” warning is back in Camera Raw after having been absent for quite a while. Today, simply trying to remove the edge of a wall in an image generated the “this doesn’t fit in the guidelines” warning message that I haven’t seen in Camera for over a year now. I realize that perhsp I hadn’t conisdered the wall’s feelings about being removed from the final image, but in all seriousness, removing things like softbox edges and other minor background intrusions seems to be exactly what these sort of tools can make short work of. Please have a look and see if the guidelines can be adjusted to be more useful. I can easily go fix this in PS and will, but something simple like this shouldn’t require a trip to PS. 

In some photos, applying the Adaptive Color Profile produces weird, blotchy artifacts in brighter areas, particularly in a sky where there is strong contrast between the bright and dark areas, like a sunrise or sunset. In the attached video, the photo in Develop begins with Adobe Color as the Profile, adjusting the Highlights slider brightens and darkens the sky as expected. Changing the Profile to Adaptive Color produces noticeable, blotchy artifacts in the sky. Adjusting the Highlights slider dramatically changes these blotchy artifacts. Adjusting the Profile Amount slider also changes these artifacts. Enabling HDR mode makes these blotches disappear; adjusting the Highlights moves a prominent bright band up and down in the sky, but the blotches do not appear. I reported this in another photo a year ago, but the problem remains. It means that for some photos, Adaptive Color is quite useless. Has anyone else seen this problem when using the Adaptive Color Profile?