Lightroom Classic

Over the past few months, I have been extremely frustrated with my cloud edits not syncing back to LRC.  Here's my basic workflow: 1.  Import photos to LRC on an external SSD (I store all photos on my external) and add those images to a collection to sync with the cloud.2.  Once all previews are done and syncing is complete, I edit on my mobile devices (iPhone 13 Pro Max and iPad Pro 2020).  My edits will show as fully synced on either mobile device and show edits made on the other mobile device within minutes.3.  When I return to my LRC on my desktop (my external SSD stays attached this entire time), the edits I have made via mobile do not sync back and update in LRC.  When I look at my sync status, it shows the green check.  I have tried pausing and restarting sync to see if it recognizes updates that need to be downloaded from the cloud.  I have tried the pause and restart both with the app open and pausing, rebooting LRC, and then restar

Beim Importieren erhalte ich seit dem neuesten update den Hinweis "Datei konnte nicht in den Zieloedner kopiert werden, da er schreibgeschützt ist". Wie kann das wieder auf einem Macbook hergestellt werden

Upgraded to classic 12.3 on mac M1 and will not open reverted back to 12.2.1 which runs ok - any ideas

I am trying to use custom plugin-specific metadata on a per-photo basis. In the API reference for "setPropertyForPlugin" it states that metadata set using this function does not need to be declared anywhere. However, when I attempt to run a script I get an error that reads "attempt to access property that's not declared in Info.lua". Currently I do not have a metadata scheme defined nor a LrMetadataProvider file specified in my Info.lua file. I would like this metadata to only be viewable and editable from within the scope of my plugin. Did I misread the API reference stating that these metadata fields don't need to be declared? Do I need to specify my metadata id in an LrMetadataProvider file?

Some Canon EOS R5 M2 raws imported into a LR 14.1.1 catalog acquire a pink cast when the catalog is opened in 14.2, and the default As Shot Tint changes in 14.2. To reproduce with LR 14.1.1 and 14.2 / Mac OS 15.2:   0. In LR 14.1.1, verify that Preferences > Presets > Raw Defaults is set to Global: Adobe Default and there are no camera overrides.   1. Download and open this catalog in LR 14.1.1. It contains two raws from a Canon EOS R5 M2: https://www.dropbox.com/scl/fi/li67cc9uswth22wyitsox/tint.14.1.1.2025-02-19.zip?rlkey=037kh2wf6sdatm4ccadij5xjc&dl=0   2. Open _U6A4519.CR3 in Develop. Observe that it has WB: As Shot, Temp: 5,950 Tint: +29.   3. Click Reset and observe no change to the photo or the WB settings:   4. Exit LR and re-open that catalog in LR 14.2. Observe that the buildings now have a pink cast, but the WB settings remain unchanged:   5. Click Reset and observe that the pink cast has disappeared and that Tint has changed fr

There are many threads about this topic like this one for example. I purchased an Eizo CS2400S along with an EX4 calibrator and encountered an issue in Lightroom's Develop module: The Navigator image and filmstrip thumbnails display incorrect colors after clicking on an image. Initially, the colors appear correct, but after a brief loading period, they shift and remain incorrect until Lightroom is restarted. The Library module is unaffected. After researching similar cases, I found that most discussions attribute this problem to a corrupted monitor profile. A common troubleshooting step is to temporarily switch to the default sRGB profile, restart Lightroom, and check if the colors display correctly. In my case, this confirmed the issue—Lightroom displayed correct colors with the sRGB profile. The recommended solution is to recalibrate the monitor to generate a new, uncorrupted profile. However, after multiple calibration attempts with different settings in ColorNavigator 7, every prof

After a corrupt catalog issue, everything is again up and running but: - when I close Lr Classic I get the message Lr is still synchronising photos Even after 12hrs, it is still synchronising ?  Is this normal ?  Catalog is about 2300Mb

After applying Develop Settings (either via SDK or via UI), sometimes photos are left in a state where photo:getDevelopSettings() will not give correct values for all sliders, especially Temperature and Tint. (and also the visual representation in the grid does not seem to be updated - when you scroll to the image, you see it visually update only after it has entered the viewport).   Simple code snippet to try for yourself:     local LrApplication = import "LrApplication" local LrTasks = import "LrTasks" local LrDialogs = import "LrDialogs" local LrFunctionContext = import "LrFunctionContext" LrTasks.startAsyncTask(function() local catalog = LrApplication.activeCatalog() local photos = catalog:getTargetPhotos() local badSettings = {} for i, photo in ipairs(photos) do local settings = photo:getDevelopSettings() local temperature = nil local tint = nil if settings.IncrementalTemperature ~= nil and settings.Increment

I'm giving a presentation to a group this weekend and want to show my images using the full frame/fill screen (F) command so they fill the screen. The images are of different sizes but all are above 1500x1000. If I zoom the image from the Grid and then hit F, it will always fill the entire screen. But if I do not first zoom the image from the Grid, some images do not fill the screen when I hit F. Problem is, I want to run the presentation manually entirely from Fill Screen/ Full Frame mode and not have to jump back and forth to the Grid at any point. Does anyone know how to accomplish this? You can see the grid view not zoomed and the image I get when I hit F for it as well as the images form the Grid zoomed and what I get in the Full screen view for it . I need them all to fill the screen when I hit F. Thanks for any help.

Hey all,  I recently moved all of my files onto an external hard drive and have been trying to create a new library with them in Lightroom. This is an import where the already exist situation. It doesnt matter what I do, the import process hangs up. I see a few images show up in the imporrt screen and the progress meter stops. I cancel the process and start again, and get the same issue, just a few images at a time.  In some instances, when I hit cancel, an error message shows up that indicates a file which is too big or corrupted, but most often not. I can select a single date folder with just a few images and it will not import them all. I have to stop and restart several times before getting all 20 or so images to sync. This is untennable.  Anyone have any ideas? I want to simply set it and forget it to let the machine do its thing. I can do this file by file...  I am using macOS Sequoia 15.3.1, Lightroom Classic 14.2 on a 2019 iMac 27inc

As stated, in Classic I periodically get a yellow alert message with ""Regenerate previews for HDR edited images to render HDR in Library Views" and a "Regenerate" button. If I click it, it can take hours to complete. The progress bar shows "Refining Previews for HDR." So far I've been too cautious to quit LrC while it's running. So it's a big annoyance. And note it has done this numerous times, so it must be "refining" images I've already imported unless it's very very very slow with new imports. I am using 14.1.1. Everything else works fine. I make extensive use of the HDR feature, and so quite a number of images are now imported with that setting in Develop enabled. I do it by default now. I want to  know why it's happening and how to prevent it. And if I can dismiss the alert without consequences. And if I can quit LrC while it's running.  Thanks, Rob

Hi everyone, I have a problem with Lightroom Classic...I have passed after a long time in a forced way from OSX Mojave that had Lightroom blocked at version 10 (because these continuous updates in the end penalize you and are certainly not a help, something that I have already expressed several times to Adobe support)Now I have OS Sonoma with Lightroom Classic version 14 installed and also version 13.5 and both have a problem of not being able to open the Finder windows to search and update catalog folders not found, and not even doing "File > Open Catalog" opens any dialog box...I tried with the Adobe script found on this page and not even with the guide..."https://helpx.adobe.com/it/lightroom-classic/help/allow-permissions.html" All this is damn frustrating and is making me waste so much time that the new features are useless in comparison...Do you know what to do? I'm quite bitter... it seems to me that we are paying subscriptions as if we were Beta Testers and not as profes

En el modulo de mascara de personas, cuando seleccion una persona para que me cree una mascara de su rostro, piel, cabello, ropa, no me esta creando mascaras por separado, por el contario me crea varias mascaras y es la misma seleccionado todo el cuerpo. alguien sabe por que pasa esto?

I have installed version 14.2. As soon as I press any keyboard button or click the mouse I get a message to say Lightroom is not responding. The screen then freezes. I have tried uninstalling and reinstalling it but this did not work either. I can get it to work if I return it to version 13.1.1. I don't know if it is connected by I had a Topaz AI plug in and external editor plug in which should automatically show up on Lightroom. They are no longer there either.I am using a Windows 11 computer. 

I've been shooting with a few different Fujifilm cameras for more than a few years, and the standard colour profile in the camera is called "PROVIA/Standard". In LrC, the import preset in Preferences > Presets has always been "Camera settings". After importing the images, they all correctly had the camera profile name. Sometimes, prior to taking an image, I would change the in-camera setting to "VELVIA/Vivid" or "ACROS/r", which would transfer correctly to LrC.Just recently I've noticed that ALL of my images taken prior to October 2022, which were previously "PROVIA/Standard", or any other camera profile, have reverted to either "Adobe Color" or "Adobe Standard", depending on the camera. However, all images taken since October, 2022 correctly show the profile as "PROVIA/Standard", or other film simulation.Did Adobe change the protocol with the major update release in the fall of 2022 that somehow affected how my images are treated?For the images taken with my Fujifilm X-T3 that have

Olá, Tenho tido essa questão que não estou entendendo, a visualização da foto sendo editada é muito inferior a foto após a exortação. Na visualização parece até que a foto está desfocada e no resultado a nitidez está ótima, isso está me levando a erra na curadoria das fotos. Alguém tem alguma dica de como melhorar essa situação.Versão do Lightroom Classic: 14.2 [ 202502071718-3869eef7 ]Licenciar: Creative CloudConfiguração de idioma: ptSistema operacional: Windows 11 - Business EditionVersão: 11.0.26100Arquitetura do aplicativo: x64Arquitetura do sistema: x64Contagem de processadores lógicos: 12Velocidade do processador: 2,4GHzVersão do SqLite: 3.36.0Uso da CPU: 33,0%Fonte de alimentação: ConectadoMemória interna: 16224,7 MBMemória GPU dedicada usada pelo Lightroom: 2697,8MB / 3935,0MB (68%)Memória real disponível para o Lightroom: 16224,7 MBMemória real usada pelo Lightroom: 4613,7 MB (28,4%)Memória virtual usada pelo Lightroom: 27521,8 MBContagem de objetos da GDI: 1369Contagem

I’ve had this error message appear over a couple of images today in the Develop module. When I switch over to Library and back into Develop the error is no longer there, edits can be applied and the photos export with no issues. Has anyone else experienced this error being only temporary? It might lead you to believe the file is corrupt when it is actually fine. If a simple restart or module switch is all Lightroom needs to correct the issue then it should present some options alongside this error message to the user such as “reload”, “attempt to reread file” – if this doesn’t work then perhaps “reimport and replace.” Over the last year I've had this error message pop up from time to time, using different SD cards, but never had it before so it seems to be a recent issue. Lightroom Classic 13.5. MacOS Ventura 13.0.1

Win10 computer:  Current version of LrC: I have 3 catalogs.  I recently deleted the LrC software and reinstalled it because of this problem below but it still exists.  I also created a new catalog for the Family Catalog and brought my images into it.  I have not experienced this in the other 2 catalogs. Every time I close LrC, it continues to keep the .lock, -shm and -wal files open so the next time I want to open Lrc I need to delete these files.   The software seems to be working in the background a lot longer than it used to.  Sometimes I close it and check win explore and the 3 files are gone.  The next day I look before I open it and they are back, not always but sometimes. Does anyone have any ideas how to fix this?  Thank you in advance,  Tom

G'day All, I've been publishing to Flickr straight out of Lightroom for years and for the first time the automatice file renaming system is failing me. I'm running the latest version -- 14.2 -- of LRC in Win 11 When I attempt to publish photos now the file naming dialogue has no impact on the published title of the image, which will only be the title of the image in LRC. When I go to customise settings in file naming and choose 'rename to' and edit to, say, 'Name of location - year - Filename Number Suffix  

So Lightroom Classic updated yesterday now my catalogs are missing. I can load older ones but not the one I was working with. I didn't do a backup unfortunately of the last photo dump. LR wants to keep upgrading my verisions of catalogs and I think this is what messed it up. Is there some way to recover that old catalog? 

Lightroom-Classic, Apple mini,  Hallo, mein Ligtroom-Classic-Katalog zeigt mir hunderte von Duplikaten an. Die Überprüfung des Datenbestandes mit dem Finder ergab, dass jedes Foto nur einmal gespeichert wurde. Der Katalog zeigt sie mit 100% identischen File- und Folder-Namen an. Meine Frage/Bitte: Wie kann soetwas geschehen, und wie kann man/ich das Problem lösen? 

Hi, I've been going crazy for a couple of days trying to fix a problem with Lightroom Classic. I have the latest version installed as of February/2025. My problem is that the brushes I put in the Local Adjustment Presets folder I only see some (about 6 of the 50) of those that the folder contains. I have restarted Lightroom on many occasions, I have also changed the brushes that I put in the folder, but I can never see them. So I don't see a solution to this problem. Can you tell me how I can solve it?