Lightroom Classic

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

In LRC, I have many hierarchical keyword structures, amongst which are locations, i.e. Country/State/City and in some cases location or street name.  Since version 15.4.1, LRC deletes upper level location keywords (Country and State, or when there's a fourth level then it deletes the city too) after a photo has been synced to the cloud. The keywords still exist in the cloud. I have checked other hierarchical trees and the keywords are all syncing correctly. If I reenter the locations the save metadata to file, the keywords once again disappear.I'm running LRC 15.4.1 on a Windows 11 Pro computer with Admin rights. Lightroom, catalog and photos are all on (separate) local nvme ssds. Plenty of space, plenty of speed. 

I have encountered an instance where a wide gamut orange colour appears desaturated in HDR editing mode. I have the uploaded output PQ HDR AVIF files to https://andrewkeyanzhe.github.io/posts/Lightroom_vs_darktable/ for comparison. My website serves the uncompressed HDR AVIF files, so you should be able to see the difference on an HDR capable device and browser (e.g. Macbook Pro with XDR display with Google Chrome)   The camera used is the Panasonic Lumix S5ii   Details:  Version of the app - Lightroom 14.2 (Camera Raw 17.2), Lightroom mobile v. 10.3.1 71F6C8/202 Platform and OS version - Macbook Pro 16 M1 Pro, macOS Sequoia, iPhone 14 Pro Max, iOS 17.5.1 Basic steps to reproduce the problem - Download the raw file https://drive.google.com/drive/u/0/folders/1YIhkxHvp77HHTaanyFJ5LXX28jH74Rau , open in Lightroom, turn on HDR editing mode, increase the exposure by 3.4 stops so it matches https://youtu.be/0FYjApop7Mk?si=S-cXCX-0hyAvsT

The smart-collection criterion Needs AI Update doesn’t identify photos with masking errors. To reproduce in LR 15.4.1 / Mac OS 25.4.1: 1. Download and open the attached catalog “needs-ai-update-bug.zip”. 2. Observe that the photo Error.jpg has a Sky mask flagged as an error, “Couldn’t find a sky to select”:  3. In Library, observe that the Library Filter column Needs AI Update doesn’t include an “Error” item identifying that photo, and that the smart-collection “_Needs AI Update = Error” doesn’t include that photo: 

Hi everyone,I'm having an issue with the latest version of Lightroom CC on a MacBook M5 Pro running macOS Tahoe 26.5.1. (I was experiencing the same problem on 26.5 and decided to update hoping it would fix it, but unfortunately it didn't.)Since this morning, it's been impossible to to use Noise Reduction, even though my internet connection is working perfectly. I've already updated both Lightroom CC and macOS, cleared the cache, and optimized the catalog, but I keep getting this error screen whenever I try to use Noise Reduction.Has anyone experienced the same issue or knows how to fix it? Any help would be greatly appreciated. Thanks! 🙏 

EnvironmentAdobe Lightroom Classic 15.4 Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() does not consistently receive keyboard input.The same floating dialog implementation exhibits two different behaviors depending on the SDK calls executed immediately before the dialog is created.In one case, keyboard input is routed to the floating dialog immediately after opening.In the other case, keyboard input remains with Lightroom, allowing Lightroom keyboard shortcuts to continue working while the floating dialog is visible.A complete standalone reproducer plugin is attached. Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run via File > Plug-in Extras > Floating Dialog Keyboard Input Reproduction. Choose one of the two test configurations: Plugin dialog receives keyboard input Lightroom receives keyboard input Press the Tab key.A complete standalone reproducer pl

 EnvironmentAdobe Lightroom Classic 15.4 (also observed in earlier versions) Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() becomes the active window, but no control initially receives keyboard focus.As a result, standard keyboard interaction is unavailable immediately after the dialog opens. Pressing Enter, Esc, Space, or Shift+Tab has no effect. Keyboard navigation only begins after pressing Tab once (or after clicking any control with the mouse).The same reproducer behaves differently on macOS, where the first control immediately participates in keyboard navigation.Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run File > Plug-in Extras > Floating Dialog Keyboard Focus Reproduction Without using the mouse, press the following keys in order: Enter Esc Space Shift+Tab Finally, press Tab.A complete standalone reproducer plugin is attached. Expected Resu

[This bug report was originally posted on 1/26/2019 in the old feedback forum, but it never got transferred here. See the attached email message.]   In LR 14.3.1 / Windows 11, when LR is in  Window > Screen Mode > Full Screen, floating dialogs always appear hidden in back of the main LR window, and calling the toFront() function has no effect. This prevents my Any Crop and Any Filter plugins from being used in Full Screen mode. This doesn't occur in the other screen modes, nor does it occur on Mac OS 15.5.   This simple plugin demonstrates the bug:https://www.dropbox.com/s/6d1l3llo5dwzzuw/floatingfullscreenbug.lrdevplugin.zip?dl=0 Simply invoke Library > Plug-in Extras > Floating Dialog in the various Screen Modes. The command executes this simple code: LrDialogs.presentFloatingDialog (_PLUGIN, { title = "Floating Fullscreen Bug", contents = f:push_button {title = "Push Me"}, onShow = showErrors (function (t) LrTasks.startAsyncTask (s

When I want to skip through hundreds or thousands of photos in Lightroom Classic (Version 15.0.1) in the film strip I mostly get this very annoying problem: after holding the arrow key to the right or left for a few seconds it doesn't stop anymore to speed through the images though I'm no more holding the arrow key. Sometimes it's going on for "just" a couple of hundred further photos and sometimes even through thousands of photos until the very last photo in the strip. I can't even stop it.This first started three months ago when I updated on a new MacBook. On my old Macbook this never happened in years. Does someone got an Idea to fix this bug?

Installed this and my tethered camera setup no longer works.  It appears to work as before, but no images are transferred.  Canon R1, Windows 11.  Anyone else having tethering issues?

On macOS Tahoe, Lightroom Classic overshoots when navigating with arrow keys on MacBook Pro models with ProMotion enabled. Setting the display refresh rate to 60 Hz immediately eliminates the issue. Reproduced on both M1 Max and M5 Max with fresh macOS and Lightroom installations. Does not occur on an M4 MacBook Air (60 Hz display).

This is core to my workflow, an absolutely necessary feature I use every single time I’m editing photos. In the Develop Module, under let’s say the “Basic” adjustments panel, one should be able to adjust values (such as Exposure, Contrast, Highlights, Shadows, Whites, Blacks, etc.) while hovering the mouse cursor over a section of the photo (in the Loupe View) and see RGB values changing under the histogram.In the latest version, the RGB values are no longer displayed under the histogram while those values are being adjusted. For example, I click the number next to the ‘Highlights’ slider and move my cursor over to a white part of the image. When I press the up arrow on my keyboard to increase the value of that number, the RGB values under the histogram *should* be displayed and also increasing. Instead, they are not displayed at all.I have downgraded to the previous version and the program’s behavior returns to expected. This is a brand new computer, fresh win 11, AMD Ryzen 7 7700X; 3

Lightroom Classic version 15.4Mac OS 26, Version 26.5.1Mac Studio M4 MaxPrior to the latest upgrade to Lightroom Classic I was backing up my catalog to my Synology drive. I now get the unable to write to drive error, check permissions and available space on the drives. I can backup the file locally on my MAC and then copy that over to the Synology drive. So it does not seem as though permissions is the issue. Have 16TB of storage on the Synology and 782 GB free on a 1 TB SSD on the Mac. Only started when after the latest upgrade to Lightroom Classic.

Description of IssueLR Classic fails to import TIFF files with deflate/zip compression.Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.3 [ 202604090947-8f3672ed ]License: Creative CloudLanguage setting: en-NLOperating system: Mac OS 26Version: 26.3.1 [25D2128]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213OS Version Numbermacos Tahoe 26.3.1 (25D2128) Camera Model (sometimes necessary)n/aStep-by-step Reproduction Instructions (in precise terms, please)Import the following sample image in LR classic:https://drive.google.com/file/d/14eazJOmOZ1XALHYXqae16sXBuZf9bZ_d/view?usp=sharingThe Expected ResultImage imports correctlyThe Actual ResultErrors: “preview unavailable for this file” and “Could not read preview”. No image is shown.Further details:Hi, developer of PTGui here. PTGui now outputs TIFF images with deflate/zip compression by default. It’s fast and efficient and th

I start with an edited version (lightroom adjustments only) of a photo in lightroom. I make a copy of it and then click reset on the new copy. This copy is essentially no modifications at this point. I then edit that copy in photoshop. When I am done editing in PS, I save it. I then open that PS-modified version in lightroom and paste ALL settings I have copied from the original to this new TIFF version. I expect the changes to work but it looks wrong. I notice the REMOVED tool item masks are strange. It looks like the REMOVE masks in the version that I pasted to are 90 degrees rotated - clockwise. Basically, copy/paste of masks does not work from a raw file to a tiff version. It’s like PS messed up the orientation indicator or something and LR got confused?

Lightroom Classic 15.0.1, Windows 25H2 26200.7171, Nvidia GeForce RTX 3060 (32.0.15.7602)   I took a photo of a bunch of fish swimming around behind a glass window. I wanted to use both reflection removal and AI Denoise. According to this page, I perform the AI Denoise first.   Here is the photo I used: https://www.dropbox.com/scl/fi/2zqjndbvb4i2mcwqqrgku/PMC_3135.NEF?rlkey=gq1w1mwdiu86oab9avto3wj9i&st=bi4tyj72&dl=0   Here is a screen capture of the unedited version of this photo, you can see reflections as well as noise       Here are the steps I followed:   1. AI Denoise, slider at 50, works as expected, noise is reduced.  2. Distraction Removal: Reflection, slider at 100. Reflection is not removed. Here is a screen capture after both steps, the noise reduction remains effective, but the reflection is not removed.     Also, please note that if I perform the steps in the opposite order (Remove Reflections first, the refl

EnvironmentLightroom Classic 15.4.1 macOS 26.5.2 Wacom Intuos PT S CTH-490 Wacom Driver 6.4.9Steps to reproduceOpen Develop module. Select Masking → Brush. Paint using a pressure-sensitive Wacom pen. Vary pen pressure.Expected resultBrush size/pressure responds to pen pressure as in Lightroom Classic 15.3.1.Actual resultPen pressure is ignored. The brush behaves as if a mouse is used.Additional informationDowngrading to Lightroom Classic 15.3.1 immediately restores pen pressure functionality using the same hardware, driver and operating system.No changes were made to the Wacom driver, hardware or macOS. Only the Lightroom Classic version changed.Control test: The same Wacom tablet and pen work correctly in Photoshop on the same Mac. Pen pressure affects brush size as expected. The issue only occurs in Lightroom Classic 15.4.1.

The red-x Reject badges persist on thumbnails in the filmstrip even when all the Select and Reject checkboxes in Assisted Culling are unchecked.  To reproduce on LR 15.4.1 / Mac OS 26.4.1: 1. Download and open the attached catalog. 2. In the Assisted Culling panel, uncheck all the checkboxes. Observe that the red-x badges still appear on the filmstrip thumbnails:  I haven’t discovered any way to make them disappear, including by deleting the Helper.lrdata file.

Lightroom Classiv v15.3 (on Mac OS Tahoe) has a problem importing photo files that have a pipe symbol - a | symbol - in the XMP field dc:subject.Lightroom apparently has a problem interpreting the pipe symbol, and then hangs, seemingly indefinitely until the import is cancelled, while showing a high level of CPU usage. This hanging seems to take place at the end of the import process for this photo.The pipe symbol is used by Lightroom to separate levels in the keyword hierarchy within the Hierarchical Subject XMP field.  Having pipe symbols also within the keywords doesn’t seem to be a problem with the Hierarchical Subject field - at least it doesn’t interfere with importing.  Also the pipe symbols in the Weighted Flat Subject field don’t seem to cause a problem with imports.Attached is a sample file that hangs when being imported into Lightroom.  Of course, a problem file causes a batch import of photos to fail, with some number of files correctly importing until Lightroom does to pro

When multiple videos are selected, Edit Capture Time incorrectly shows the message for a single photo selected, rather than a message that indicates the capture times of the other videos will be adjusted by the same amount as the first: When multiple photos and at least one video is selected, the message incorrectly states that videos will not be adjusted: But in these cases, the problem is just with the message being displayed. Clicking Change All correctly adjusts the capture times of the other videos by the same amount as the most-selected photo/video. Tested on LR 15.4.1 / Mac OS 26.4.1.

The update to the Generative Remove AI model in Lightroom Classic 14.5 has ruined it, as it now changes elements outside the painted mask, making it more or less unusable in many situations.

Synchronize Folder > Scan For Metadata Updates can cause frequent spurious metadata conflicts for TIFFs that are stored on NAS.  Over the years many people have reported spurious metadata conflicts that Adobe hasn't been able to track down, and many of those reports involve photos stored on NAS.  Here's a recent report:https://feedback.photoshop.com/photoshop_family/topics/before_after_comparison_of_metadata_conflicts...While the particular use case here may not be that common, it may provide a reproducible test case that points to the bug (likely a race condition) underlying all those other persistent reports.Here are the steps that consistently produce the spurious conflicts in my configuration:1. Connect to a network volume on a 2013 iMac running MacOS 10.14.6. The volume is mounted with SMB 3.0.2.  2. Place 4 1800 x 1200 TIFFs (about 13 MB each) in a folder on the network volume.3. Import them with Add into a LR 9.0 catalog running on a 2019 Macbook Pro

I am so SAD!  I have bought a new Macbook M4 Max However, Lightroom CC lastest version, cant EXPORT slideshows as videos! the progress bar is stopped at nearly 10% position. No matter if I wait several hours it won't move any progress = I Cant export slideshow as Video   I always used this function, for a few years, day by days   I uninstalled the LR and tried reinstalling it, but it still failed. Does anybody have the same issue?I wonder if it is a problem related to M4 chips. Please kindly help and fix please!

This bug causes DATA LOSS.Description of Issue After viewing duplicates using the new LR15.4 Find and manage duplicate photos feature, and marking some photos (either Original or Duplicate) as Rejected, the use of the “delete rejected photos” function (e.g., through the keystroke cmd-Delete) will cause all photos to be deleted from disk and from the catalog, not just those marked for rejection. Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.4 [ 202606101834-493069d4 ] OS Version Number ​​​​​​​MacOS 26.5.1 (25F80) Step-by-step Reproduction Instructions ​​​​​​​add a photo, and a duplicate of that photo, to a LR catalog. switch to Duplicates view; the two photos should appear in a stack. mark one of the two photos Rejected. cmd-Delete to delete rejected photos confirm. The Expected Result ​​​​​​​only the Rejected photos disappear from disk and the catalog. The Actual Result ​​​​​​​all the photos - even those not marked Rejected, disappear fr