Connect with fellow editors in our Lr Classic community.
Recently active
I’m experiencing a display/rendering problem in Lightroom Classic on macOS.When Lightroom Classic is in Develop on my primary display, the image shown on the Secondary Display immediately becomes noticeably lighter/washed out when I select it. This happens in both Grid and Loupe view on the Secondary Display.The same photos display correctly in Library and Print, and the problem occurs on all four of my connected displays.Expected: The Secondary Display should show the same appearance as the photo in Library/Print.Actual: The selected photo becomes visibly lighter/washed out only when the primary Lightroom window is in Develop.I can reproduce this with a brand-new catalog and an untouched JPEG or RAW file. I have also tested with GPU disabled, reset Lightroom preferences, purged the Camera Raw cache, and updated Lightroom Classic to the latest version. The behavior remains unchanged.System: 2019 Intel iMac, Radeon Pro 555X 2GB, 32GB RAM, macOS 15.7.7.
I used to edit photos in the FIT option. and Zoom when I required to edit a specific area. I was not an issue till now. But happened to be like shifting the color/exposure when I trying to zoom. This affects the final export as well I am seeing different output that I see in the fit options. I tried by changing the GPU off and On but resulting same.
Whenever I try to apply a preset, any preset, this message pops up. “Downloading AI ModelsSome AI Models are downloading. Please try again later.”There’s nothing wrong with my internet, or disk space or anything really. It literally just started happening after an update I did (v15.3.1). I’ve uninstalled, reinstalled a few times, same thing. I can’t apply any preset, but lightroom can still function properly as normal. Can anyone help?
Using an m1 Max, didn't have this issue prior to the latest update to version 9.4 Denoise introduces banding that continues on through to exported files. Not an issue prior to the update.
Hi all. I'm SUPER frustrated right now, and feel like I've been chasing my tail. And I think that there just isn't a solution for my problem, that it is a bug in the software, but I'm really hoping that is not the case.So, when I export my RAW files as jpegs, my noise reduction settings are completely ignored, and the images turn out extremely grainy with a lot of noise.Just to clarify... I understand high ISO, I am NOT applying any sharpening or sharpening output settings, and my images look great (with NR) in both the library and develop modules.It is only when I EXPORT that they become a grainy mess.So, after spending hours researching what could be wrong, I discovered that if I export the image with ANY kind of resizing, the NR DOES apply. It is only if I try to export it in its original size that it the NR settings are not applied.Trouble is, I really want to export all my images in their ORIGINAL size. I do not want to make them smaller in any way, as I am
Description of Issue:Lightroom Classic freezes the photo preview after using AI Denoise combined with Sync across a batch of high-ISO photos. Once the bug triggers, no slider adjustment updates the preview anymore - only the histogram reflects changes, not the actual image.Lightroom Classic Version Number:15.5OS Version Number:macOS 26.5.2Camera Model:Sony A1 II / A7R V / A7S IIIStep-by-step Reproduction Instructions:Import a batch of high-ISO photos, some already partially edited. Select one photo and apply AI Denoise at approximately 30%. Select all high-ISO photos in the batch and Sync settings from the denoised photo. Navigate to the first photo in the batch (one that had edits applied prior to the denoise sync). Attempt to change any slider on that photo.The Expected Result:The photo preview updates in real time to reflect the new slider values, as in any normal edit.The Actual Result:The photo preview is frozen and does not update regardless of slider changes. The histogram does
SummaryImporting photos in Add mode (files already local on a fast NVMe volume, no copy/convert) is extremely slow. CPU utilization spikes for 1–2 seconds, then the application goes idle for 5–10+ seconds, repeating in a cycle. During the idle gaps the Lightroom window intermittently reports Not Responding. Per-second process tracing shows the import pipeline is running with a median of 2 active threads while the rest of the machine is idle. All external causes (storage, antivirus, network, background analysis features) have been measured and excluded — details below.Environment Item Value Lightroom Classic 15.5 [ 202607291506-b8869fa7 ], Camera Raw 18.5 [ 2673 ] OS Windows 11 Enterprise, build 11.0.26200 CPU AMD Ryzen Threadripper PRO 9975WX — 32 cores / 64 logical processors RAM 256 GB (Lightroom reports 261,500 MB available) GPU NVIDIA GeForce RTX (32 GB VRAM), driver current Storage
I can't open any of my LRC catalogs. I get message "AI storage error." Tried to find the Data storage file. Supposed to find it in "Help>system info>library. Window shown after these steps shows no "library."No problem opening catalogs when I move my master HD to my laptop. Laptop is running LRC 15.4. Mac Mini is running Tahoe 26.3.1 Desktop is running LRC 15.5 release. Should I re-download software on desktop mini?
In summer there is a lot of small insects in the air, which results in lots of small black dots in the sky.Unfortunately Dust removal cannot detect it as a dust, so I have to remove them one by one with Remove tool, which is not comfortable.It would be nice to improve this.Or is there any trick I'm missing?
On my laptop, when I highlight a folder>press file>export as catalog I get the dialog box but I cannot choose where I want it to be exported. After a bit lightroom says it must close and offers to report the issue. This function worked a week ago and works on my desktop. Please help I need this function.Bill
I am on Windows 11 Pro and I have the latest Creative Cloud with PS and LR Classic, Nvidia 2060S with the latest drivers. This error started appearing a couple of months ago. I start Lightroom, never mind if I open the catalogue or click the icon, and it takes 20 minutes to pop up. Task Manager shows it’s running, but it takes 20 minutes to show up.
In 15.4.1 I have found that in Lens Blur the Blur option of Brush Refinement seems broken. Using it does the same as the Focus option. Anyone else noticed this?I am running the Mac version.
I’ve noticed the crop tool is sticky again. Lightroom Classic version: 15.5 [ 202607291506-b8869fa7 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213CPU Utilisation: 1.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 11351.4MB / 15995.0MB (70%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 12382.0 MB (18.9%)Virtual memory used by Lightroom: 24292.0 MBGDI objects count: 1276USER objects count: 4660Process handles count: 19316Memory cache size: 0.0MBInternal Camera Raw version: 18.5 [ 2673 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 1660MB / 32646MB (5%)Camera Raw real memory: 1926MB / 65292MB (2%)Cache1: NT- RAM:0.0MB, VRAM:0.0MB,
Since going to the 15.5 release, the Masking tools are not working correctly. As with the attached screenshot, though there is clearly a subject, the Subject mask cannot find it. I tried with several other photos and got the same results (on equally obvious subjects).
since updating to 15.3, I’m finding that Lightroom Classic is quickly hitting a memory leak and freezing or crashing. I’m processing RAW Canon CR-3 files, often adding AI object removal, and synchronising my edits across groups of photos (including masks, AI object removals & colour grading). I find that I can only run for approximately 30 - 60 minutes before I start to encounter memory issues and either the app pauses (and doesn’t come back to life) or crashes altogether. I keep getting error messages telling me that my system has run out of memoryThis has only been a problem since updating to LrC 15.3 a few days ago.system tech specs: MacBook Pro (16-inch, 2021)Apple M1 Max64gb ramMac OSX 26.4.1
HI,I have LR classic and LR web, On LR classic I want to synchro somes photo and video, but the program stay blocked, i try to take off the synchro but it stay the same!!Can you help me?Antoine
Any mask that I create in LRC the selection turns to B&W. The only way I can revert back to color is to undo the mask. if I leave the Mask Edit menu and go to Basic Edit menu, the selected objects are still B&W and all the sliders work as expected on the B&W object, i.e. if I change the Exposure slider the B&W object change brightness just as the rest of the image. This happens with both .nef & .dng files. Ken Anderson (aka keniliamna)
Hardware:Mac Mini M4 Pro with 24 GB RAM and 16 GPU cores. The same issue also occurs on an M1 Pro. Lightroom Classic 15.2 macOS Tahoe 26.3 RAW ARW files from Sony A1, A9ii and A9i as well as compressed DNG converted files behave similarly. GPU acceleration is enabled in Preferences > PerformanceObserved behavior with AI Denoise Lightroom Classic Denoising a single image via the Detail panel is very fast: 5–7 seconds. When batch-processing even just 2 images, the first image processes quickly (normal speed), but the second image takes 38–40 seconds — about 5× slower. In larger batches (e.g., 100 images), the first image remains fast, but all subsequent images (the remaining 99) are consistently slow. Creating a preset that applies only Denoise and applying it to a single image results in the slow processing time (~40 seconds). Denoising one image quickly, then syncing that setting to another image, is also very slow.Workaround comparison: Manually scrolling through thumbnails and cli
In the recently released 15.5 LrC when modifying the capture time the list in the Library filter is not updated. Before edit capture time 001 is updated, not shown as selected on todayLeaving folder and re-entering brings in new date of 001.Modifying 002 does not show its new date. This started with LrC 15.5, in 15.4 the date list was updated immediately.Checked with Flag and Rating these new values are shown immediately when set.This is on Windows ARM.
Lightroom Classic 15.5 crashes during Assisted Culling / Auto Analysis on Windows 11, RTX 4060 Laptop GPU, 32 GB RAM. Please investigate.
Subject: Lightroom Classic – Reproducible UI Instability and Repeated Crashes After the Latest UpdateDear Adobe Support,I am reporting a serious stability issue that started immediately after installing the latest version of Lightroom Classic.EnvironmentWindows 11Latest version of Lightroom ClassicCatalog optimizedSufficient free disk space availableLatest graphics drivers installedLightroom Classic reinstalledGPU settings reviewed and testedCamera Raw cache reviewed and increasedWindows fully updatedIssue DescriptionSince the latest Lightroom Classic update, the application has become unstable during normal editing sessions.The issues occur without using any AI-powered features such as AI Denoise, AI Masking, HDR, Super Resolution or Generative Remove.During normal work in both the Library and Develop modules, I consistently experience the following problems:The histogram in the Develop module randomly disappears and then reappears several seconds later.Interface panels load slowly or
My Lightroom Classic catalog got corrupted so I created a new one and imported all my photos from the corrupted one. That worked fine. Now, I am trying to get it back to syncing properly. I enabled sync on the new catalog. Lightroom created a "From Lightroom" collection set, but all downloaded collections remain empty. Sync stopped after approximately about 2,000 photographs and has remained at that count for several days even though there are over 30,000 photos to be synced. Sync Activity continuously shows cloud asset downloads, but no progress is made. The original local collections remain intact but are no longer linked to the cloud. Enabling sync on one of those collections creates a duplicate cloud album instead of reconnecting it. Does anyone know what I should do?
Why does the Develop module not populate the image, but is a blank grey space? G, E all quickly populate proper display, but Develop, Flagging, Starring are SUPER SLOW, as in 30 seconds to register the keystroke, if at all. What is bogging this down. Came out of blue, however the images are stored on an external HD, and my Mac battery expired while the external hard drive was attached and LrClassic was open. I have the latest MacOS and Lightroom classic updates onboard.
I have an issue for about last month or so that every time I remove something from a photo, it can be a dirty spot in the sky and it can be a socket on the wall, each one of them can take 5 sec or 10 minutes.Sometimes it will remove a spot in a sec and in the next it will take forever. 5-10 minutes.I worked with gemini and this are the things I did to try and solve this:- Created a new catalog and gave it more space for cache, I think 5GB was the recommendation if I remember correctly.- I added memory to my pc now it is 2*16GB.- Changed my wierelles card now my internet is 100GB download 80GB upload.Overall my pc works very fast and has no issues, this is the only one.What else can I do to make this processes faster?I can’t work and provide results for my customers and it hurts my business badly.
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.