Lightroom Classic

When calling the LrApplication.addDevelopPresetForPlugin with the settings below, which don't include any white balance settings, the temp is adjusted to 2000 and Tint to 150.local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2}Full code examplelocal LrDialogs = import 'LrDialogs'local LrTasks = import 'LrTasks'local LrFunctionContext = import 'LrFunctionContext'local LrApplication = import 'LrApplication'local LrFileUtils = import 'LrFileUtils'LrFunctionContext.postAsyncTaskWithContext("Test apply preset", function(context) LrDialogs.attachErrorDialogToFunctionContext(context) local catalog = LrApplication.activeCatalog() local activePhoto = catalog:getTargetPhoto() -- Create preset local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2 } local newPhotoPreset = LrApplication.addDevelopPresetForPlugin(_PLUGIN, "Test preset", photoPresetTable) -- Apply preset catalog:withWriteAccessDo("Apply preset", function() activePhoto:applyDevelopPreset(newPhotoPreset, _PLUGI

Sorry, solved, problem was in front of the computer 

I’m a nature photographer and until now I’ve been shooting in JPEG, but I’ve recently switched to C-RAW. I want to upload my photos to Instagram in the same size and quality, but no matter what export settings I use, the image never looks like the original.The only time it looks right is when I set the image dimensions to small in Lightroom, but that changes the size of the crop, which I don’t want.I would really appreciate your help. Thanks in advance.

Buenas,  ayer pague por el premium de Lightroom Classic, la versión app para android, pero resulta que me figura que se cargaron todas las ediciones y tengo 1,7GB ocupado en la nube, pero sin embargo no puedo ver las fotos editadas que tenia antes de pagar premium, entro a la nube desde la PC y toda las fotos me dicen “error de procesamiento” sinceramente ya no se q hacer para recuperar el trabajo de 400fotos editadas desde hace 2 años 

Hi there, up until upgrading my Mac to Tahoe 26.2 and Lightroom Classic to 15.1.1, my navigator panel would display preset previews when i hovered over them leaving the ‘main’ image unedited.Now i either have no preview on the navigator and main image, or - after selecting ‘Enable Hover Preview of Presets in Loupe’ - i then have the preset preview on the main image and the navigator preview which is incredibly frustrating when editing larger files. Is there any workaround this?I’ve tried all the usual options in terms of clearing cache, resetting preferences, downgrading to previous versions etc. but nothing seems to allow me to just apply a preset preview to the navigator image alone.-Mark

I’m getting the “AI Edits Storage Error” in Lightroom Classic, and I’ve already followed all the steps listed on Adobe’s help page, but the issue is still happening.Here’s what I’ve tried so far: Confirmed there is enough free disk space Restarted Lightroom and my Mac Ensured only one instance of Lightroom is open Gave Lightroom Classic Full Disk Access and Files & Folders permissions in macOS Verified my user account has Read & Write permissions Checked that the catalog and .lrcat-data folder are accessible Not using any cleanup tools or cloud sync on the catalog while Lightroom is open Despite all this, the error continues to appear and AI edits fail to save properly.

Interesting problem:MacOs 26.2, LRC 15.1.1Backup catalog fails if I assign it to a network-NAS-volume. All my photos are on the same NAS-volume and I can read/write without any problem.If I change the backup-location to the internal drive, no problem. Don’t want that, because the LR-catalog itself is on the same drive.I noticed the backup process starting with much enthusiasm, then at about 40% it slows down, but does proceed till the end (compress). And then it gives up with an error message and tells me to check the rights and space (both fine).I recently upgraded LRC from v12 (on older macbook, no upgrade possible due to old MacOS) to this version (on new macbook). The old setup did work with the same NAS without any problem (other than very slow). I did not try a backup v12 on the new macbook.Working around now, backup to the same local internal drive as the catalog itself and copy the backup by hand to the NAS. Anyone has a clue? Thanks for your response!Ernst

Would a MacBook pro, M4, 24 GB RAM be adequate for running LrC?  Thinking of getting a new computer and leaving Windows behind. 

Hi there, since updating my Lightroom Classic to 15.1.1 i now have the dreaded ‘phantom’ scrolling when trying to quickly go through images in my library.If i go through each image individually, it’s absolutely fine. However if i hold the arrow key for more than a second, it will rapidly scroll through images non-stop and in most cases refuses to stop until it reaches the end.I’ve looked through previous topics - i’ve tried resetting preferences, clearing cache, disabling GPU and i have no tablets or plugins to worry about interfering. The only thing that is different is i upgraded to Mac Tahoe 26.2; i tried going back to previous versions of Lightroom after this and unfortunately the issue persists.Can anyone shed any light on what else i can try to clear this issue or a workaround? I do a lot of action photography, so quickly being able to scroll through images in library before development is a massive help vs. simply scrolling image by image.-Mark

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

Lightroom Classic is extremely slow while using the Develop Mode. Virtually unusable. It seems to be happening on AI edit features and non-AI alike. Have an XPS 17 9100.Even closing the System Info tray caused LR to go into “Not Responding” mode. I feel like as a basic level something is wrong, and that it shouldn’t be this bad of a performance. Things that have been tried:Updating Nvidia drivers to lastest Creating new catalog and importing pictures from current one (this turned out to be slower) Turned off GPU assist Everything mentioned in official Adobe documentation  Lightroom Classic version: 15.1.1 [ 202601141538-a543b18a ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26100Application architecture: x64System architecture: x64Logical processor count: 16Processor speed: 2.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 58.0%Power Source: Plugged InBuilt-in memory: 32491.0 MBDedicated GPU memory u

 AI Denoise checkbox immediately unticks until full system restart.  Description In Lightroom Classic,AI Denoise cannot be enabled on eligible RAW files. When the Denoise checkbox is ticked, it immediately unticks with no error message.Restarting Lightroom alone does not always resolve the issue; a full system restart is required.After restart, AI Denoise works normally again.  Steps to reproduce  Use Lightroom Classic for an extended session (file moves, preview building, culling).  Select a supported RAW (.ARW) file.  Open AI Denoise.  Tick “Denoise” → checkbox immediately unticks.  Expected result Denoise remains enabled and Enhance proceeds.  Actual result Checkbox immediately unticks with no feedback.  Workaround Full system restart.lightroom clasic 15.0

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. 

Old bug/issuer never fixed. Steps to Reproduce: 1. Select X originals with the same metadata Status (e.g "Has been changed" or "Up to date" or etc...)2.Set metadata to “Selected Photos” Originals only3. Select 1 Virtual Copy Actual Result: At step 3 “Metadata Status” appears as "mixed"  Originals + VCLrC doesn’t filter out Virtual Copies that do not have Metadata Status Expected Result: Virtual Copies are ignored when comparing and when displaying the “Metadata Status”   

Can you please fix the very slow photo switching speed in Develop mode?In Library mode photo switching is instantaneous, but in Develop mode it takes 1 to 2 seconds (!) to change photo. During that time I can see UI updating slowly, all sliders graying out and coming back to life.It's really disrupting my workflow, especially when I want to quickly compare two virtual copies of the photo to see subtle differences I've made.This behaviour is always so slow for all versions of LRC in the past years, no matter what hardware I used (eg. powerful PC with 4070, or MacBook M1).Look at how fast Capture One photo changing works. 

Tying to upgrade from LR v1.5 ro V15, it keeps failing when tryung to convert teh catalog file.  the Messggae is eitehr Corrupt or an Unknown error.I use the Windows version, with the files on One Drive.I have tried most of teh fixes mentioned - creating anew catalog and importing - failedMoving files to Local drive and using a clean backup - failed etcI have reinstalled v14.5 and system seems to be working.What next?

Após atualizar para a versão 15 as minhas edições não estão sendo salvas automaticamente nos XMP’s, mesmo estando configurado para que sejam gravados. Os arquivos originais (CR3) está dentro do dropbox (arquivos off-line). Somente é salvo se eu clicar em salvar metadados.Já atualizei para a versão 15.1.1 e continua sem funcionar. Nos meus 2 macbooks está assim.

Hello everyone,I have a weird situation here Si where it startLRC → LR all my collections are synced to cloud → everything is local for the files → LR on iphone works well, when i take a picture it arrives in LR the in LRC So because why not i tried to migrate my entire catalog from LRC to LR It tooks severals days to be achieved and when it was there was a lot of pictures missing, a lot o collections not as the same as in my on prem LRC So what i did is delete everything from LR, empty the trash, stopped all sync from LRC to LR to have a fresh start Now nothing works well If i take a picture from my iphone, it upload well in LR, and in LRC the sync is stuck at syncing 1 pictureTried to rebuild the sync data, not helping, tried to stop and restartTook a bundle, nothing that seems to imply some erreur from what i’m able to see So my bad trying to migrate everything to the cloud, but now what ca i do to recover something working? Thanks for reading and for any help here

Using Windows 11 and Lightroom Classic 15.1.1  I’ve had success deleting the Lcat files, but having to do that everytime is becoming a pain. I have also tried resetting preferences while launching Lightroom CC which doesn’t do anything in my scenario.