Lightroom Classic

When you change the year in Metadata > Edit Capture Time to before 2001, the milliseconds goes negative and one is added to whatever value you enter for seconds.  This is likely related to the Cocoa timestamp epoch of 1/1/2001.  If instead you change the year to 2018, the milliseconds gets decremented by one (also incorrect). To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached tiny catalog. 2. Select the photo and do Metadata > Edit Capture Time. 3. Click in the year and type 2019 (quickly, to avoid another Edit Capture Time bug).  Observe that the milliseconds field stays at 22 (correct). 4. Click cancel, do Edit Capture Time, click in the year, and type 2018. Observe that the milliseconds field gets changed to 21 (incorrect) 5. Click cancel, do Edit Capture Time, click in the year, and type 2001. Observe that the milliseconds field gets changed to 21 (incorrect). 6. Click cancel, do Edit Capture Time, click in the year, and type 2000. Observe that the milliseconds field

When viewing a film strip which is filtered to only show flagged image if I click on the flag to "unpick" the selected image and then click on the next image that image is also unpicked. It's a little complicated to explain but the attached video shows it happening and it's very easy to duplicate using these steps:Set the pick flag on multiple imagesGo to Develop Filter only so only images with the flag are displayedSelect an imageClick the flag on the thumbnail to remove it from the filtered listQuickly click on another thumbnailA second image will be removed (UNDO will return it)It seems like the time it takes for the preview for the next image that's automatically displayed when the last image is filtered out is the window for when a click on a thumbnail means the 2nd image will also lose it's flag.I believe it's a bug, it's been happening for quite a few versions now but I've posted in discussion as per the preferred method of reporting. It's become more apparent and annoying in 14

Typing into the year field in the Edit Capture Time dialog is too fussy, making it difficult for people who are slow typists (hunt-and-peck or disabled) to enter the year. If you type just a little slowly, then after 1-3 digits, the dialog thinks you've finished entering a year, and the next digit you type will erase the previous ones. Screen recording: https://www.dropbox.com/s/ks09r4f5847zwx0/capture-time-digits.2019.04.05.mov?dl=0A perhaps related problem was reported fixed back in 2015.4, though it had somewhat different symptoms. Another user just wasted a bunch of time tripping over this:https://forums.adobe.com/message/11010712#11010712The fix should be trivial: the timeout for entering digits just needs to be increased a fair bit.Tested on LR 8.2 / Mac OS 10.14.3.

Invoking the Library Filter bar’s Restore Default Presets creates duplicates of the built-in filter presets.   To reproduce in LR 15.2 / Mac OS 26.2: 1. Set the option Preferences > Presets > Store Presets With This Catalog. 2. Open the attached catalog “filter-presets-bug”. 3. In the Library Filter bar, click the drop-down menu and do Restore Default Presets. Observe that the built-in presets Default Columns, Filters Off, and Location Columns have been duplicated.  Examining those presets’ .lrtemplate files, the contents of the duplicates are identical. Before and after of the drop-down menu: 

Same  Problme  help me, please

LR fails to normalize the Unicode text of keyword names and allows the creation of two keywords that are canonically equivalent, with the same appearance and meaning under the Unicode standard. To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached file “keywords.txt” in a Unicode-compliant text editor (e.g. Textedit or Notepad). 2. In LR’s Keyword List panel, click + to create a keyword, and copy/paste the first line from the file into the keyword’s name. 3. Repeat for the second line of the file. 4. Observe there are two keywords with the same name, as defined by the Unicode standard: The two lines of the text file use different canonically equivalent Unicode representations for the same letter: U+00F6 (LATIN SMALL LETTER O WITH DIAERESIS)U+006F (LATIN SMALL LETTER O) + U+0308 (COMBINING DIAERESIS) Such keywords tripped up this user’s catalog upgrade from LR 14 to LR 15:In that case, we were unable to construct a test case that failed other than on his computer. There is a simil

LR 15.0.1 / Windows incorrectly rounds a capture date/time of 11/13/25 10:30:03.99974 PM to 1/1/1601 4:00:00.477 PM.  But LR 15.0.1 / Mac correctly rounds it to 11/13/25 10:30:04.000 PM.   Tested on LR 15.0.1 / Windows 11 Intel, Windows 11 ARM, and Mac OS 15.7.1. To reproduce:   1. Download and open this catalog: https://www.dropbox.com/scl/fi/3psajur7hfth6ezly98vk/subsec-bug.2025-11-18.zip?rlkey=e3ww25awh8wf3rmrf1nr6x8am&dl=0   It contains two photos with these capture date/times: subsec.dng: 2025:11:13 22:30:03.99974 subsec-smaller.dng: 2025:11:13 22:30:03.99900   2. Right-click the folder "pics" and do Synchronize Folder.   3. On Mac, observe the capture/date times of the two photos have been rounded correctly:   But on Windows 11, observe that the capture time of "subsec.dng" has been mangled to 1/1/1601 4:00:00.477:    

Upgraded to 11.3 this morning. 11.2 and previous worked without problems.   I notice the following: Using the hand tool to reposition the image within the print frame: Up and down are reversed.    For example I am printing a photo of a model on white background. If I reposition the photo so that the model is in the center of the frame I have to click and drag the image in the opposite direction to which I want the image to move.    So with the model in the center of the frame and with ample padding around the image the print comes out with her toes cut off????    If I then reposition the image on screen so that the models toes are cut off the print comes out with the model centered nicely with ample padding around the image!!!!   Richard

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

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

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

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