Bug Reports

LrView.bind (key) creates a non-working binding when "key" contains a period. To reproduce, install this plugin: https://www.dropbox.com/s/fhx9521z9re47ro/bind-bug.lrdevplugin.2022.01.16.zip?dl=0    and then do File > Plug-in Extras > Bind Bug. That will produce this window:   The first checkbox should be unchecked (white), not in the mixed state (hyphen).  Tested on LR 11.1 / Mac OS 11.6.2.   Just one more SDK bug to work around.   Here's the script for the Bind Bug command:   local LrBinding = import "LrBinding" local LrDialogs = import "LrDialogs" local LrFunctionContext = import "LrFunctionContext" local LrView = import "LrView" local bind = LrView.bind local f = LrView.osFactory() local key1 = "x.y" local key2 = "x_y" LrFunctionContext.callWithContext ("main", function (context) local prop = LrBinding.makePropertyTable (context) prop [key1], prop [key2] = false, false assert (prop [key1] == false) assert (prop [key2] ==

LrLogger adds an extra "\r" to each "\r\n" contained in logged strings on Windows. Tested on LR 14.5.1.   1. Save the attached file "logger-bug.txt" to the LR Scripts folder.  That script contains: logger = import "LrLogger" ("MyLog") logger:enable ("logfile") logger:info ("line 1\r\nline 2\r\n")   2. Restart LR and execute the script.   3. Observe that %LOCALAPPDATA%\Adobe\Lightroom\Logs\LrClassicLogs\MyLog.log contains "line 1\r\r\nline 2\r\r\n" (incorrect) instead of "line 1\r\nline 2\r\n": $ od -c MyLog.log 0000000 0 9 / 2 3 / 2 0 2 5 1 6 : 4 9 0000020 : 4 4 I N F O \t l i n e 1 \r 0000040 \r \n l i n e 2 \r \r \n \0 \r \n  

Hi all,   I am hoping someone can help.  I am having issues dragging-and-dropping a photo or group of photos into a collection.  Any time I attempt to do this, lightroom classic crashes.  I am running the updated version of lightroom 14.5.1.  OS is Windows 11.   I attached the error xml as well below.  Has anyone run into this or have any suggestions?    I have tried the following and issue persists: 1. Restart computer / lightroom 2. Restore default lightroom settings / preferences 3. Update GPU driver 4. Disable GPU acceleration 5. Create new lightroom catalog 6. Revert to prior versions of lightroom.  I have tried 14.5 and 14.4 so far.   Thanks! Andrew        

App Version: Lightroom Classic 14.2 OS: macOS Sequoia 15.3.1   I would really appreciate some help with this. I'm not sure if it's even a bug or if I'm just doing something wrong. I just noticed this issue on some recent images from a recent trip when trying to export. When exporting from a RAW file with the correct lens profile assigned, the exported file doesn't appear corrrected as I am seeing it in the Develop tab. Everything looks great in the Develop tab when I view the image as ‘Fit’ in the window. The moment I zoom in on the image in the Develop tab, the distortion is incorrect; the same way it appears in the exported file. Here are a few images for reference. The first image is what I want/expect; all the lines are nice and straight.     Additionally, it all looks fine when previewing it in the develop tab but if I switch to the Library tab, the distortion appears like the image below. This is what I get when I export:     And here's the image with n

Nice to meet you. When I try to tether the Leica SL2 with Lightroom classic, Lightroom classic crashes. When I turn on the SL2, it crashes the moment Lightroom recognizes the SL2.   Restarting the Mac and SL2 repeatedly does not improve the situation. The OS is as follows. Leica SL2 Firmware 6.2.0 MacBook Pro 14-inch 2021 Apple M1 Pro Memory 32GB OS Sequoia 15.1 Lightroom classic Version 14.4 By the way, I was able to shoot tethered without any problems with Lightroom classic 13. If you know of any solutions, please let me know. Thank you in advance.  

I used to use the "Text" option in the Library Filter in Grid mode to select photographs that needed renaming. I used the "Filename" "Starts With" option. It used to filter only files whose file name started with the text that I put into the search box. Now it appears to find any file that has the text in the file name, not just at the beginning. It seems to be looking at the beginning of every word in the file name. I think I first noticed this when Version 3 came out, but it might have been before that.

Hello everybody, I want to upload a photobook to Blurb, but while uploading it stopped by half upload saying 'An internal error occurred, ?:0: attempt to perform arithmetic on field 'chunk_size' (a nil value)'. How can I upload my photobook? Thanks for your support. Guenther

Right-clicking a mask and doing Intersect Mask With causes the three-dot menus and eyeball icons to stop appearing when you hover over any mask or mask component. The bug recipe below faithfully replicates a common way of configuring the LR UI. With this config, it's very easy for the bug to occur, and, while it's a simple bug with a now-known trivial workaround, it is quite annoying (as it apparently was to Conrad).   To reproduce on a virgin LR 14.5.1 / Mac OS 15.6.1 (both freshly installed in a virtual machine):   1. Download and open this small catalog: https://www.dropbox.com/scl/fi/okzrplm6igsst4an71xpm/intersect-bug.2025-09-05.zip?rlkey=xhxs6es9e56wfi83t3ol8qqob&dl=0   2. Click the window's green button to fill the screen with LR.   3. Take one of the photos into Develop and create a mask. If the Masks panel isn't docked in the main Develop column, dock it.   4. Click the three-dot men in the lower right corner of the Masks panel to ensure you h

Bonjour,  Je viens vers vous car je suis au bout des solutions que j'ai pu explorer. J'ai un problème depuis l'installation de Lightroom sur mon ordinateur (V 14.5.1). Sur certaines photos, dès que je veux utiliser la détection de personnes, le logiciel crash. Tout mes pilotes sont à jour.J'ai désactivé l'utilisation du GPU pour le traitement de l'image, ce qui résout le problème. Cependant, je souhaitais savoir si cela réduisait grandement l'impact sur les performances de l'application et s'il y a un moyen de résoudre ce problème sans limiter l'utilisation du GPU.    Configuration de l'appareil portable :  - Intel Core Ultra 9 285H - Intel ARC 140T - 32Go Ram   Cordialement, Tristan.

LrC 14.3 Release Enhance no longer allows me to use Enhance Super-Resolution on TIFF files. Before upgrading to 14.3, I was able to convert a DNG file to TIFF and then apply Enhance Super-Resolution to the TIFF file.  What changed? Was that a "bug" that was fixed, because I really liked that "bug".

After upgrading to 14.5, I selected a group of photos for review. When I deleted one of the highlighted photos, the current photo became the first photo in the group instead of the next photo in the group when "Filter based on flag status (Unflagged Photos Only)" is active. I've restarted Lightroom Classic a couple of times and the behavior persists. I'm running on a Macbook 16 M1 Max with 64MB of memory Sequoia 15.5

Hello, I just updated LR Classic from v14.4 to v14.5 on Windows 10.I’d like to report a major bug: It is impossible to create a new catalog from within the application (Menu > File > New Catalog). It is impossible to switch catalogs (except by clicking directly on the catalog file to open the application). The window App closes, then nothing happens for several minutes (Task Manager shows a "zombie" Adobe process still running) → I have to kill It to reOpen the app. I had to reinstall version 14.4 and everything is now working normally again.

Hi everybody!I have been using Lightroom for over 10 years. On my old laptop with Intel Core i7 4720HQ, NVIDIA GeForce GTX 960M and 16 GB RAM, the screen was always slow when I zoomed in or out of the LR window and you could clearly see the individual parts of LR building up.Now I have a brand new PC: AMD Ryzen 9950x, NVIDIA RTX 5070, 96 GB RAM. I assumed that everything would just load smoothly. It does, but not with LR Classic! GPU is activated in the settings of LR. Why is that?  

Since upgrading to 14.5 today, the "down arrow" key in Compare mode has regressed.  Very frustrating, completely disrupts my preferred workflow.   Open a folder with >few images Expand the film strip (so you can see the selection later) "C" for compare mode (Not broken - demo:) Use Right and Left arrow keys to advance the candidate (Not broken - demo:) Use the Up arrow key to promote the candidate Use the Down arrow key to swap selection/candidate - THEN: Press Right arrow key twice   Actual behavior: 3 photos are selected (wrong behavior) Henceforth, Left/Right arrow keys can only toggle between the 3 selected photos. (Compare mode only works when 2 photos are selected, as has always been the case) Up arrow key no longer work at all ("Bonk" sound plays indicating invalid input, no change to selection) Can't continue to use Compare mode   Workaround: you're stuck until you clear the selection (Cmd+D), or deselect all but the primary selection (Cmd+Shift+D). &

The Save Metadata To File command doesn't always update a photo's metadata status to indicate it is Up To Date. To reproduce:   1. Download and open this catalog in LR: https://www.dropbox.com/scl/fi/jokv9a8pfsdc2z0jrqlu5/save-metadat-bug.2024.05.25.zip?rlkey=z833g3ek2gghxouxzx3xx62jb&dl=0   2. In Library View > View Options > Grid View, check Cell Icons > Unsaved Metadata.   3. In the Library Filter bar, open the Metadata browser with the column Metadata Status.   4. Observe that all 32 photos have metadata status Has Been Changed as indicated in the Metadata browser and on the thumbnails.   5. Select all the photos and do Metadata > Save Metadata To File.   6. Observe that 32 photos remain with status Has Been Changed, and Finder / File Explorer show the files or their .xmp sidecards have their Date Modified set to "now", indicating that LR wrote the files (but I haven't tested if they've been written correctly).   Tested on LR 13.3

After updating LrC to 14.4, and then using super resolution on a RAW file, then exporting it to Photoshop, Photoshop starts, opens, but no file appears and no menu items or tools work in Photoshop.   Task Manager in Windows  is necessary to close Photoshop.  The same procedure is applied to the same RAW file, after resetting the RAW file, but without super resolution or denoise being applied.   The RAW file is sent to Photoshop, Photoshop opens and works as usual.      These procedures were applied to several other RAw files with and without super resolution applied.   The results in Photoshop were repeated as above.   Use super resolution on a file in LrC then go to Photoshop - Photoshop will not function.     Solution : stay with LrC 14.3.1 if you wish to use Denoise that works.  

Renaming a develop preset from within Favorites incorrectly moves the preset from the User Presets group into a second Favorites group.   To reproduce on LR 14.3.1 / Mac OS 15.5:   1. In the Develop Presets panel, create a new preset named Test.   2. Right-click Test and do Add To Favorites.   3. In the Favorites group, right-click Test, do Rename, and rename it to Test 2.   4. Observe there's now a second group named Favorites containing Test 2, and Test 2 no longer occurs under User Presets (incorrect).   5. Right-click Test 2, do Show In Finder, and edit it's .xmp file. Observe that it records the group as "Favorites" (incorrect): <crs:Group> <rdf:Alt> <rdf:li xml:lang="x-default">Favorites</rdf:li> </rdf:Alt> </crs:Group>   6. Drag the second instance of Test 2 back into User Presets, and the second bogus Favorites group disappears.

When a raw file is imported with the option Copy As DNG and a metadata preset is applied during import, the values set by the preset disappear from the metadata panel after a couple of seconds. A workaround is to set the option Catalog Settings > Automatically Write Changes Into XMP.     Originally reported by another person: https://www.lightroomqueen.com/community/threads/copyrights-disappear-during-dng-conversion.53023/    To reproduce on LR 14.4 / Mac OS 15.5 (see the attached screen recording):   1. Download and open this catalog: https://www.dropbox.com/scl/fi/97ztsg16ekxc2h297lv4w/copy-dng-metadata.2025-06-23.zip?rlkey=9iqixpsthk7c7e3ybbtvlboh1&dl=0   2. Define a Metadata preset "Copy As DNG" with the fields:   Caption: Hello world Copyright Status: Copyrighted. Copyright: 2025 Joe Cool   The preset's .lrtemplate is in the catalog folder.   3. Verify Catalog Settings > Automatically Write Changes Into XMP is unchecked.

The Nikon Z5 II Raw Files (NEF Files) are having a known probem in LR Classic, including the very latest release 14.4. Here is a link to a YouTube video detailing the problem, and a summary of the video with chapter markings. It's a known issue, and thousands of people are discussing it on multiple social media outlets. Lightroom Classic will read the RAW files from the Nikon Z5 II, but when "auto" WB is applied, a magenta cast takes effect. I spoke to an Adobe rep today. We could not troubleshoot it. Nikon says it's an Adobe issue, and I agree, as this issue does NOT occur in Capture One, or Nikons own software. The JPEGS from the camera are great and as long as "AS SHOT" is applied in LR, it works, but any other WB settings (Auto, Daylight, Cloudy) etc... leans the file so far into magenta, it's unusable. I also tried using the eyedropper tool on a grey card, and it also leans magenta. I am on Mac OS, Sequoia 15.5. Anyone else having this issue? How can we escalate it to Adobe s

As expected, increasing the shadows in an image reveals noise in those regions. However, when a photo in HDR mode has the clarity in the SDR Conversion settings set to roughly -80 or lower, increasing its shadows doesn't just reveal existing noise, but creates new unwanted noise pixels in those regions. These pixels are almost always entirely red, green, or blue, distractingly bright, and can appear in nearly any raw photo.   When the image is taken out of HDR mode, the pixels disappear. In HDR, I only found four ways to remove these pixels outside of masking and manual editing: >Set the entire image to black-and-white mode. >Increase the clarity in the SDR conversion settings. -80 or higher is usually enough to remove them. >Increase the clarity in the tone mapping settings. +15 is usually good even with the clarity at -100 in the conversion settings. >Perform an AI Denoise. >>On the other hand, AI Super Resolution creates even more of these pixels.  

When the catalog setting Write Date Or Time Changes Into Proprietary Raw Files is enabled, Save Metadata To File will incorrectly modify a .CR3, changing its EXIF:DateTimeOriginal.   This bug was introduced in LR 14.4 -- it doesn't occur in LR 14.3. Tested on Mac OS 15.5. To reproduce:   1. Download and open this very small catalog: https://www.dropbox.com/scl/fi/q8h2ewc5tf3snplofz1j8/raw-capture-time.2025-06-29.zip?rlkey=nggfak157pvulk12a5mhcjgsu&dl=0   Observe that the Metadata panel shows the .CR3 has Capture Date/Time: 6/29/25 1:26:10 PM.   2. Open the "pics" subfolder in the catalog folder in Finder with View > As List. Sort the view by Date Modified. Take note of the Date Modified for the .ARW and .CR3.   3. Select both photos and do Metadata > Save Metadata To File. Observe in Finder that the Date Modified of the two files hasn't changed and that there are now two .xmp sidecars (correct).   4. Set the option Catalog Settings > Meta

When a video is exported from Lightroom Classic, the “Capture Date” (CreateDate or DateTimeDigitized) is overwritten with the time of the export. However, the “Capture Date” must not be changed during export. It works when exporting photos.

ISSUE (relates to both Lr and LrC):    Short description: when dual monitors are set to different Scale in Windows then the top menu (File, Edit, Library, etc) and the dropdown menu text size displays in the wrong size (too large in my case).  Also, lines with check boxes in the Preferences menu are cropped in the upper end and are hard to decipher.   Suspected bug: when Lr opens it looks up the scaling set in Windows for the primary display (Monitor 1) regardless of which monitor it resides in. It should look up the scaling of the monitor it is displayed in at any given time.   Background: johnrelis asked me to post this as a bug. Original discussion thread: Re: Menu and context text size in LrC too large - Dual monitor   System Specs:  Lightroom CC 6.1 Lightroom Classic 15.1 Windows 11 Pro for Workstations NVIDIA RTX A4000 Intel(R) Xeon(R) W-11955M CPU @ 2.60GHz 2.61 GHz RAM 128 GB Monitor 1: Internal laptop 17'' (3840x2160)

The previous behavior was to match a caption or filename that starts with the search string.   For example, searching for filename that "Starts With" "FE" matches both "FeeDemoWall.jpg" and "Big Tree 12 Feet.jpg"   The same behaviour happens searching for captions. Maybe other things too but I only tested these two.

Hello, since Lrc 14/14.01 I have not been able to import images from a favourite Win 10 folder.Its where I keep all my misc stuff I download from the net, etc.    Its called "Downloads & Software". I try to import a jpeg and the progress bar on the top left just hangs there doing nothing.   I can import images from other folders.I just created a new folder called 'New Folder' - and cut everything from with "Downloads and Software" and pasted it inside "New Folder".I tried to import a jpeg and the progress bar on the top left just hangs there doing nothing. So there is an issue that it does not want to import from the root folder - yet it imports images from subfolders.   Conversely - if I go to the root of New Folder - select an image and right-click and choose "Open With - Lightroom Classic" - it again shows the import progress bar but it just hangs.   I just put "New Folder"  into another folder - and tried to import from the root of New Folder - and