Lightroom Classic

OK. Now I see what happened, so I’ll start over. I’m hoping that someone has an idea for a fix for this.Re: LRC 15.4.1Running painfully slow. A little history: I’ve been a Lightroom user for over 10 years, along the way Lightroom would bog down once in a while, but it always seemed to function good enough, until it became unacceptable. I was due for  a new system so in 2012 I purchased a new XPS8500. Things went well, but the day came where Lightroom slowed to a crawl again. Fast forward to 2018 when I purchase my present system. Specs:Dell XPS8950Win 11 Pro32GB DDR4 2266 Mhz1TB SSD2TB 7200 rpm HDD NVIDEA GeForce GTX 1080 w 8GB GDDR5X Graphics MemoryBDRE DriveWith this system all problems all Lightroom problems vanished and I could multitask with several photo applications along with Lightroom with no problems. Editing became a pleasure once again.Lately everything regarding Lightroom is once again becoming intolerable.I’ve watched several videos on how to speed up LRC, but all to no a

I was asked if I could help a Mac user of LrC resolve a problem, but being a Windows user, I have been unable to help.Whenever they run LrC inDevelop, this cache location rapidly consumes their hard drive storage:/Users/[username]/Library/Caches/com.adobe.LightroomClassicCC7/com.apple.e5rt.e5bundlecacheIn the user’s own words: ‘Issue: A cache folder grows continuously while Lightroom Classic is open in the Develop module, eventually consuming almost the entire SSD. The problem has been so bad for months, this user is about to ditch LrC forever. 

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

What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!  

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).

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?

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  

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.   

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) 

Since the latest versions of Lightroom Classic and MacOS the masking of people always shows “No people found” – even on photos where it was working before. Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-DEOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: x64Logical processor count: 24Processor speed: 3,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Built-in memory: 196.608,0 MBDedicated GPU memory used by Lightroom: 4.743,3MB / 16.368,0MB (28%)Real memory available to Lightroom: 196.608,0 MBReal memory used by Lightroom: 3.040,3 MB (1,5%)Virtual memory used by Lightroom: 55.303,7 MBMemory cache size: 62,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 631MB / 98303MB (0%)Camera Raw real memory: 644MB / 196608MB (0%)Cache1: Final1- RAM:519,0MB, VRAM:1.818,0MB, ALP05331.ARWNT- RAM:519,0MB, VRAM

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

AI Denoise consistently fails to complete on my machine. This is 100% reproducible and has persisted across multiple Lightroom Classic and Intel driver versions, including the current pairing of both.System:Lightroom Classic 15.4.1 [202606201310-b9f148a4], Camera Raw 18.4 Windows 11 Home 26200 Intel Core Ultra laptop, 16 logical cores, 32 GB RAM Intel Arc 140T integrated GPU (16 GB shared), driver 32.0.101.8860 WHQL (current, verified in Device Manager) Files: Fujifilm RAF (X-Trans)Symptom:Click Denoise. The background progress indicator (top-left) immediately shows roughly 10% progress, then never advances — waited well over an hour. The photo becomes locked: "AI processing is in progress for this photo. Editing is temporarily unavailable." Task Manager shows the Arc 140T near 100% compute utilisation for the entire time, so the GPU is actively executing something — it just never finishes. Exiting Lightroom during this state leaves orphaned Lightroom processes that must be killed in T

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. 

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? 

hii copied my lightroom catalogue to an expernal encrypted usb-drive. I can’t open it directly on the external drive (because it is read-only) so i copied it on my notebook (windows).When i open it in Lightroom it updates the catalog (which works fine) and then opens it …. unfortunately not a single preview is shown although i also copied those files with the catalogue(yes, i did not take all original photos with me as i intended to do most work in the catalogue section (where the previews would be enough to have).can i somehow get those previews to be shown in the catalogue? 

This post applies to Lightroom Classic and the Lightroom Ecosystem products. Camera Raw feedback can be found here.   Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size.    Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now.    We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed.    Batch updating is also now supported for Generative Remove spots.    Try out the latest updates and share your feedback with us here. Please also include the following details in your post:  App versi