Lightroom Classic

🔹 O que o Lightroom tem de IANo Lightroom mais atual você encontra: Selecionar Pessoa / Pele / Rosto / Olhos / Lábios (IA de máscaras) Remoção com IA (Remove Tool / Content-Aware) Redução de ruído por IA Ajustes automáticos inteligentes Perfis adaptativos 👉 É uma IA mais manual e fotográfica, você ajusta fino.🔹 O que o Evoto AI faz (e o Lightroom não faz igual)O Evoto é mais agressivo e automático: Suavização de pele “beauty” com um clique Afinar rosto, ajustar proporções Clarear dentes, olhos, olheiras automaticamente Retoque em lote de retratos Estilo mais “editorial / estúdio” 👉 Ideal pra grandes volumes de retrato (casamento, formatura, estúdio).Estou tendo que recorrer a outras soluções para tornar meu trabalho mais rápido! Tem previsão de incorporar ferramentas de IA mais automatizadas? 

Hola, al instalar LRC y al querer usar la función de quitar con IA me salta el error Eliminación generativa ha fallado. Ya había usado en otra versión está funcion, pero en esta última instalación ya no.Mi equipo : i3 10ma, 16gb ram, gráfica GeForce GT 1030 4gb. 

Reflection removal in so many cases works wonder, astonishing. However I noticed that sometimes when using denoise after the reflection removal, the reflection removal will be undone. Here is an example, a snapshot from Egyptian museum. Image 1, original.Image 2, reflection vanished.Image 3, de-noised, reflections are back. And when I try to make it the other way around (1st de-noise, than reflection removal) the process hangs and never terminates.  No reflections. Denoised, reflections are back. 

Hello, Since the installation of a graphic card (RTX 5060), there’s some visual bug on thumbnails ie. for Character selection masking.  Does anyone have an idea ? Thanks ! Here’s my specs :Version Lightroom Classic: 15.1.1 [ 202601141538-a543b18a ]Licence: Creative CloudParamètre de langue: frSystème d'exploitation : Windows 11 - Business EditionVersion : 11.0.26200Architecture de l'application : x64Architecture du système : x64Nombre de processeurs logiques: 16Vitesse du processeur : 4,2GhzVersion SQLite: 3.36.0Version Adobe GSDK: 1.4.0.171Utilisation du CPU: 0,0%Source d’alimentation: BranchéMémoire intégrée : 31853,8 MoMémoire GPU dédiée utilisée par Lightroom: 3733,2Mo / 7895,0Mo (47%)Mémoire réelle disponible pour Lightroom : 31853,8 MoMémoire réelle utilisée par Lightroom : 7821,1 Mo (24,5%)Mémoire virtuelle utilisée par Lightroom : 17164,4 MoNombre d'objets GDI : 2386Nombre d'objets utilisateur : 4870Nombre de processus gérés : 5413Taille de la mémoire cache : 1137,4MoVersion in

Bonsoir,Je sature depuis le jour où est apparu Lightroom 2025, j’ai contacté Adobe mais sans succès, j’ai naïvement pensé que la version 2026 changerai qqchose, mais rien n’a changé…J’ai un PC Portable depuis Mai 2024 :Windows 11Intel 7Nvidia 4060 8GoSSD 1 To partitionné en C 200Go et D avec le reste.16 Go de RAMSur Lightroom 2024, tout fonctionné parfaitement, c’était hyper rapide.J’ai un PC Fixe depuis Décembre 2025 :Windows11AMD 7Nvidia 5060 8GoSSD 1 To partitionné en C 200Go et D avec le reste.32 Go de RAMDans les 2 cas j’ai exactement le même problème.Lightroom fonctionne de façon aléatoire : Dans le module développement, le logiciel peut-être fluide, comme hyper lent (½ sec pour passer d’une photo à l’autre, pour ouvrir la fonction recadrage, appliquer des masques, l’ia générative ou la réduction de bruit...etc) L’export peut prendre 10/15min pour 200 photos, comme 3/5h pour 50 photos Le GPU est utilisé à 1% (Malgré que tout soit coché dans les options) et le CPU à 10/15%… Les RA

[Adobe doesn't accept bug reports of LR 14 on Mac OS 26, so I'm posting this here to inform other plugin developers and users and perhaps Adobe developers, if they're interested.] Plugins sometimes crash LR 14.5.1 with Mac OS 26.0 on Apple Silicon Macs when they try to run a child program using LrTasks.execute(), with the error in the crash log, "crashed on child side of fork pre-exec".  If this bug continues with LR 15 (officially supported on Mac OS 26), it could have a serious impact on many plugins. A similar bug occurred a year ago starting with LR 13.5, on just Intel Macs, and wasn't fixed until 14.5. Adobe's fix was suboptimal, serializing all invocations of LrTasks.execute(), creating a real performance hit for plugins that invoked multiple instances of programs in parallel (e.g. Exiftool). A better fix would have been to serialize the lower-level invocations of the operating system's fork/exec system calls, which would still allow multiple instances of LrTa

If I edit a PSD (2025) file that is in my LR catalog what magic do I have perform to get the edits to consistently update and show in LR?I can edit a PSD file, return to LR, and the changes don't show. Or I should say most of the time nothing shows. Most of the time Selecting Read Metadata From File does nothing. Sometimes if I take the edited image and go to the Develop module, the changes appear. But then going back to Grid view, the changes are no longer there. But...sometimes the edits pappear instantly. If I select the edited image in the catalog and choose to Show In Finder, the changes are there in the file previewI have no idea how to control this appearing/not appearing other than to delete the file from the catalog and re-import. That seems a little stupid.I'm going to list this as a bug since it's something that happens a lot 

After M1 MacBook Pro Upgrade to Tahoe, Lightroom Classic is running extremely slow, 3 HOURS to export 42 images. My workflow has come to a halt  Help   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules. You cannot file a bug report for Lightroom Classic 14.5.1 on MacOS 26, because Lightroom Classic 14.5.1 is not supported on that version of MacOS.]

My last iPhone photo import was on Christmas Day (25 Dec 2025). Today, a LIghtroom Classic import either identifies a very small number of year+ old photos that have already been imported or says “no photos found’; it’s inconsistent. I am on an old iMac (late 2015) running the latest macOS supported by that hardware (Monterey 12.7.6) and Lightroom Classic 13.5.1.This is a new problem.I’d appreciate any suggestions on how to get things working again.

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

I now have the Lightroom Classic version 15,1,1 camera raw 18,1  and the Tahoe 26,2.  When I wan to get red off some pictures; I now get an error message :  the file could not be moved to the Trash.  The files are on a volume that does not support Trash ! Would you like to delete them permanently ? And 2 buttons : 1 delete permanently and a second one “cancel”.  But before the 26,2 version there was not a problem at all. The Trash has the great advantage that if needed you could “reset” the files back to the place they were originally stored.  All of my photo pictures are stored on an external harddrive.  Even all my files (docs/ pdf / music ) are stored on several external HDs.  Any idea how to fix this ? On all these drives I have “reading and writing “ authority.

I have the LRC version 15,1,1 and Camera Raw 18,1  the Imac runs Tahoe 26,2.  All my photo files are stored on a external HD ( all my other files docs music etc are also on other external HDs) When I wan to remove some photos to the Trash I now get an screen telling me that those files are on a volumethat does not support Trash ! And I get the choice either to delete them permanently or “cancel”… But before the last updates LRC this question was not asked, and the files went directly to the TRASH. So that if needed you could put them back to their original storage place What is very useful should you have trashed some files by mistake.  And I do have all the reading and writing authority on that external HD. Is this just an issue ? Am I doing something wrong or ….is their something to fixed..Thanks for letting me know best regards  Willy 

BonjourLe contexteJ’utilise Lightroom Classic sur deux ordinateurs, un mini Mac doté de la puce M1 et un autre mini Mac doté de la puce M4.Les photos et les sauvegardes (ou backup) des catalogues sont stockés sur un disque externe.Le problème rencontréMi-janvier, sur le mini Mac M4, j’ai fait la mise à jour de l’OS vers la dernière version macOS Tahoe. Depuis, je rencontre des anomalies dans les fichiers backup : Le fichier le fichier zip constituant un backup contient deux éléments, un fichier lrcat et un dossier lrcat–data, et désormais deux fichiers temporaires lrcat-shm et lrcat-wal. Ce backup n’est pas exploitable sur un autre ordinateur avec Lightroom. Lorsque je visualise le contenu du dossier catalogue sur mon mini Mac M4, je constate bien que les fichiers temporaires shm et wal ont été supprimés. Si je crée un fichier zip avec les deux éléments utiles, le fichier lrcat et le dossier lrcat–data, j’obtiens une archive qui est tout à fait utilisable sur un autre micro ordinate

Capture_1 is my PSD in LightRoom.Right-click --> Edit in Adobe Photoshop (Beta)…Capture_2 is what I get in PhotoShop.

En voyage, j’utilise l’appli mobile sur IPad pour télécharger mes photos. Et je fait quelques retouches.De retour à la maison, je lance classic, et j’attends le téléchargement. Tous les aperçus se téléchargent, avec les retouches. Mais si je les ouvre, l’aperçu me dit qu’il n’a pas la photo d’origine. Or je les voit si j’ouvre CC.Je ne sais pas comment rapatrier mes originaux, avec les metadonnées de retouche, sur mon ordi..

Lightroom Classic 15.1.1 on MacOSX with 56,000 images.I have been using LRC facial recognition for years, with photos from a variety of different ages and camera sources. A few years ago, LRC was very good at identifying people even as they aged or from unusual angles. This behaviour has noticeably downgraded in 2025/2026. Faces are being shown as ‘unnamed’ even though they are of people who already have 5,000 previously identified examples.Previously, at load time, almost all new faces were being named, even if some of the identifications were incorrect. Currently, almost all new faces are unnamed. It has become so uncommon that I am surprised when occasionally my own face is correctly identified.Has there been a change in the algorithm, and if not, is there something that I can do to get the naming function to work properly again in my installation? I have tried ‘Find Faces Again’ but it just redraws the face region without making a better identification. 

I wrote a free browser userscript that automatically expands nested replies, expands the input box of new replies to fill the window, changes the initial reply ordering to oldest first, and shows up to 30 top-level replies at once.  See here for details: 

The only altered attribute was "Temp / Tint". The problem was resolved by unselecting the photos and then reselecting the same photos.     [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

Any time I try to import an image to LrC the image gets darker. Then, when I adjust the settings and export it, the image gets brighter, as if I'm editing a different version of a picture. This makes impossible to work in my LrC and I've been struggling with this issue for some time now. Please help!!! Altough my specs aren't really focused on image editing an studio stuff, I managed to work with LrC for a long time before this issue came in. I suspect it's a GPU driver thing but I've looked everwhere and couldn't find an answer. Again, I'm not talking about RAW images an the JPEG or JPG conversions that happens in LrC. This issue happens with ANY image imported to my Lightroom Classic, even a JPG downloaded from Google.I'm running Lightroom Classic with:Intel i7-7700Geforce Gtx 106016 GB RAM