Lightroom Classic

Is anyone else having issues with the copy/paste settings? I’ve tried to use Lightroom classic, and the regular light room, and they are both having the same issue. I have a photo that was taken literally 2 seconds apart, same exact lighting and everything, when I copy my settings, which I make sure I copy EVERYTHING, then paste it onto the photo that’s literally almost identical, it turns out look completely different. I know I’m not crazy because I did compare the settings side by side from original photo and second photo, and some of the adjustments didn’t match, and the mask also weren’t the same, so it literally changing up some of the edits by itself. This drives me nutssss, there’s noooo way I can edit each photo one by one… any one have this problem or a solution for this!!? 

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

when I use the mask option in lightroom, I click on people, lightroom takes a few seconds, like its looking for people to select, but then I get a message no people found. I am using lightroom classic v15.4.1

Select a number of photos say about 200 on the film strip. auto sync on Hit auto to adjust the settings automatically. Can be done on library or develop module does not matter to the issueLightroom will adjust the settings automatically and you can go to different photos and the automatic settings would have been applied to all the photos.Now adjust one setting on one photo with auto sync on (eg. bring the vibrance or saturation down back to 0 or a different amount….in this case vibrance to -5)Browse the rest of the photos … The rest of the photos should now have auto adjustments applied + the vibrace slider to where you adjusted it manually. However when I do this other than some photos that are in immediate to left and right of the photo that was active while I did the vibrance adjustment the rest of the photos has the auto adjustments back down to 0 and the only vibrace is at -5. This seems to affect tone and vibrance saturation.. not presence (probably because auto does not affect

The latest screenshots from “Lightroom Queen” talk about Generative Expand in Lightroom Classic and new “Flatten AI Edits” options in LRC.https://www.lightroomqueen.com/whats-new-in-lightroom-2026-08/I’m not seeing any of this in the 15.5 release. Maybe this information was not intended for public release? It is causing confusion among Lightroom Classic users.

I was told that “when an image is opened in LRC, sometimes Adobe automatically creates a mask” and I want to know if that is correct and if so how do I detect or search for these auto created masks? 

This post applies to Camera Raw and Lightroom Classic. Dust Removal is no longer in Early Access status and can be found in the Remove edit panel for Camera Raw & Lightroom Classic. Dust Removal helps remove distracting spots in an image that may be caused by dust on a camera's sensor and is also effective on dust on the rear lens element. Once enabled, your image will be scanned, and any detected dust spots will be automatically removed using Content-Aware Remove. For refinement, you can select one or multiple spots to delete or refresh. Batch removal is also supported; simply select the "Dust" checkbox under "Remove" in the copy settings dialog.Please note that scanned negatives are not in the scope of this feature at this time.  Dust spots on scans tend to be located in the focal plane, with the negative and very sharp, while sensor dust is typically positioned out of the focal plane and therefore not in focus. Scanned negative dust typically appears as white spots on a darker b

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

Is Adobe AI Denoise fully optimized for GoPro MISSION 1 PRO 50 MP GPR RAW files?I've been comparing 12 MP and 50 MP RAW files from the new GoPro MISSION 1 PRO.Without AI Denoise, the 50 MP RAW files look very good and preserve more detail and color than the 12 MP files.However, after applying Enhance > Denoise, the 50 MP files frequently develop visible artifacts, while the 12 MP RAW files remain clean and natural.Other users have reported similar behavior.Is this a known limitation of the current AI Denoise model with these new GPR files, or could this indicate a bug?Are there any plans to optimize AI Denoise for GoPro MISSION 1 PRO 50 MP RAW files in a future Camera Raw update?

Not as much of a question, but more a critical remark. Recently I noted that some new features in the latest Camera Raw update were not available in Lightroom Classic. Specifically I mention some masking features like "Depth Range" and the "Feather" and "Edge" options in the "Sky" mask. Earlier on we had "Denoise" in Camera Raw not needing to create a separate DNG file, when Lightroom Classic's Denoise resulted in an extra large additional DNG file.This is very inconvenient. To use these (very useful!) features, I now have to open a raw file as a smart object in Photoshop to continue with raw editing and save the result as a very large psb file. Later when continuing with the edit, I have to reopen the psb file from Lightroom Classic.I hope it is not Adobe's policy to continue with supporting new features in Camera Raw first and only later in Lightroom Classic, I find it cumbersome and annoying when Lightroom Classic lags with feature updates, complicating the workflow and resulting in

Seit dem Update von Lightroom Classic auf Windows 11 wird beim KI-Entrauschen keine neue -Verbessert-NR.dng mehr im Ordner erstellt. Der Entrauschungsvorgang läuft scheinbar durch, aber das Ergebnis wird nicht persistent gespeichert. Beim anschließenden HDR-Zusammenfügen werden wieder die ursprünglichen RAW-Daten verwendet, wodurch das Rauschen zurückkehrt. Früher funktionierte der Workflow korrekt: RAW entrauschen → neue DNG-Dateien entstehen → HDR aus den neuen DNGs erzeugen. Getestet mit DNG- und TIFF-Export, Neuimport der RAWs und erneutem Laden; das Verhalten bleibt unverändert.

Hi Community,I’m experiencing severe performance issues with Lightroom. The app is extremely slow, barely usable, while all other Adobe Suite apps run smoothly on my system.I’ve tried restarting the app, change settings, edit on my SSD but the issue persists. I haven’t made any recent changes to my setup that would explain this. I use Windows 11, release 15.2.1 and Camera Raw 18.2.2Does anyone have suggestions on how to resolve this?Thanks in advance for your help!

When multiple videos are selected, Edit Capture Time incorrectly shows the message for a single photo selected, rather than a message that indicates the capture times of the other videos will be adjusted by the same amount as the first: When multiple photos and at least one video is selected, the message incorrectly states that videos will not be adjusted: But in these cases, the problem is just with the message being displayed. Clicking Change All correctly adjusts the capture times of the other videos by the same amount as the most-selected photo/video. Tested on LR 15.4.1 / Mac OS 26.4.1.

Lightroom Classic version 15.4Mac OS 26, Version 26.5.1Mac Studio M4 MaxPrior to the latest upgrade to Lightroom Classic I was backing up my catalog to my Synology drive. I now get the unable to write to drive error, check permissions and available space on the drives. I can backup the file locally on my MAC and then copy that over to the Synology drive. So it does not seem as though permissions is the issue. Have 16TB of storage on the Synology and 782 GB free on a 1 TB SSD on the Mac. Only started when after the latest upgrade to Lightroom Classic.

Have been having a lot of crashes with LRc 15.4.1 for a week or so. Currently the situation is so bad, that moving from library to dev the app crashes every time. I’ve been sending a lot of crash reports. I’ve also tested multiple files from different cameras over past 20 years, the issue stays.I’ve also tested downgrading LRc, issue doesn’t go away. I also tested the other Lightroom, Photoshop, Bridge and Bridge (beta) - all crashing equally the same, when changing to dev/edit or in case of bridge an ps, just opening any raw file. This suggests that the problem is somewhere in Adobe shared runtime stack that is used by all of the apps. I also repaired Creative Cloud installation, no help. Files can be opened just fine in any other capable app. I created new catalogs to see if it was catalog corruption, but it is not. I have gone through all the usual Windows error checkings, sfc, dism, chkdsk, even the memory check. no problems there. All my other apps and even games work fine. Window

Lightroom Classic 15.4.1 on Windows: 1–2 second UI stalls when selecting photos — WPR trace points to MFC/Win32 window-handle processing Hello,  I am investigating a persistent Lightroom Classic performance problem on Windows. Selecting a different image can freeze the entire Lightroom interface for approximately 1–2 seconds.  This does not appear to be caused by RAW decoding, storage performance, the catalog, previews, GPU acceleration, plug-ins, or monitor refresh technology. Windows Performance Recorder traces consistently point to Lightroom’s main UI thread spending substantial CPU time in MFC and Win32 window-handle processing.  ## System configuration  - Lightroom Classic 15.4.1    Build: 202606201310-b9f148a4  - Camera Raw 18.4  - Windows 11 Business, build 26200.8737  - AMD Ryzen 9 5950X, 16 cores / 32 threads  - 32 GB RAM  - NVIDIA GeForce RTX 2080 Ti, 11 GB VRAM  - NVIDIA driver 591.86  - Catalog stored on an NVMe SSD  - 12 MP RAW files stored on another NVMe SSD  - Approxima

Sometimes, maybe. 1 in 10 when I edit in another program, LR does not properly make a copy with Lightroom edits. It will sometimes even make the copy of a version prior to some final edits I made. It’s almost always. a much brighter version of what it should have done. You can look at the copy and original and they are not the same.