Lightroom Classic

Suelo trabajar con un ajuste general a todas las fotos y luego repaso una x una en caso de necesitar algo más.El caso es que a veces uso la herramienta quitar (con IA) o bien, algún preset que contiene alguna máscara.El problema ha empezado cuando le he dado a quitar ruido (y no funcionaba) he actualizado lightroom y ha funcionado. Pero a partir de ahí, cada vez que copio una foto que tiene la herramienta quitar o el preset con máscara, se convierte en una odisea, y me sale en el cuadro de ajustes esto: “El procesamiento de IA está en curso para esta foto.La edición no está disponible temporalmente.”Insisto, hace 4 fotos no me pasaba. Y no sé que hacer. Es muy desesperante.

I’d love to see Adobe introduce AI-powered keywording in Lightroom. With several AI features already added, AI keyword generation feels like the next logical step.I have a relatively small catalog of around 8,000 images, yet keywording is still by far the most time-consuming part of my workflow. I haven’t found another Lightroom task that takes as much time and effort.An AI feature that could automatically suggest accurate keywords would make organising photo libraries much more efficient, allowing photographers to spend less time managing catalogs and more time editing, sharing, and enjoying their images.Is AI keywording something Adobe is actively considering for a future release? I’m sure many Lightroom users would find it a valuable addition.

Message récurant a chaque fermeture du logiciel Lightroom

LR Classic not opening. Macbook Pro, Tahoe 26.6. I have tried various options, including reinstalling the software and restarting the app, testing catalog integrity etc. Any suggestions?

[This bug report was originally posted on 1/26/2019 in the old feedback forum, but it never got transferred here. See the attached email message.]   In LR 14.3.1 / Windows 11, when LR is in  Window > Screen Mode > Full Screen, floating dialogs always appear hidden in back of the main LR window, and calling the toFront() function has no effect. This prevents my Any Crop and Any Filter plugins from being used in Full Screen mode. This doesn't occur in the other screen modes, nor does it occur on Mac OS 15.5.   This simple plugin demonstrates the bug:https://www.dropbox.com/s/6d1l3llo5dwzzuw/floatingfullscreenbug.lrdevplugin.zip?dl=0 Simply invoke Library > Plug-in Extras > Floating Dialog in the various Screen Modes. The command executes this simple code: LrDialogs.presentFloatingDialog (_PLUGIN, { title = "Floating Fullscreen Bug", contents = f:push_button {title = "Push Me"}, onShow = showErrors (function (t) LrTasks.startAsyncTask (s

I have a new laptop which I have installed my creative cloud elements. I can open a verson of Lightroom but cannot open Lightroom classic. 

I am having a hard time understanding editing off of a hard drive. I understand smart previews and how it generally works (all on LrC), but I don't understand the importing process. When I got the photos I wanted to import off of the folder on my hard drive, I just clicked import. Am I supposed to be doing something with the "add" button? Also, I'm not understanding collections. Are they a good equivalent to albums? And should I even use them if I have the folder connected to LrC through my hard drive? How do I move the photos to a collection if needed? Will storage be used if collections are used? For reference, I am a portrait photographer editing/culling about 600 photos and delivering galleries of about 100.

Hello: I just updated to the 15.0 release and I think I just discovered a bug. When I click Edit Capture Time via the Metadata tab, whatever time I enter is one hour off from the time that shows up in the EXIF data panel (and how it sorts the photo if "Capture Time" is used to sort the library); therefore to get the EXIF information to show up correctly, I must purposely enter the information one hour behind the time I want it to be (see screenshot where I want 5:31pm to be the edited time, but I must enter 4:31pm to get 5:31pm).  -- Scott, MacBook Pro, Apple M3 Pro chip, macOS Sequoia 15.6.1.

I have been using Lightroom AI Denoise for years. I haven't changed cameras, have not updated my camera, and have not changed RAW settings on my camera. All of a sudden AI Denoise no longer works. 

Lightroom Classic 15.4.1 always quit unexpectedly under MacOS Tahoe 26.6 beta when using Silver Efex Pro 3.0 plug in

When I switch to the developement modul, the warning sign in the thumbnails don’t show anymore. When I switch back to Bibliothek, they show again.How can I get rid of the red symbol with the white "X" on my thumbnails in the bibliothec modul? All pictures are correctly connected on the hard drive; lightroom can show them in the finder. Is it a problem with the new analyzing tool? 

LRC v15.4.1 will not open. I do not want to open a catalogue, just the LRC app.  I get a message that an earlier version (loaded on an old computer that is no longer accessible) Lightroom Catalog-2-2-v13-4 is corrupt.

Since the recent updates I have intermittently experienced a number of issues when using Lightroom Classic 15.4.1 on a Windows 11 PC (System info below):program crashed on one or two occasions; program switches from Develop to Library mode by itself;  clipping indicators show in green rather than red;  ‘Before’ image does not appear when selecting Before / After; Masking fails to find landscape features, subject or object and pop-out closes; Adaptive colour profile does not work.None of these issues were present before the update, and I tried the masking in Lightroom (desktop) without problems on an image where LR Classic failed to find the subject or landscape features. I have tried switching between ‘use graphics processor’ and ‘off’ but it does not seem to make a consistent difference - sometimes things work as expected, the next time they don’t.Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Busine

Lightroom Classic renders local Radial Gradient masks differently in Develop vs Library/Export Hi,I have a reproducible issue in Lightroom Classic that started after moving to a new computer.My workflow relies on presets containing local Radial Gradient masks.On certain photos (not all), the image looks correct in the Develop module, where the Radial Gradient is applied properly.However, when I switch to the Library module, the image immediately becomes darker, as if the Radial Gradient mask is no longer being applied.The exported JPEG matches the Library module, not the Develop module.I have already tried:* Updating Lightroom Classic to version 15.4.1* Rebuilding previews* Disabling GPU acceleration* Creating new previews* Testing on multiple imagesAdditional findings:* The issue only happens on certain photos.* It is related to local Radial Gradient masks.* Creating a completely new Radial Gradient on a different image works correctly.* Saving the problematic edit as a preset reprodu

Hello,my interface menu (font size) are so small that I cannot read the menus.How can I change this?  I am on a MS surface PC.

This has just started happening !  LRc version 15.4.1  PS Version 27.8.0When I select A RAW file (Sony ARW), and edit in Photoshop the resulting PSD file has the creation date aet to the date/time of editing and appears out of sync in the Lightroom develop module as a result. This is very annoying since it results in the original file and the edit PSD not appearing next to each other when the images are sorted by creation date. THIS IS VERY ANNOYING and has only just started to happen - it didn’t used to be like this - the creation date of the image in the ARW and PSD files used to be the same with the PSD adopting the the creation date of the RAW file.The image below shows what I mean - the image shot on 24/07/2026 - the psd fille has a creation date of 25/07/2026 - which is when the image was edited, not when it was created. If I look a at some images from just a month or so ago this did not happen the image below shows an image taken on 01/05/2026 and edited a few days later - the o

I've always had issues going back and forth with clients on proofing — Lightroom's own Web Gallery never quite cut it for this, so I'd end up just sending a folder of images, they reply "I love these three, hate that one, and can we lighten this one up a bit," then I'm cross-referencing that back into Lightroom by hand.Built a plugin that fixes it for myself: it generates a self-contained HTML gallery straight from Lightroom, the client stars favorites and leaves notes right in it, sends back a small file, and it re-imports the ratings/notes straight into LR.Cleaned it up enough that I put it up for sale (ProofingGallery, $29.95 one-time, not a subscription — enginecollective.studio/proofinggallery) but honestly just want to know if it's useful outside my own workflow. I've got 2-3 free licenses if anyone's interested in trying it out and sharing their thoughts.

Windows 11, latest Nvidia studio driver, latest Lightroom Classic version. AMD 5800X, Nvidia 4070TI. The program has started to hang on launch. It launches as a background app in Windows task manager, and next to whatever Catalog I have asked it to open it will create the usual companion files:CatalogName.lrcat-shm CatalogName.lrcat-wal CatalogName.lrcat-lock Nothing happens no matter how long I leave it. I have to kill the task, and those 3 files remain. Even though I have Lightroom set to prompt me to select a catalog every time it starts up, no matter what I try it keeps trying to open the catalog it failed to open every time it starts, even if I start it by clicking and entirely different .lrcat file.The *only* way to get the program to launch at all - even after rebooting Windows - is to remove/rename the .lrcat file it is looking for, and then it will start as normal, get to the splash screen, and create a new empty catalog with CatalogName.lrcat.  From there, I can get the progr

I have LR 15.4.1 and get frequent catalog corruption when LR locks up. The problem existed in 15.3 so it is not related to the 15.4.1 update.If I have background AI updates active then there is a good chance that LR will just freeze. I have no option except to end task. And after this point I have seen the corruption. So now I backup 3 or 4 times per day so I don't loose too many edits. On relaunch of LR, there is no UI. the all sits around 5% CPU and just a few hundred MB of memory use.The lockup does not always happen - I could update a batch of mages (select images, CTRL+ALT+U) to refresh AI info such as masks or denoise… and this could work fine for 20 images, or lock up for just 2 images. There does not seem to be any pattern.AMD Ryzen 7 3700X, 32GB RamWindows 11 (up to date)Catalog on C: - 512GB PCS PCIe M.2 SSD (NVMe)RTX 2060, 6GB, Nvidia Studio driver version 610.62NViidea driver optimised for LR    use GPU for display: On    use GPU for image processing: On     Use Graphics Pr

I'm having some issues with my exported photos not holding the edits I made in lightroom. Ive been doing some research online but so far, I've had no luck in figuring things out :/. Would greatly appreciate any insight that could be provided here as to what might be the problem.  In one of the pictures below you can see the photo is very vibrant and colorful and the other one is dull and bland.  The colorful and vibrant photo is what I see in lightroom before I export, and the bland and dull photo is what I see after I export.Thanks, in advanced!  

My Lightroom Classic just updated to the latest version (13.0).  When I exit, rather than the option of delaying writing XMP, it now says I should wait until it completes. The first time, I let it complete in case the delay was due to the update.  I didn't time it, but it took several minutes.  I went back in, and made minor edits to two images and then exited.  It's been over 5 minutes, and it's only up to 14%. Why has the message changed to say you should wait?  Why is it taking so long?

I even went back and looked at a JPG I exported out of Lightroom earlier this year and that image had a hefty resolution of 5000x4000. No problems there! I’m not sure what happened! help!