Lightroom Classic

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.

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.

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. 

EnvironmentAdobe Lightroom Classic 15.3 Lightroom SDK macOS 26.5.1 Standalone reproducer plugin attachedSummaryA floating dialog opened via `presentFloatingDialog()` does not reopen on the second screen. When the dialog is closed while positioned on a second monitor and then reopened, it always appears on the primary screen instead. Steps to Reproduce1. Connect a second monitor.2. Install the attached reproducer plugin via File > Plug-in Manager > Add.3. Run via Library > Plug-in Extras > Run Second Screen Dialog Bug Repro.4. Choose "Test Floating Dialog".5. Drag the dialog to the second screen.6. Click "Close and Reopen".A complete standalone reproducer plugin is attached. Expected ResultThe dialog reopens on the second screen at the position where it was last closed. Actual ResultThe dialog reopens on the primary screen. The position on the primary screen mirrors the saved coordinates — for example, a dialog closed at the top-left of the second screen reopens at the top-l

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.

Lightroom Classic Version 12.1  OS Name: Microsoft Windows 11 Home Version 10.0.22621 Build 22621   Importing a .MOV file from a NAS drive into lightroom .MOV file originally taken on an i-phone 12 720x960 0.7 MP Imported video is rotated by 180 - so upside down .MOV file originally taken on an i-phone 12 960x720 0.7 MP Video is imported correctly

Sync Settings with Upright Transforms checked doesn’t always check Copy automatically, as was intended by the undocumented change in LR 15.0.  To reproduce on LR 15.3 / Mac OS 26.2 (see the attached screen recording): 1. Save the attached file Upright-Transforms.lrtemplate (created in LR 14) to the Copy Paste Subsets subfolder of the Lightroom settings folder.  Restart LR. 2. Select two photos and do Sync Settings. Click Check None and click Synchronize. 3. Do Sync Settings again, select the subset Upright Transforms, and observe that Crop is checked (correct).  Click Synchronize. 4. Do Sync Settings again.Observe that the subset Upright Transforms is selected (correct) but that Crop is unchecked (incorrect). When you click Synchronize, the Crop is copied, even though it is unchecked.

Then I apply AI denoise, in LR Classic 15.3 it does it in the background which I really like, however once I apply it to let’s say 100 pictures, and start editing the ones that already editable, it is stopping at the last few images. It is toally random where it is stopping but all the AI denoise remains in a stuck position and I can’t edit those photos unless I restart LR Classic. Sometimes these are images that already have some AI denoise on them, I just don’t bother to select the ones that doesn’t have it, so I paste the settings to all. And usually it is stuck it one point of the process.It only goes through the process if I don’t start editing any other photos, just wait for the whole process to finish. Lightroom Classic version 15.3Mac OS Sequoia 15.7.5Maxed out M1 Max MacBook Pro with Apple Studio Display 5K.

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.

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

Recipe:  When the secondary window is in grid view, it doesn’t always respond to the keyboard shortcuts “f”, Escape, or Shift+g.  To reproduce on LR 15.3 / Mac OS 26.4.1, follow these precise steps (see the attached screen recording): 1. In LR, go to Grid view, close the secondary display window if it’s open, and do Window > Screen Mode > Normal 2. Restart LR. 3. Do the menu command Window > Secondary Display > Grid to open the secondary window in Grid view. 4. Select a thumbnail in the secondary window and type “f”. Observe that nothing happens (incorrect). 5. Do the menu command Window > Screen Mode > Full Screen Preview (the command invoked by the shortcut “f”) and observe that the image is displayed in full screen. 6. Type Escape to exit full screen preview and observe nothing happens (incorrect). Typing “g” and Shift+g also have no effect (incorrect).   7. Type Cmd + Tab and then Tab to switch to an app other than LR. LR is now no longer in full screen mode. 8. C

Description of Issue: The eye icon on the Remove panel stays greyed out.Lightroom Classic Version Number: 15.4 (June 2026)OS Version Number: Windows 11 25H2 (up to date)Camera Model: Canon R6 mk2Step-by-step Reproduction Instructions: In the develop module use the remove/heal/clone on some part of the image.The Expected Result: The eye icon should become active so you can hide the edits.The Actual Result: The eye icon stays greyed out.Image below shows the result:  

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!

System: Mac M1 Air 16gb/512gb OS: Sonoma 14.3.1 LRC Version: 13.1 Release ---------------   Three Issues: 1) I have a preset folder with six custom presets.  When doing multiple exports using the batch export feature, LRC often doesn't launch the same number of processes as there are presets selected.  I select 6 presets and it will only do 4 sometimes, 5 others.  Sometimes it does all 6.  I have to examine the export folder, see which ones it missed, and go back and re-export the ones it didn't do.  Annoying.   Potential Fix:  If LRC can't do all of the processes because of system limitations (I don't know why on a Mac M1 that would be the case), at least inform the user which ones are being done and which are not.  Perhaps a loop to do sets consecutively with proper UI notification would be a good approach.   2) When doing multiple exports, a dialog comes up for each process, "Preparing to export".   "number of processes - 1

[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

Hello: I just updated to the 15.0 release and I think I just discovered a bug. When I click Edit Capture Time via the Metadata tab, whatever time I enter is one hour off from the time that shows up in the EXIF data panel (and how it sorts the photo if "Capture Time" is used to sort the library); therefore to get the EXIF information to show up correctly, I must purposely enter the information one hour behind the time I want it to be (see screenshot where I want 5:31pm to be the edited time, but I must enter 4:31pm to get 5:31pm).  -- Scott, MacBook Pro, Apple M3 Pro chip, macOS Sequoia 15.6.1.

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

Lightroom bug - hit a folder limit and unable to select the newly imported folder.452497 photographs across many drives in one catalog.The S drive has 214341 photos. It's the largest drive and so had many more folders than the previous drives.S:\Master Photos\ contains ~1633 folders. I know that's a lot but that is how her filing system was started. Those are the sequential numbers from 2220 - 3853 but there may be a sub folder or two or deleted folder in there so that's why the number is ~ approximate.Folders are labeled "sequential number"-"date" so 3853-20150316Adding one more folder caused Lightroom 4 to not allow the last folder to be clicked on and not show any images. The T:\ drive (offline, collapsed and below the S:\ drive) was collapsed and the label was overlaid on top of the "Collections" section label. Updated to latest version of Lightroom 5 via her new cloud account, had it rebuild the catalog and the same problem occurred.Created a sub folder S:\Master Photos\2012 and m

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

Lightroom Classic Version15.4.1macOSTahoe 26.5.2HardwareMacBook Pro (Apple Silicon)DescriptionExport as Catalog consistently fails when the destination is an external exFAT SSD.After several minutes Lightroom displays:“An unknown error occurred while exporting the catalog.”The partially created export folder is then deleted.The identical export succeeds immediately when the destination is the internal APFS SSD.ReproductionOpen any Lightroom catalog. Choose File → Export as Catalog. Select an external exFAT SSD. Export with or without negatives. Wait. Lightroom reports “Unknown error occurred while exporting the catalog.”ExpectedCatalog exports successfully.ActualGeneric error.Export folder deleted.Reproduces onSamsung T9 (exFAT) SanDisk Extreme SSD (exFAT)Does NOT reproduce when destination isInternal APFS SSD.The same catalog (approximately 415 GB including negatives) exports successfully to the internal APFS SSD in a few seconds. The resulting exported folder can then be copied to th

In the Send Book to Blurb function first the pages are rendered. Thereafter the upload takes place, during that second part the upload is very often stopped with this pop-up:Error appearing many timesThe pop-up shows very often, like dozens of time (100+ page book, 300+ images). The interval between messages does not seem to be fixed.This is the behavior of machine network while sending (between the errors):Data sent while continuingUnknown if this is normal…The progress bar does continue to go forward, so progress seems to happen between the errors. However, as too many errors are given no full book is uploaded currently.The screenshot is using a cable connection (from machine to router), using WIFI gives the same.This is behavior is observed in the LrC 15.3 and 15.2.1 and previously in early 2025 (LrC version unknown).Machine is Microsoft Surface, current version of Windows, ARM64; further info in attached file.

Environment Adobe Lightroom Classic 15.3 Lightroom SDK Windows 11 Standalone Lua script attached SummaryTransparent PNG images displayed in an overlapping layout do not reveal the underlying image on Windows.Instead, transparent pixels are rendered using the Lightroom dialog background color, resulting in visible rectangular artifacts around the overlay image.The same code behaves correctly on macOS. Steps to Reproduce Create an overlapping view (place = "overlapping"). Add a background image (blue PNG). Add a second image consisting of a 45×45 RGBA PNG containing a single red pixel and otherwise fully transparent pixels. Position the overlay image using a child container (f:row with margins). Display the dialog. A complete standalone reproducer is attached. Expected ResultOnly the red pixel should be visible.The transparent pixels of the overlay image should reveal the underlying blue image. Actual Result on WindowsA visible 45×45 rectangle appears around the red pixel.T

When importing Leica M11 DNG files using Adobe Default (as shown in the Preferences / Presets -- Global setting) Adobe Standard is applied as the Profile instead of Adobe Color.  When I create and specify a Preset which specifically uses Adobe Color as the Profile, Adobe Standard is still applied.  If I specify to use Camera Setting, then the embedded M11 profile is correctly applied.  As a work-around,  I can indeed force the Adobe Color profile to be applied if I specify it as the Apply During Import - Development Setting (right-hand panel when importing) and select under the Defaults presets - Adobe Color + Lens or similar. [Moved to Color Management by moderator authority]

In Lightroom it is impossible to edit a photo as much as we want or need, using Masking regardless of the hardware you have.EXPLANATION Let's say you want to edit a photo with Masking to your heart's content OR because you need to change many aspect of the photo.Logic tells you "we have Masking so obviously it's possible to do masking safely and as much as I want"Reality is that in Lightroom Classic there is an "upper limit" of local edits that we can have on a photo: once we reach that "upper limit" the photo will be be reset.So in Lr it's not possible to sue Masking as much as we want/need.Usually if you have lots, lots of edits on an image other editing software struggle and get progressively slower and slower (if one has powerful hardware generally slowdowns don't happen or appear later) but in LR a photo can reach a point where it's no longer editable and it will be reset NO MATTER THE HARDWARE YOU HAVE. All Masking tools (gradients, sp

OS: Windows 11LrC VERSION: 14.5A couple of days ago I upgrade to v14.5.As for every update, I regurlay empty cache, optimise catalog, remove all previews and generate new standard ones (also, I wanted to test how was was the new option to use GPU for generating previews).Never had a problem with this workflow.After previews generation process was completed (1h 30m for 29.000 files, 23.000 jpegs and 6.000 raws) I got an error: for 21 RAWs the preview could not be generated. Looking in the catalog at those files, I realised they have an exclamation mark on a dark circle: this is not the missing photo mark. If I click on the exclamation mark, I see error "Lightroom has encountered problems reading this photo, you are not allowed to edit this image. " Yet, I can still enter develop module and edit the photos without any problem: the editing history is there, I can zoom in at 100% (generating the 1:1 preview), I can change sliders, export... Everything... (PS: I do not use smart previe