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

catalog:getCurrentViewFilter() doesn't report the new Stack options in Library Filter's Attribute bar.  This affects the popular commands Back To Previous and Forward To Next Source/Filter/Selection of my Any Source plugin.   When this is fixed, be sure to test catalog:setViewFilter() as well.   To reproduce on LR 15.0 / Mac OS 15.7.1, run my Debugging Toolkit's Debug Script command:    

Lightroom Classic crashes when backing up catalog and looking at preferences, and doing an integrity check. I'm running Lightroom Classic on a new MAC with Sonoma and I've recently upgraded all my external hard drives.  I'm a photographer for the USA Today and have an enormous catalog. My crash report header is below - the full report is beyond enornmous. My catalog is over 4 gig. Lightroom Classic crashes during the integrity check. I've reset preferenes during startup.   I've uninstalled Lightroom today and reinstalled the latest from Adobe CC.   Neither of those options have helped.  I've tried backing up my catalog to 3 other external hard drives and also to the local MAC hard disk - no luck and no success with any of that. Restart, Reboot - nothing works.   Help, please.   -------------------------------------Translated Report (Full Report Below)------------------------------------- Process: Adobe Lightroom Classic [694]Path: /Applications/Adobe Light

I have a Macbook Pro M4 Pro chip, using MacOS Sequoia 15.5 with 48GB of memory. I am using version 14.4 of Lightroom classic with Camera Raw 17.4. My Lightroom keeps crashing, with no particular pattern that I can pick up.   Is there any fix or anything I can do to resolve the issue? Your help would be appreciated.

Windows 11 21H2   If you shut down Lightroom Classic 11.3.1 with the Library Module showing, then re-launch later, the Map Module works fine.   If you shut down Lightroom Classic 11.3.1 with the Map Module showing, and then re-launch later, the Map Module is not usable. The exact form of the error changes, its not always the same, sometimes I get JavaScript error, sometimes the Map Module just freezes, other times it has other errors, but the Map Module simply doesn't work in this situation.

I just updated my LrC to v 12.4 this morning and now when I try to copy/paste settings in the develop tab to a new photo, the new photo is hazed out and flat looking. If I reset the settings and put them in manually, it looks correct, so it has to be an issue with the copy/paste. Please help this is slowing down my work flow tremendously.   PC, Windows 10

When a video is exported from Lightroom Classic that does not have the size 1920x1080 pixels, it is scaled down. Videos that are in portrait format (1080x1920 pixels) are scaled to 960x540 pixels. A video with 1440x1080 pixels becomes 1280x720 pixels when exported. Do not scale videos during export.  

Description: Lightroom Classic (v15.1.1) is experiencing a terminal hang (Beachball) immediately upon launch on macOS Tahoe 26.2. The application only functions when the system is completely offline.This is NOT a catalog or hardware issue. It occurs even with a brand-new empty catalog and with the sync engine paused.System Specs: Model: Mac mini (Mac14,12) Processor: Apple M2 Pro Memory: 32 GB RAM OS: macOS Tahoe 26.2 (Build 25C56) Architecture: arm64e Troubleshooting performed (All unsuccessful): Multiple Preference Resets: Reset preferences on launch and via manual deletion of PLIST files. Adobe Clean Removal & Reinstall: Used the official Adobe CC Cleaner Tool to wipe all Adobe products and folders (including ~/Library/Application Support/Adobe), followed by a fresh reinstall of the Creative Cloud Desktop app and LrC. Standard Troubleshooting: Followed all official Adobe "Basic troubleshooting steps" (checked file permissions, etc.). Network Diagnosis: Verified /et

Windows LR doesn't correctly open a catalog folder exported with Mac LR with File > Export As Catalog, Export Negative Files, if the Mac catalog folder contains subfolders with non-ASCII characters (e.g. á or é). To reproduce on LR 14.2 / Mac OS 15.2, Windows 11:   1. Download this .zip file containing a catalog and photos to your Mac desktop: https://www.dropbox.com/scl/fi/stbx8iyfekqk9xkuri3fi/accents.2025-02-14.zip?rlkey=xt283tc32rjarroeu4bz90jlh&dl=0   It contains a catalog created with Mac LR by doing FIle > Export As Catalog, Export Negative Files.   2. Unzip and open that catalog in Mac LR. Observe that it contains four photos in two folders and none of the folders or photos are marked missing:   2. Download the .zip file to your Windows desktop.   3. Unzip the .zip using these exact commands:   cd Desktop tar xfzv accents.2025-02-14.zip   Do not use the Windows ZIP built-in to File Explorer. It still doesn't correctly handle paths c

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

This message appears on the screen. "An internal error has occurred: attempt to index field "?" (a nil value). How can I fix this?

Dans le mode developpement, j utilise le recadrage en mettant ma souris sur les poignet  mais imposiible de recadre ou depalcer avec la min ma photo Est ce que ce bug est connu depuis la MAJ et quelle solutionPour information le reglage cadrage fonctionnebien avec le pad du pc par contre pas avec la souris tecknet (piles neuves)Merci

In LR 15.1, after deleting the catalog's .lrcat-data file, photos with Denoise or Distraction Removal applied show the error message "An unknown error occurred" in Develop.  Trying to do Update AI Settings in Library hangs LR, requiring a force quit.  This doesn't occur with the other AI commands, nor does it occur in LR 15.0.1.    This bug makes recovery of corrupted .lrcat-data files harder, forcing the user to wait for Adobe Support to repair their catalog. (Note that Denoise and Distraction Removal use the FilterList setting internally.) To reproduce with LR 15.1 / Mac OS 15.7.1: 1. Download this tiny catalog:https://www.dropbox.com/scl/fi/jm9r26rn62qffkc02q5b8/update-ai-settings-bug.2026-01-12.zip?rlkey=y0q8h9iysj9045f490cjtxobr&dl=0  2. Uncompress the catalog and open it in LR 15.1. 3. Open the photo in Develop. 4. Apply one of these AI commands: Denoise, Distraction Removal > Reflections, > People, or > Dus

Ran into this issue for the first time this week, although I've had the same workflow for years.   Edit RAW images in Lightroom Classic > select photo and "Edit in Photoshop" > make edits as needed > Export from Photoshop as JPG or PNG   Now as soon as I export the photo from Photoshop, it will immediately affect the photo in the Lightroom catalog. It removes the rating (1-5 stars) and removes ALL edit settings, but the +/- icon on the bottom right of the thumbnail remains as if there are changes made. I can go back on the photo, look at the edit history, select the most recent change and the photo will go back to the edited version that I moved into Photoshop with, but this shouldn't be happening in the first place. This also happens when I save the file from Photoshop (to my computer or the cloud).   I've checked export settings on both softwares and can't find anything.    Using MacBook Pro 2020 M1 MacOS Tahoe 26.1Photoshop 27.1Lightroom Classic 15.

Hi. In the latest version 15.1, when I change a value (e.g., from "0" to 100" or "-100"), the effect doesn't appear after entering it manually. The change only appears after pressing enter. This wasn't the case before. This makes work very difficult!

Modal dialogs created by LrDialogs.presentModalDialog() fail to release the Windows GDI objects allocated to them, causing LR to silently crash after a relatively small number of invocations of the plugin, if it has lots of LrView controls.   To reproduce on LR 15.1.1 / Windows 11 (Intel):   1. Save the script below to the file "gdi-leak.lua" in the LR Scripts folder.   2. Restart LR.   3. Open Task Manager, click Details view in the left column, right-click the column header "CPU", do Select Columns, check GDI Objects, click OK, and drag the column header "GDI Objects" to the first column position. Then click the column header "GDI Objects" to sort by that column.  It should look like:     3. Do Scripts > gdi-leak.  A dialog with 10 columns of 50 rows of text opens.    4. Repeatedly click OK.  After about 20 iterations, observe that the number of GDI Objects for Lightroom.exe has reached 10,000, the maximum value for a process.   5. Click Cancel, and then try to use LR. Observe th

  Estou notando um comportamento estranho do LRC Build [202512101606-1bb801a8] no meu sistema. Ao mandar exportar muitias fotos ( vi acontecendo com mais de 1000 fotos ) em raw , parece que o sistema fica instavel ( a windows fica ok, a maquina continua funcionando perfeitamente por horas.... o ambiente do LRC que fica instavel. Se vc fechar o LRC e abrir novamente, ele abre sem o provavel memory leak, voltando a aparecer caso vc volte a exportar as fotos  ) com o processo demorando tempo absurdo ( horas ) e a atulizacao da maquina eh praticamente zero com picos de tempos em tempos. O que notei de anormal eh que o uso de memory do sistema salta para casa de 41GB onde o normal eh por volta dos 10GB.Aparentemente uma certa quantidade de fotos eh exportada normalmente ja que a tulizacao do CPU e GPU sobem bastante mas depois a medida que o uso de RAM vai subindo e chega perto dos 40GB, o sistema "para" ... ficando com o comportamento relatado.CPU: utilizacao abaixo de

I recently set up my Lightroom Classic catalog to sync to Lightroom and monbile apps. I followed the steps to make a "From Lightroom" Collection and synched everything except for one file. Attached is a screenshot of what I'm seeing. Any thoughts? Thanks!

I am using a MacBook Pro M3 Pro omputer with 16 GB of memory as I have been for a couple of years. I use the internal SD card reader on the computer which I have tested and it gets close to the stated read speed of the card. The computer has OSX 15.7.3. My Lightroom Classic is version 15.1. My SD cards are ProGrade 256GB, 250MB/s cards. I shoot compressed RAW files on a Canon R6 MKII. I think this prroblem started with the upgrade to LR 15.   As an example, a couple of days ago I came back from shooting 3 basketball games with a little over 6,000 frames on the card, about 105 GB of data. I stick the card into the card reader and the Lightroom Classic import window comes up. I have found that I need to wait many minutes, maybe areound 10 for 6,000 files, for LR to read all the files on the card before I actually click import. If I do that everything works fine.   If I don't wait the 10 minutes, and actually verify that LR has seen all the files, they won't all import.   T

When you type a keyword into the Keyword Tags subpanel that's already assigned to the photo, the duplicate keyword is added to the list shown in the subpanel. But when you type a duplicate keyword into "Click here to add keywords" box, the duplicate never appears in the list.   See here for a user confused by this minor misbehavior: https://www.lightroomqueen.com/community/threads/lrc-15-1-sometimes-allows-the-same-keyword-to-be-entered-multiple-times.54186   To reproduce on LR 15.1 / Mac OS 15.7.1 (see the this screen recording😞   1. Start with a new catalog containing a single photo and an empty Keyword List.   2. Select the photo in Library Grid view.   3. In the Keywording > Keyword Tags subpanel, type "x" followed by return. Observe the keyword "x" appears in the subpanel and in the Keyword List.   4. Click in the Keyword Tags subpanel and type ", x" followed by return. Observe the subpanel now contains "x, x" (incorrect).   5. Go

In version 15.01 and earlier, the mask overlay would disappear when I clicked in a number field for an adjustment to highlight it.I would then use the arrow keys to change the value, and the adjustment would not commit until I pressed Enter.The adjustment increments would be the same each time I pressed an arrow key.   In version 15.1 the mask overlay does not disappear when clicking in a number field, but disappears when I start using the arrow keys.Every time I press an arrow key, an entry is added to the History panel, which rapidly fills up with unnecessary entries.The adjustment increments are not equal – if I for instance want to use negative Exposure, I get this sequence: -0.10  -0.21  -0.31  -0.42  -0.52  -0.62  -0.73  -0.84  -0.94I get similar results with other adjustments using Shift + arrow keys.This also happens with positive adjustments, but only after I reach a value of 70.   I'm seeing this on two computers running Windo

I just spent over an hour with tech support on this with no available fix.  Since the 15.0 update I am unable to use my touchscreen to adjust image size or crop.  When attempted it tries to flag the image and immediately flashes and reverts to the previous image.  I am able to use the mouse to resize or crop normally. 

I'm on 15.0.1 currently and have AI culling off as I simply don't find the feature useful and don't need it running in the background every time I enter Library mode. So to that end I have it disabled in my catalog settings intentionally, however every minute or two, the message "Enable AI Analysis in Catalog Settings to use Assisted Cullling" appears ON TOP OF the photo I'm currently editing. I click the "X" and it simply reappears a few minutes later. It's incredibly distracting, especially while cropping. I don't think it's unreasonable to expect a professional photo editing app to allow the user to edit a photo without messages popping up on top of the photo every few minutes. How can I completely disable AI culling analysis from running without having this message appear? Or is this a bug to be fixed in a future release?

In Lightroom Classic, after I created a new catalog, the file originally displayed the correct LrC logo. However, the logo has now disappeared and is no longer showing on the file icon. Tried all neassary process but not working.

The method photo:addOrRemoveFromTargetCollection() adds or removes all selected photos from the target collection rather than just "photo".   To reproduce in LR 15.1 / Mac OS 15.7.1:   1. Save these lines to the file "add-remove-bug.lua" in the Lightroom Scripts folder: local catalog = import "LrApplication".activeCatalog () catalog:getTargetPhoto ():addOrRemoveFromTargetCollection ()   2. Restart LR.   3. In Library, select three or more photos.   4. Do Scripts > add-remove-bug. Observe that all selected photos are added to the current target collection (incorrect), rather than just the most-selected photo.   If the developers consider the current behavior "as designed" (which would be very weird), then the documentation should be corrected to explain that behavior clearly.