Lightroom Classic

Depuis la mise à jour Lightroom Classic 15 et la conversion obligatoire de mon ancien catalogue, Lightroom Classic affiche en permanence « Synchronisation de 123 043 photos ». Le compteur ne change pas, même après plusieurs heures.Le catalogue contient 168 764 photos, dont 67 198 sont indiquées comme synchronisées. La synchronisation a parfois une activité CPU/disque/réseau, puis retombe à zéro sans progression visible.J’ai déjà : réparé Creative Cloud Desktop en recréant OPM.db, puis suspendu la synchronisation, quitté Lightroom Classic, sauvegardé le catalogue et renommé le dossier Lcc transfert 24.10.25 Sync.lrdata afin qu’il soit reconstruit.Mes originaux sont sur un disque externe G:, avec une sauvegarde E:. Je ne veux pas supprimer/recréer le catalogue, ni risquer les photos ou les collections synchronisées. Merci de vérifier côté serveur l’état de la file Lightroom Cloud et de m’indiquer la procédure de diagnostic ou de réinitialisation serveur appropriée.

Around 4 years ago, I had already thought about an early version of this kind of intelligent Lightroom workflow. My idea was simple: photographers working with thousands of images should not have to spend hours manually finding duplicates, checking sharpness, expressions, open eyes, and selecting the best photographs. Today, seeing similar intelligent capabilities becoming part of Lightroom makes me even more confident that the workflow problems I identify are real and worth solving. But this is just Version 1 of one idea. Over the years of working deeply with Adobe Photoshop and Lightroom, I have identified many more: • Real user workflow problems • Missing or improvable features • AI-based feature opportunities • Time-consuming repetitive workflows • UX improvements • Performance/workflow issues • Practical solutions for photographers and creators For many of these problems, I already have ideas about what the solution could be, how the feature should work, and how it could fit into

D

Sinds de laatste update van Adobe LrC 16.5 worden de foto's enkel uit de catalogus verwijderd. Ik krijg wel het scherm efkens te zien waar ik de keuze kan maken, maar dit verdwijnt onmiddellijk en de foto verdwijnt in LRC catalog maar blijft wel op de schijf staanWaar kan ik een aanpassing doen om dat schermpje langer in beeld te hebben om een ​​keuze te kunnen maken

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

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

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

In library, I hit R to open crop tool in Develop. But this opens crop overlay, with the Zoom tool, not the crop tool. Hitting R again (closes crop ), then R again, will open crop overlay with the crop tool.The in the Right-hand panel the Crop section is greyed out too.

SummaryI am a professional photographer and use Lightroom Classic as my primary production software.On a high-end mobile workstation, Lightroom Classic becomes progressively slower within approximately 5 minutes of editing.During normal editing, dedicated GPU memory rapidly increases until almost the entire 8 GB VRAM of the NVIDIA RTX 4070 Laptop GPU is occupied. Once this happens, Lightroom becomes increasingly sluggish and eventually the entire Windows desktop (including mouse movement) becomes noticeably stuttery.The problem has existed since the laptop was purchased in early 2025.Despite extensive troubleshooting together with Lenovo support and the computer manufacturer, the problem has never been resolved.HardwareLaptopLenovo ThinkPad P1 Gen 7CPUIntel Core UltraGPUNVIDIA GeForce RTX 4070 Laptop GPU (8 GB VRAM)Intel Arc integrated GPURAM64 GBStorageNVMe SSDOperating SystemWindows 11 Pro (fully updated)CameraNikon Z8Compressed NEF RAW filesTypical file size: 30–40 MBLightroom Versi

Hi everyone. I am posting in this forum as Lightroom is what I’ve used, and I cannot find a support email address to ask Adobe directly.I subscribe to a 1TB/month cloud storage, as well as to the Creative Cloud monthly applications package. I am cancelling both services as I haven’t used them much in years. However, there are warnings upon cancelling that photos may be lost if I cancel. I’d like to not lose any of my photos, as I may want to pick my editing back up at a later time. Does anyone know the following:If I cancel my services, if I re-subscribe later, will all my photos be there again in my photo library, or would I be starting from scratch with an empty library and need to re-import everything? If the photos would still be there - will any edits I’ve made still show up, or no? Also… my mind boggles with the locations of all of my photos - when I first started they all lived on hard drives nicely organized, but once services started switching to cloud I became very confused w

Since I updated to MacOS 14.6, printing from Lr Classic to my Epson SCP800 has beeen a nightmare. The printer driver seems to have become completely unreliable.    1. When I select a profile in Lr, the printer driver has color matching set to Epson Color Controls, and not (as it should) to Color Sync. Sometimes the driver opens with Color Sync correctly set, but then changing any other setting (eg, paper type) causes it to revert to Epson Color Controls.   2. When I make changes to the print settings (eg, changing paper type) and save a preset, the change is not present in the preset. This problem does NOT seem to occur when using the print driver from Apple Preview.   I have -- reinstalled the Epson drivers -- deleted and readded my printer -- deleted my Lr preferences (but I'm confused about this because moving the com.adobe.LightroomClassicCC7.plist file out of ~/Library/Preferences doesn't seem to change anything in my Lr setup, even if I restart my machine

This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)For the Lightroom Ecosystem feedback, click here.  The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity.   New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature.   You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF

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.

Assisted Culling is now generally available in Lightroom ClassicTL; DR: Assisted Culling has graduated from Early Access to General Availability. It gives you a fast, reviewable first pass on large shoots: it surfaces your strongest frames and sets aside the obvious rejects, so you spend less time comparing near-duplicates. You stay in control: review everything, adjust the thresholds, and override any call. If you tried it back in October 2025, it's substantially more accurate now, especially for wedding, event, group, and portrait work. We'd love for you to give it another look and tell us what you think in this thread.  What it does Open an album or collection, run a cull, and Assisted Culling analyzes your images against the criteria you choose: Subject Sharpness, Eye Sharpness, Eyes Open, exposure, and more. It marks Selects and Rejects, shows you why behind every call, and leaves the final decision to you. How far it's come since Early Access  February 2026: Expanded from individ

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

While working on a project doing a lot of parameters sync, all the pictures suddenly disappeared from the directory.There were 258 pictures in this directory.The directory on the disk is also empty.I have copied back the files from a backup and re-sync the directory in Lightroom.I had to do again the modifications I have done before.

After starting LR, clicking the GPS badge of a photo centers the map on the last-displayed location rather than the coordinates of the clicked photo. To reproduce on LR 15.5 / Mac OS 26.4.1: 1. Open the attached catalog. 2. Go to Map view. 3. In the filmstrip, click on the GPS badge of "miami.jpg". Observe the map centers on Miami (correct). 4. Go to Library. 5. Restart LR. 6. Click on the GPS badge of "san francisco.jpg". Observe that the module switches to Map view and the map centers on Miami rather than San Francisco (incorrect). 7. Go to Library. 8. Click on the GPS badge of "san francisco.jpg" and observe the map moves to San Francisco (correct).  

LRC: 13.5.1Windows 11Lightroom has been really slow for me, and I was sure that facial recognition was turned off, but today I was scanning some photos that had group pictures, and LRC is still recognizing faces when I’ve explicitly turned it off. Note that it was turned off before this screen capture and has been turned off as long as I can remember, but LRC is clearly still doing it. How can I stop this? I don’t want LRC to recognize faces. I don’t want it, don’t need it, and it’s taking computer resources and slowing down my work. Thanks  NB: I am not upgrading to the newest version because it is incompatible with my Fuji GFX100 due to LRC’s native tethering causing issues. Thanks

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. 

 Hi everyone,First, ChatGPT helped writing this post since i have been talking with it about this question yesterday the whole day. now the question below:I'm having a really weird problem with Lightroom Classic and I'm running out of things to try.When I switch Lightroom Classic to Chinese, most of the UI becomes garbled/unreadable. The really strange part is that the top menu bar displays Chinese normally, while most of the rest of the Lightroom interface is messed up.Even stranger: Photoshop on the same PC displays Chinese perfectly.So I'm starting to think this might be something specific to Lightroom's UI/text rendering rather than a general Windows Chinese-font problem.SystemWindows 11 Build: 10.0.26200.8875 Lightroom Classic 15.5 Windows display language: English (United States) Display scaling: 150% Lightroom scaling: Auto Chinese fonts: Microsoft YaHei installedThings I've already triedI've gone pretty far down the troubleshooting rabbit hole:Uninstalled and reinstalled Lightr