Bug Reports

The Heal overlay used to work perfectly in previous versions of Lightroom Classic for Windows. You just pushed "H" to hide or unhide. Now, in 13.4 the closest thing is to use "Auto", but it shows you all the heal spots and you can't do a heal that is overlapping a place that has already been healed, unless you change to "Never", but then you can't see the overlay that shows you where you are sampling from. I hope this makes sense.   Is this a bug, or is lightroom going backwards?   It's driving me bonkers!   

Since I updated to MacOS 14.6, printing from Lr Classic to my Epson SCP800 has beeen a nightmare. The printer driver seems to have become completely unreliable.    1. When I select a profile in Lr, the printer driver has color matching set to Epson Color Controls, and not (as it should) to Color Sync. Sometimes the driver opens with Color Sync correctly set, but then changing any other setting (eg, paper type) causes it to revert to Epson Color Controls.   2. When I make changes to the print settings (eg, changing paper type) and save a preset, the change is not present in the preset. This problem does NOT seem to occur when using the print driver from Apple Preview.   I have -- reinstalled the Epson drivers -- deleted and readded my printer -- deleted my Lr preferences (but I'm confused about this because moving the com.adobe.LightroomClassicCC7.plist file out of ~/Library/Preferences doesn't seem to change anything in my Lr setup, even if I restart my machine

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

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

Windows 10 64 with all updates, LrC 11.2   Long story short: Lr's FFC works not as described. Description tells that only first or last file in sequence is treated as the reference flat field frame, but actually every file is checked for uniformity, and if Lr decides that it is uniform enough to be treated as the reference - it is treated, and the next file treated as photo is corrected using this "new reference" file that actually is a real photo, just not-so-contrasty.   It leads to two issues: - not all files are corrected - if there is a file in the middle of the sequence that is not corrected, then files after (in the direction from real reference file) that file are corrupted.   Steps to reproduce: - do as described in the guide: place a real reference file first or last in the sequence - have one or more files with low contrast in the sequense - perform FFC   ER: all files are processed using first or last file as reference. AR: every file is checked for havi

I updated Lightroom on Oct 16, 2024, and now it keeps crashing shortly after I open it. What can I do?   Thanks!

I noticed after updating my new v10 converted catalog that LrC was acting slow in the Library module, so I disengaged the usual culprit for this, the "Automatically write changes into XMP" setting. Then to my dismay, I noticed that it proceeded to mark the majority of the photos in the current grid view as needing a metadata update, even though the catalog metadata was fully saved to XMP prior to the upgrade, as far as I was aware.   Then I paged down, and the pattern repeated: Lightroom scanned all the now-visible photos and found that almost all of them also needed to be updated on disk.   And I did it again. And again.   Eventually I wrote a script to send "Page Down" events to the program periodically to ensure that Lightroom looked at every photo in the catalog, then let it run overnight with the library filter set to "Metadata Status = Up to date", so that it would give me the list of photos that need no metadata update. The next morning, I scrolled the grid back u

Attached video shows new issue with 13.5 and 13.5.1 since the "fix" for the automatically added white balance: as shot in the history.With the update thumbnails in develop are resetting to the embedded preview and sometimes the white balance in the main image is not being updated until the user changes a value.Video starts with me switching images and then hovering the mouse over the thumbnail of the last image which makes it reset to the embedded preview (icon reappears).   I then circle the bride's arm before adjusting the clarity slider a tiny amount and you can see the white balance updates.   Next I switch to the previous image and again hover over the thumbnail which switches back to the embedded preview.   Finally I switch back the other image and this time the white balance is shown correctly.LRc isn't always creating a preview for an image when viewed in Develop unless the user changes a value. Sometimes it does but I cannot find a repeatable set of steps. I hav

When editing an image in the Develop Module ie changing any of the sliders the image on the secondary display momentarily turns black. The primary display stays ok.   PC specifications:LR 14.1 - Using Graphics Processor on Auto or CustomW11 Pro - 23H2Intel Core i7 12700 K - 32 GB RAMGeForce RTX 3060 Ti - 8GB - with the latest drivers

Issue still present in 14.2.(Note: started a new thread at the request of the Classic Team to file a new bug)

Hello there !    Mys problem is the following : once Lightroom Classic is opened, it always crashes after few seconds. I can't work on my images from Japan. I have the latest version and I work on MacOs Sequioa.    What's going on ? Any ideas ? Its a first for me...   Thanks anyway

Version: Lightroom 10.1.1 Platform: iPhone 16 Pro Max with iOS 18.2   Pictures taken with Lightroom Mobule iOS on the iPhone 16 Pro Max have just "iPhone" as model name in the meta data. Previous iPhone models such as iPhone 13 Pro had their exact model name embedded. This makes it really cumbersome to filter in certain parts of Lightroom. Please check the attached images. Note the generic "iPhone" model name for the iPhone 16 compared to the exact model name for the iPhone 13 Pro.      

Since the latest update of Lightroom Classic, I can no longer apply presets to videos in the Library module. I can select the presets, but they don't change the appearance of the video at all. Restarting my Mac and Lightroom didn't resolve the issue.

HI, today I licensed Adobe Cloud with LR Classic 14. I installed LR Classic 14. After start LR tried to upgrade my old legacy LR 6 catalog to the newest format. An error message occured.   Questions: - Can LrC 14 migrate an old legacy LR 6 catalog? - How can I avoid the error during upgrade?   Thanks.  

Mac LR gets confused in various ways when opening a smart-previews catalog exported from Windows, when the source folder for a photo contains a non-US-ASCII character such as é. This confusion doesn't occur when the same folder is renamed to include e rather than é. Tested on LR 13.3.1, Mac OS 14.5 and Windows 11. To reproduce:   1. Download and open this catalog on Mac, which was exported from a Windows 11 catalog with just the option Build / Include Smart Previews: https://www.dropbox.com/scl/fi/nb1wx44ryf0l0ariq13gj/special-char.2024.06.15.zip?rlkey=zidmlyy9zdakywtcoc68f4rtv&dl=0   2. Observe the source folder was named AéB and that the preview thumbnail is grey (incorrect) and there is no smart-preview badge (incorrect):     3. Edit the photo in Develop and change Exposure. Observe that the Histogram says "Original + Smart Preview" (incorrect, should be just "Smart Preview"):     4. Observe that the metadata-status badge indicates "Meta

If you select a Library Filter bar preset, toggle off filtering with Cmd L, and toggle it back on, sometimes the previous state of the filter bar set by the preset is not properly restored. The conditions that trigger this are very obscure but highly reproducible.  To the average user, it looks entirely mysterious.   To avoid this bug, use these precise steps:   - Select any Library Filter bar preset (don't skip this step). - Select the preset Filters Off. - Define the preset.   Tested on a virgin installation of LR 14.1.1 on a virgin installation of Mac OS 15 (a virtual machine) -- screen recording attached. Follow these precise steps:   1. Import a JPEG.   2. In the Library Filter bar, click the preset popup and select the Camera Info preset.   3. In the Metadata browser, change the first column to File Type and select JPEG. Delete the other columns. Save as the preset "JPEG - Camera Info".   4. In the Library Filter bar preset popup, select Fi

Adobe LrC and CR are not recognizing Apple iPhone DNG files as being raw files. (1) When I import into LrC using Copy As DNG, the error message says: "Non-Raw Files Were Not Converted to DNG", (2) The new PS CR feature to remove reflections from shooting through glass gives error message that this applies only for RAW files (but this IS a raw file), (3) LrC Develop Basic Auto button hardly makes any changes including leaving major clipping. It appears that Apple ProRAW file format is not being recognized by Adobe products as being a RAW file.

Have been using Lightroom Classic on MacBook 16 Pro (2021) for 3 years without problems.  Beginning around 1/1/2025, have had 2 new problems:    1) Import of new photos from SD card (Canon R5, firmware 2.1.0, RAW images) is sometimes incomplete.  May have 600 new photos, only imports 85, or 200.  Repeating import 1-2 additional times usually succeeds.2) While simply reviewing images, LRC crashes.  Does automatic test of Apple system, which always shows no problems.  Long technical error message on screen which I am not skilled enough to interpret.  (Have not yet made a screenshot of this message, will do so ASAP.).  Crashes occur 2-3 times during a single review session of 300-500 images.  (All still images).   Troubleshooting:  Have upgraded cmaera firmware, MacOs, LRC version.  Have uninstalled, reinstalled LRC through Creative Cloud.  Have tried creating new catalogue.  Have not yet tried deleting preferences

The ExtractPreviews script in this help article: https://helpx.adobe.com/lightroom-classic/kb/extract-previews-for-lost-images-lightroom.html    doesn't work in LR 14.0.1 on Mac OS 14.6.1 or Windows 11. No matter which photos are selected, it always produces this error:   This appears in the console log when you run the script:   2024-11-24 11:54:29.038 Adobe Lightroom Classic[77127:11037041] Could not open file "/Users/john/Lightroom/cats/Test-14/Test-14 Previews.lrdata/0/062F/062F71E0-1BE7-43EA-B951-332C8CF33405-2bbfa387aba361443ffb2e579b214e8c.lrprev" 0: field parseMultiSectionFile - C 1: upvalue ? - 71:134+5 2: [unnamed] - 108:205+4 3: global pcall - C 4: method next - 187:445+27 5: upvalue ? - 1438065897:158+21 6: upvalue ? - 1438065897:489+11 7

LRC 14.0.1 - Camera Raw 17.0 ProArt Z790 Motherboard Intel Core i9-13900K 64GB Ram Nvidia RTX 3090 OS & LRC are installed on a 2TB Samsung NVMe drive with over 700GB free. Images are on an EditShare NAS, 30TB "partition" with 12TB free. I was struggling with an import of a large number of images (about 750,000 from a multi-year time-lapse). The images are GoPro Raw (.gpr) and just over 5MB each. I initially thought that maybe trying to import them to an existing catalogue was causing the issues, so I created a new catalog. That didn't change anything.I thought then that the issue with the long import time was just the number of images, so I left it running over my long holiday, about 4.5 weeks.   I came back today and it had barely processed 33% and was still going! Some additional troubleshooting I tried was in resetting the preferences (that didn't work) and then trashing the preference file manually (that didn't work). I thought maybe the cache was overloaded, but it's set

Since the Update to LrC 14 and subsequently 14.0.1 LrC always crashes shortly after using denoise AI. I am using an 16" Macbook Pro with a M3max with the 40 core GPU and 64 GB of unified memory and 2tb ssd. macOS Sequoia 15.0.1 [Moderator removed Crash Report and Attached at Text File]

Hello! After updating to 11.4, when I export to DNG, it loses the lens profile, after importing such a file to another computer, or even again in my Lightroom, there are no Panasonic profiles at all. Rolled back to 11.3.1 and it works fine. Any ideas how to fix it or is it a bug in the new version?

In Lightroom Classic's Print Module, the Page Setup pop-up menu that lets me select a paper page size no longer changes when I switch printers. This used to work (I have been printing in LR for years) and I can still print to the printers. I just can't tell LR the page size I want.   I have no issues in other apps (PS, QImage, etc) which correctly show me the list of supported pages sizes. Indeed, LR seems to know about the options as the "Printer..." dialog has a Scale to fit paper size option that is correct. It just looks like the Page Setup list of print sizes never gets updated and stays on the "Any Printer" default list.   I'm on a recent Macbook Pro M3 running current Sonoma (14.4) , latest version of LR (I tried deleting, re-installing, installing prio version, rebooting laptop, updated print driver, and anything else I could think of to no avail). Main printer I use is a Canon Pro 100, but same issue on another printer. And as I say, PS (etc) has no issues.   I

Found a bug with changing ratings with a rating filter applied in a Publish service collection: If I first set a filter to show all 2 star photos or >2 stars then change any photo to 1 star the selected photo auto-advances two photos ahead of the original selection instead of just one (auto advance is turned off) Example: If I have Photo1, Photo2, Photo3, Photo4, Photo5 etc showing as the filtered photos in the grid and I change Photo2 to be only 1 star it is expected that Photo2 would disappear and then Photo3 would become the new selected photo. But it moves to Photo4 instead. This behaviour is only a problem in Publish Service collections. Using LR5.4 with Win7. -- Bruce

The LR 14.0 SDK is missing documentation for:   - progressScope:done (dismissalStrategy)  The parameter "dismissalStrategy" was added (and its name documented) but there is no description of its type or meaning.   - These methods were added to LrDevelopController but not documented: countAllSpots deleteSelectedSpot deleteSelectedVariation getAllSpots getRemovePanelPreferences getSelectedSpotIndex getSelectedSpotParams getSelectedSpotType goToEyeCorrection goToRemove gotoNextVariation gotoPreviousVariation moveSelectedSpot refreshSelectedSpot setRemovePanelPreferences setSelectedSpotIndex setSelectedSpotParams setSelectedSpotType