Lightroom Classic

Lightroom Classic sur Mac reste bloqué sur “Synchronisation de 420 photos” avec le message “Problème de synchronisation”. Aucune collection n'est synchronisée et l'état de synchronisation sur le Web indique 0 photo. J'ai déjà supprimé Managed Catalog.mcat et Managed Catalog.wfindex ainsi que leurs fichiers auxiliaires, puis relancé Lightroom Classic, mais le problème persiste.Quelqu’un peut il m’aider ?

 When my long-established Lightroom Classic catalogue (~183,000 images) is opened with the drive containing the original photographs online, Lightroom automatically begins a large background image-analysis/culling operation. I am not deliberately starting Assisted Culling.During this operation Lightroom systematically reads original image files and its committed/private memory grows continuously. I have observed Lightroom reach approximately 148 GB Private Bytes, at which point Windows becomes extremely difficult to use.If the originals drive is disconnected, the same catalogue remains stable at approximately 2 GB PB.Clean Lightroom catalogues using photographs from the same physical drive and same original files behave normally: processing completes and memory stabilises. The problem reproduces in Lightroom Classic 15.4.1 and 15.5.1, and also with GPU acceleration disabled.SystemWindows 10 Pro 22H2Intel Core i9-1090064 GB RAMNVIDIA RTX 2060 6 GBCatalogue/previews on dedicated SSDOrigi

I am using Lightroom Classic 15.5.1 on an iMac. I have approximately 40,228 photographs already successfully synced over then years.I created a new synced collection containing 803 JPEG photographs. Syncing stopped with 364 photographs remaining and stayed there indefinitely.Lightroom Sync Activity shows the first affected photographs as “Uploading — [file path] — Image.”View Sync Status on Web reports no sync problems, and there is no “All Sync Errors” collection in Lightroom Classic.I tried removing individual photographs at the head of the stuck queue. This allowed syncing to progress temporarily from 364 to 362 and subsequently to 356, but it then stopped again on another photograph. A newly created synced collection also remains queued behind these photographs.I have generated the Lightroom Classic Sync Diagnostic Report.I have not used Rebuild Sync Data or reset the cloud library.Anyone out there having this problem?

I use Windows 11

When you paste only a few settings it changes the other values to 0 (default) really messed up my work flow and now cannot paste single setting when I have already edited the photo  

LrC is not working with its existing catalogue….. keeps saying corrupt, it makes copies, I delete.lock files and nothing changes…...im really sick of praying that LrC will work, its been like this for two days this week with tons of glitches and I can't access anything…. my clients are not happy!PLEASE HELP X

When I try to start lightroom classic I get the error message ?:0: attempt to index field'_nglController'  I cannot get it to start in any other way. Greg Hoglund 

Ok, so this is a small issue but it annoys me; Using the remove tool, I remove something and press “Enter” on my keyboard. The tool deselects and I can move on to the next photo in the queue. When I remove something with the Generative AI Removal tool, I remove something and press “Enter” on my keyboard...but nothing happens UNTIL I click the cursor in the empty border area surrounding a photo. Then, and only then, the removal tool becomes deselected after pressing “Enter”. This is especially aggravating when working on horizontally oriented photos where empty border area is extremely limited in size. I hope that was clear. Let me know if not, and I’ll do my best to explain more thoroughly.

I have catalog A with keywords and associated keyword tag options (ex. Export Containing Keywords) and export them as a .csv file using Metadata>Export keywords>Include keyword tag options  and then import that same file into catalog B with no keywords currently defined using Metadata>Import, will the keywords and associated keyword tag options get imported correctly to match catalog B?If catalog B has some keywords that don’t match any of the keywords from catalog A - same answer?If catalog B has some keywords that do match any any of the keywords from catalog A  - I belive the keyword tag options will not get updated, correct? Thanks. P.S. I may now regret having multiple catalogs if I have to update each keyword tag option in each one moving forward. 😁 

My lightroom classic is suddenly EXCRUCIATINGLY slow. Everything is running slowly, but especially when trying to copy and paste settings (even if there are no AI adjustments being copied). I have been waiting 15 minutes on my current image and it's not even a quarter of the way done processing.  It was working fine last week. Then one day I logged in and this started happening. I have not uploaded any images or anything in the meantime, so I know it's not a system problem ( I have a fairly good setup). This is causing me huge delays in my workflow and I've had to contact clients to extend their wait time for their galleries. 

Please add the “manual” remove setting to the camera presets you can save for specific cameras. like the sample below. No, in-camera pixel mapping does not fix this issue.  I have a couple of cameras with several of these black spots due to a sensor defect that I could just fix by using the remove tool (without generative AI) when importing.For some reason it is the only feature you have not added from the copy/parte settings to the camera presets settings. Just adding this feature would cut my workflow considerably since I would not have to hunt for those spots anymore.Thanks!D.  

I have a Classic catalog of 43,000+ photos (version 15.6 on Windows 11) that has been syncing with Lightroom online however something has gone astray recently and I get Sync Error showing maybe after a handful of photos have loaded. I think it’s overloaded and clogged and ticking Sync Keywords a few days ago probably did not help.Sync Activity always shows the same approx 70 photos, all marked “Uploading”. Online there is no folder for Sync errors (or similar). I have unticked sync on all my collections and selected Rebuild Sync Data. I am told to that it’s recommended to Generate Diagnostics Report and contact customer care.Trying here to load that diagnostics report I get “Sorry, we couldn’t upload your file because it's too big. Maximum file size: 50 MB”. It’s 321MB…Advice on how to proceed appreciated!Thanks, Scott

Currently, selecting Custom Name in the Rename Photo dialog does not display the filename of the selected photo.Instead, Lightroom Classic reuses the last custom name entered, even when a different photo is selected.This behavior is confusing for users performing single-photo renaming because the command behaves more like a persistent naming preset than a traditional rename operation.For single-file renaming, the expected behavior would be to display the current filename of the selected photo in an editable text field, allowing quick modifications without retyping the entire name.Instead, when selecting Custom Name, Lightroom initially presents an empty field rather than the current filename.What makes this behavior particularly confusing is that Lightroom remembers and automatically reuses the last value entered in the Custom Name field, even when a completely different file is selected.For example, after renaming:IMG_20260920_123456.CR3to:IMG_20260920_123456.CR3_modselecting another

AI sky masks often must be feathered entirely within the sky, without bleeding into the background below.  With the current Feather/Edge sliders, Feather can go to 100, but Edge can only go to -50.  Therefore, the practical maximum is Feather 50 and Edge -50, so that the feather remains within the sky.  The Edge slider should go to -100, so that the full feather can be applied within the sky.

 "Custom Name" or "Edit": Please populate with current name. Allow direct editing. e.g. current name “Alaska_1034.nef”  “Show Alaska_1034.nef” and let me delete “Alaska_” or change it to “Yukon_”And: include button <Copy File to New Name [same folder]> which leaves old file with old name untouched

I’m trying to detect the background/subject while editing pictures, but I keep getting the message “no background detected. couldn’t find background to select” on all images. This is a recent issue that I’ve been having and can’t figure out why. I’ve updated my Mac and Photoshop software, reset my computer, and made sure my GPU settings were set to auto. How do I fix this?