Design the future of fashion, win Firefly Pro 👗✨
Questions
Recently active
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.
I am seeing a significant performance regression with AI Denoise in Camera Raw 18.7 on a 2023 Mac Studio with an Apple M2 Ultra.SystemMac Studio (2023) Apple M2 Ultra, 24-core CPU 128 GB unified memory macOS 27.0.1 Camera Raw 18.7 Photoshop 2026 Sony A1 II RAW files, approximately 49.8 MP (8640 × 5760)ProblemAI Denoise on comparable Sony A1 II RAW files previously completed in under 10 seconds on this same Mac. It now typically takes approximately 15–20 seconds.I reproduced the problem by opening a Sony A1 II ARW directly in Photoshop/Camera Raw, so Lightroom Classic, its catalog, previews, and the location of the Lightroom photo library are not involved.During a recent Camera Raw Denoise test, Camera Raw estimated approximately 20 seconds. While Denoise was running, Activity Monitor showed the Mac remaining approximately 86–94% CPU idle. GPU History also showed relatively low GPU activity rather than sustained heavy utilization.Camera Raw Preferences > Performance identifies the Ap
Pressing G used to add a linear gradient mask. Now it brings up the new Grid layout. J used to apply the radial mask. Now it does nothing. What’s going on with the KBSCs? I’m not sure if there are others that have changed. The brush took, still works with K.
This is feedback rather than a question. I have just returned from visiting a site of ancient buddhist caves in China. The delightful Buddhist statues are behind wire mesh grids for protection. This makes photography virtually impossible. However, i took a few photos and reflection removal worked to remove the wire grid!
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.
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
any help would be good i am wasting so much time
Hello,GPU acceleration has been suddely desactivated (denoising very slow from early Sept.)My configuration :Windows 11 Home 25H2 Camera RAW 18.6How to recover CPU acceleration ? Need to switch to Windows 11 Pro ? Thanks
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.
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?
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.
If I double, click of a jpg. That I’ve already edited, it will open camera raw. But not a new jpg. I have the box clicked where it says double click opens camera raw. There is no error message.
In the last 4 days, it has happened at least 4 times where I have made significant adjustments to an image in Camera Raw - on the Edit panel, a bunch of masks, cropping, created snapshots - the works... and the image just spontaneously resets itself to previous settings. I cannot say 100% but I think it has reset them to the settings that were there when it was last opened. The snapshots even disappeared. It is definitely not user error - I am not hitting anything that is causing this to happen and I cannot Command+Z to undo it. I haven't yet pinpointed exactly what tab I am on when it happens. Has anyone else experienced this?CameraRaw 18.6.0.26982024 MacBook Air M3 16GB
Use Profile Corrections (Camera Raw, Optics, Profile) used to be automatic. Now every RAW file I open (I only shoot in RAW), I have to tell it to use profile corrections. It becomes really annoying when opening 20-30 images a day.I work on images from Nikon D-300 (not so much anymore), D-810 (the most for now) and Nikon Z8 (newly purchased) and all lenses I use appear on the Adobe list as being supported. The Z8 is not a problem as it has a built-in correction.I found instructions for a Camera Raw Preset (Stephen Marsh, 6 years ago) but it doesn’t work with the current version of Camera Raw (I’m on the prescription plan and updated).Does anyone have a way to make Use Profile Corrections permanent or automatic? Thanks for the help.
In previous versions of ACR, you could execute the following steps:edit a photo select a second photo (or multiples) hover your cursor over the edited photo to select the icon that will bring up the Synchronize box, select the edit options to apply to the second photo and click OK. All of the options you selected will be pasted to the second photo. NOW: this is what happens:edit a photo select a second photo when you hover the cursor over the first photo, the icon for Synchronize is NOT available. If you hover the cursor over the second photo, the Synchronize icon IS available. If you select it, the options on the second photo are applied to the first photo effectively wiping out all of the previous edits. Additionally NO masks are applied. The only work-around I have found to go select the dots icon, click Copy Selected Edit Settings to get the dialog box; then go to the second photo and select the dots icon and click Paste Selected Edit Settings. Making an easy process time consuming
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.