Lightroom Classic

LR 15.2,  Windows 11 up to date,  Geforce RTX 3060 with latest studio driver, latest Epson driverIt happens many times (not always) when printing on large paper (A2 42x59 cm) at  300 or 360 dpi that LR crashes during printing, just before sending data to the printer. The GPU was set to inactive in the preferences (see screen shot)attached zip file containing 2 screen shots and the error dump produced by LRThis error is really annoying, please helpThanks

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.

I am currently using Lightroom Classic v14.0.1 on Windows 11. Flat Field Correction has been working previously on scanned negatives. However, when I try to use it now there appears to be no affect or alteration of the files. The "task bar" in the top left corner appears to finish, but there is no correction applied nor is the DNG file created. I have verified by checking the source folder for a DNG file, looking at photo in library and develop tab, tried various layouts (correction image first and last), correcting one photo to multiple, tried different locations, restarting PC, etc.  Is this a recent bug? I am using the same workflow as before and it appears to be broken right now.

Lightroom Mobile – Unable to Save Presets (Error #20190613a) Device: iPhoneApp: Adobe Lightroom MobileError Code: #20190613a Description:When attempting to save a preset in Lightroom Mobile, the application fails and displays the message: “ERROR #20190613a”. The preset is not saved and the action cannot be completed.

Has anyone else experienced losing the colour labelling after Lr Updates? This has been going on for years, but because it was more annoying than "mission" critical, I've been ignoring it.  It's finally reached the top of my Bug List. Nonetheless, what's with that?  Please fix it, it's moved past annoying.

I’m currently stuck with macOS Monterey. Is there a way to install older version of 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

I am trying to import phots from my camera into lightroom classic but keep getting a message saying either: “could not copy a file to the destination folder because it is not writable”or I am using a MacBook Pro with macOS Sequoia version 15.7.4I am using Adobe Lightroom Classic Release 15.2Destination Drive is an external Hard Drive which has all my Library PhotosCatalog is in the “Lightroom” folder inside the “Pictures” folder on my Mac I have already checked/done the following with no result:The destination drive is not full and has sufficient space still available for the photos being imported The folder into which I am trying to import the file has read and write permission in mac os Adobe Lightroom Classic has “Full Disk Access” under mac OS Settings/Privacy & Security Settings I have tried “Clear Recent Paths” in the Destination Folder I have tried unticking “Make a Second Copy To : ” in the File Handling section and then importing I have tried ticking “Make a Second Copy To

Since the latest versions of Lightroom Classic and MacOS the masking of people always shows “No people found” – even on photos where it was working before. Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-DEOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: x64Logical processor count: 24Processor speed: 3,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Built-in memory: 196.608,0 MBDedicated GPU memory used by Lightroom: 4.743,3MB / 16.368,0MB (28%)Real memory available to Lightroom: 196.608,0 MBReal memory used by Lightroom: 3.040,3 MB (1,5%)Virtual memory used by Lightroom: 55.303,7 MBMemory cache size: 62,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 631MB / 98303MB (0%)Camera Raw real memory: 644MB / 196608MB (0%)Cache1: Final1- RAM:519,0MB, VRAM:1.818,0MB, ALP05331.ARWNT- RAM:519,0MB, VRAM

Ai Masks/Healing constantly undo and need updated.  For example: - Use Ai mask on a few photos through-out a photo set.- Go through photos to make sure I'm happy before exporting and see the error "Some Ai masks need updated" - Update all Ai error messages through-out the photo set.- Go through the photos again before I export and I see the same message again. This is infuriating me as I now need to update two Ai settings and then export those two photos and move on to the next two Ai errors to export those separately.  This is the only way for me to export photos with Ai settings working. I've just got a a brand new MacBook Pro 16-inch M2 Pro 12-core CPU 19-core GPU 32GB/1TB and one of the main reasons I updated was because I thought my last laptop wasn't powerful enough to handle the Ai on Lightroom.  Turns out, it's just a bug?!

Hi everyone!I hope I didn’t miss any already existing bug / issue posts for this issue. Here’s the short version again:After upgrading to Lightroom Classic 15.2, I experience an increase in repeatable and reproducable freezes with following crashes. These occur always when zooming into an image and are instantanous. The resulting CrashLog from the error report tool is attatched as well as the Lightroom System Info sheet.  System spec overview: Windows Desktop PC (custom)OS: Windows 11 25H2 Build 26200CPU: AMD Ryzen 9 7950x3D (+ integrated iGPU)GPU: NVIDIA RTX 4070ti (12GB GDDR6 VRAM) [591.74 - Driver info see below]RAM: 64GB DDR5 6000MTs CL30DISK: LRc installed on M.2 Gen.4 SSD; Library on same drive; Media on 7200RPM HDDVER.: Adobe Lightroom v15.2First observations:Since version 14.1, I have encountered random issues, from increased stuttering to freezing. When those issues persistet and occured more often, I finally got a “KNOWN ISSUE” warning prompt once, which led me to the Adobe H

Introducing Assisted Culling (Early Access) in Lightroom Classic.  For providing feedback for Lightroom Desktop, click here.    We’re bringing Assisted Culling to Lightroom Classic as part of the MAX 2025 release! This AI-powered workflow helps you quickly narrow large photo sets to the best shots using objective signals.    What is Assisted Culling? Assisted Culling is one of the most requested features from advanced photographers, consistently topping feedback at customer events. It streamlines the process of identifying top photo selects from large sets—hundreds or even thousands—based on attributes like eye openness, sharpness, and more.    Assisted Culling saves photographers countless hours of manual review, letting them focus on creativity instead of sorting.  Eyes Open – Detects whether subjects’ eyes are open.  Eye Focus – Measures the sharpness of the eyes.  Subject Focus – Evaluates overall clarity.  Clean Up

Hi all. I’m on a M3 MacBook Air running macOS 26.3 and using  LR classic v15.2 with Camera Raw up to date at 18.2.1.My problem is that on one of my external SSDs, a 2TB Samsung T7, LR will not show the photos. In grid mode it will show empty thumbnails with meta data, like star rating, but no previews. In develop it will show only the background color.I tried building previews, both standard and 1:1, via the menu for individual files, for a group of files and for all files. The progress bar appears but does not move at all and no previews of any kind are created. I tried creating a new catalog and copying the files to another T7 SSD and creating a catalog on that, but that did not work either. The drives are all exFAT formatted. The catalog lives on the drive.I’m confused especially because for other photos, I use the same setup and it works well.The photos and folders were originally created on an HDD drive on windows and then also on windows 10 copied to the SSD and used on the SSD o

When I upload to Blurb from LRc 15.2, random photos will have horizontal blue-green lines running through them...if I upload again, different photos will have the lines...I’ve checked my fonts and padding (none) and can’t fine any apparent issues with any photos...how can I fix this?

My system info is included below.I am frequently in the position where I am happily using Lightroom and then suddenly everything in Develop starts to run at a snails pace. The Lightroom CPU load is constantly running at 20-30% even when I am doing nothing at all. Restarting Lightroom will return things to normal for a few minutes and then I am back where I started. I have even exported a subset of images to a new catalog and the same thing is happening.Application and catalog are both on an NVME SSD which is only 50% full. I have disabled the majority of plugins. Nvidia Studio drivers are up to date. Lightroom and Camera Raw are up to date.The system is clearly powerful enough to smoothly run Lightroom…..until it isn’t, which is driving me crazy. SYSTEM INFO Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Business EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical proc

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: 

My experience with LR sync has has been very disappointing. I have LR on my 13Pro set up to import every photo from the camera roll. I see the DNGs in the LR app on my phone. After a short time they will appear on my iPad. But to see them in LR Classic on my desktop (mac) can be any where from a few minutes (not usually) to a couple of hours (more likely). For instance I shot 3 images (DNG) at noon this morning and 9 hours later they are still not synced to Classic.In the past I've quit and reopened LR, paused and restarted Sync, and I've also deleted all Sync data. Sometimes these actions work, sometimes not.All I want is to have what I shoot on my phone apear on my desktop and I have no clue at this point how to have that consistently happen. MacOS 12.7.2/LR Classic 13.1

Every time I try to remove something using generative AI on Lightroom Classic, I suddenly now get “!Generative Remove Failed. Something went wrong. Please Try again”I have restarted Lightroom, and my computer. Logged out and back in.This worked before, and this suddenly started happening.