Connect with our global Camera Raw Community.
Recently active
camera raw 18.5 randomly freezes, doesn't crash very slow compared to past few releases
When reviewing and culling photos in Adobe Camera Raw, the counter displayed at the top of the interface always shows the original number of loaded images, even after some of them have been marked for deletion.For example:Load 100 images Mark 25 images for deletion The counter still shows 1 of 100This makes it difficult to see how many images will actually remain after the culling process.I would like the item counter to reflect images that have been marked for deletion, or at least display that information in real time.For example:DSC_XXXX.NEF (1 of 100 • 25 marked for deletion)This small UI improvement would make the culling workflow much clearer, especially when reviewing hundreds or thousands of photos. Users could immediately see how many images are pending deletion without having to keep track mentally or wait until the files are actually deleted.The attached screenshot shows the current counter, which could be enhanced to provide this additional information. Thanks!
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
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
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?
Przydała by sie funkcja Koło barw taka podobna jak
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
In Camera Raw, it would be nice to have more precision in the Geometry tab when you want to shift an image along the X or Y axis. Using the slider to the right or left with a mouse isn't precise at all. Ideally, you should be able to increment the values by +0.1 or -0.1 using the <- or -> keys on the keyboard.The “Constrain to Image” checkbox should also be moved back to where it used to be, right next to the Magnifying Glass checkbox. Since the latest version, you have to right-click on the photo and select “Constrain to Image,” which is sometimes grayed out even though it should be active. This is truly an incomprehensible regression.
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.
SummaryPanorama Merge with Perspective projection anchors the output projection plane on the first image in filmstrip sort order. The geometry of the merged panorama therefore changes when only the filenames change, with identical pixel data, EXIF and capture times.EnvironmentCamera Raw 18.4.1, macOS 14.8.7, Sony SLT-A77, 3 frames shot right to left.Steps to reproduceSelect the 3 frames, Merge to Panorama, Perspective, Boundary Warp 0, Auto Crop off. Repeat twice, renaming the files so that the centre frame, then the left frame, sorts first.Actual resultThree different output geometries.Case 1 - Right image first.Case 2 - Center image first.Case 3 - Left image first.Cases 1 and 3 are exact mirror images of each other, indicating the output plane is aligned with the optical axis of whichever frame sorts first, with no re-centring applied.Expected resultOutput geometry depends only on image content, not on filenames.Suggested fixDerive the output plane orientation from the estimated came
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?
Please add generative expand for cropping in Adobe Camera Raw. I love that Geneative AI is added as an opton for "remmove," but it would be GREAT if we could expand the crop area byond the original image and use Generative AI to expand...just like in Photoshop.
Attached is a photo I took this afternoon witih my new Pixel 10. The various C2PA verifiers and inspectors are happy with it. I pull it into LrC (via the Android Lr app) and try to export it with C2PA attachment enabled. It refuses to do this, simply saying "Couldn't apply Content Credentials (1) and then the file name. In Ps however I can open it, enable Content Credentials and then export. c2patool likes it, but the online c2pa verifiers/inspectors report breakage and failure to validate.
Steps to reproduce: 1. load image in ACR 2. choose the crop tool (C) 3. enlarge the canvas (check "enable expand" first) 4. apply a manual transformation Result: the stretched image is confined by the dimension of the imageExpected result: the stretched image is only restricted by the size of the canvas Workaround: Export image with enlarged canvas and use ACR from there
I am a professional wedding photographer and I edit between 30,000 and 50,000 RAW files every year using Photo Mechanic, Adobe Bridge and Camera Raw.For many years, after confirming a crop in Camera Raw, the image automatically returned to 100% zoom. This behavior became an essential part of my editing workflow and muscle memory.Since updating to Camera Raw 18.4.1, this behavior has changed. The image now remains at the previous zoom level, forcing me to manually press Command + 1 after almost every crop.This may seem like a minor interface change, but for professionals editing tens of thousands of images every year, it adds thousands of unnecessary keystrokes and noticeably slows down the editing process.Please consider restoring the previous behavior or, even better, adding a preference that allows users to choose what happens after confirming a crop:• Return to 100% zoom• Keep current zoom• Fit on screenCamera Raw is an exceptional tool, and this request is simply about preserving t
Nikon cameras stores the focus point that was in focus and the exposure was taken. This would be extremely valuable to see for a sports/action/wildlife photographer.
Hi Adobe Team,I am writing to express my strong frustration regarding the latest Adobe Camera Raw updates (v18.4 / v18.4.1). [1, 2]With the latest update, the automatic limitation feature for mass automation/batch processing was completely removed or broken. Because of this regression, I was forced to manually limit and process hundreds of images individually, which completely ruined my high-volume workflow and cost me hours of manual labor. [1]Due to this severe limitation, I had to uninstall the latest version and downgrade back to version 18.3.2 just to keep my daily business running. Batch automation is a core requirement for professional photographers, and removing or breaking this automation constraint makes the plugin unusable for mass editing. [1, 2]Please treat this as a critical bug or regression and restore the automatic limitation for batch workflows in the next patch.System Environment:Previous Working Version: v18.3.2 Broken Version: v18.4 / v18.4.1 Windows 11 Thank you,
Every now and then I get errors whilst using ACR in Photoshop stating 'The graphics proccessor has encountered an unrecoverable error, due to a runtime error GPU acceleration has been diabled for the remainder of the session' - often when using masking tools. Also get: 'Camera Raw requires graphics processor acceleration to edit photos' This is happening on my new PC running Win 11 with an RTX 5070 Ti 16GB graphics card. I've tried addressing this with support but all I've been advised to do is rename the 'GPU' file so that a new one is created which has made no difference. Oddly, I have similar issues on my previous PC so I asked Adobe support if any of the items are copied form my old installation to the new one such as crop presets and Actions could be connected but was advised that they would not. I generated a log file which I uploaded to Adobe but they have not commented on what if anything this shows. Unfortunately I feel I am just being given an
I am missing the Histogram in Adobe ACR. I clicked on something in the window and it went away.ACR 18.4.4
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.