Bug Reports

When Command-E to send an image to Photoshop, (DNG from iPhone), the image is much lighter. I've been using Photoshop since verion 3 and Lightroom since version 1 and have never come across this. In order to make it work, I have to Export as PSD, only then does Photoshop match what I see in Lightroom. Any thoughts? Mac Studio 2025, M4 Max 128 GB,  15.6, latest versions of LR and PS.    

Ich fotografiere seit vielen Jahren mit der Nikon Z6 und seit Anfang 2025 mit der Nikon Z6 III und u. a. mit 5 Zeiss Objektiven ZF.2.Mit der Z6 III werden 3 dieser Zeiss Objektive in Lightroom unter Objektivdaten mit 5mm f1 angezeigt, obwohl die richtigen Daten 35 mm f2,0 und 50 mm f 2,0 und 100 mm f2,0 sind. Mit der Z6 werden die vorgenannten 3 Zeiss Objektive dagegen korrenkt angezeigt!Die Firmware beider Kameras ist auf dem aktuellen Stand.   In den RAW-Aufnahmen mit beiden Kameras werden im Exif-Viewer die korrekten Objektivdaten angezeigt!   Folglich müssen in Lightroom Fehler in der Kombination "Profildaten" Kamera Nikon Z8 II und den "Profildaten" der genannten 3 Zeiss Objektive sein.   Wegen des Fehlers kann ich bei den Aufnahmen mit der Z6 III nicht erkennen, welche Aufnahme mit welchem der 3 verschiedenen Zeiss-Objektiven entstanden sind.   Ich hoffe, dass die Adobe Lightroom Systembetreuer das Problem lösen können.    

Help required: I get Lr crashes when I move an image to the print module in LR classic.  2022 m1 max iMac studio with 32gb of ram. I noted that memory pressure was only at 40% at last occurrence. I have reported via the submit crash report pop-up on numerous occasions with no reply, and the system check pop-up finds no fault within my system.   extract from the crash report>>   Process: Adobe Lightroom Classic [5066]Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier: com.adobe.LightroomClassicCC7Version: 14.0.1 (14.0.1)Code Type: ARM-64 (Native)Parent Process: launchd [1]User ID: 501 Date/Time: 2024-10-27 16:50:27.7684 +0000OS Version: macOS 14.7 (23H124)Report Version: 12Anonymous UUID: 6BC1FE9C-D164-90F3-6A59-95387E283444 Sleep/Wake UUID: C3527BE1-A19E-4F28-9F25-1754EEBC87DF Time Awake Since Boot: 30000 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue:

I notice that LR eats all memory when you start importing images. When opened, it takes about 1.5-3GB ram. Then import 100 images, and RAM shoots up to +17GB   Iv been doing some tests with smaller raw files, same thing, always goes up to 17GB ram usage. The folder i imported as test contains only 5GB of raws, and LR uses more then twice that amount to import those images? When you delete the images, 17GB ram is still in use. Then tested less images, like 30, and memory still goes up, but less, around 5GB ram extra, for images that on disk only take around 1GB. Importing more images, like +300 will not make memory to increase more then 17GB.   Solution? Import images, restart LR to clear memory, edit... and ram usage will stay "normal" around 6GB during edit after some testing. Thats 10GB less then just doing an import. Whats up with that?   Im on 13.5 btw   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

Lightroom 14.3.1/Camera Raw 17.3.1 Windows 11 Version 24H2   For all non-adaptive profiles the histogram in the develop module's Histogram widget and the histogram displayed behind the Tone Curve widget match in shape and the tone curve works correctly (c.f. first screenshot).   As soon as an adaptive profile is applied the tone curve seems to be compressed to the first 3 quadrants and reacts overly sensitive. (c.f. second screenshot) Also when adjusting the tone curve picking the brightness values directly from the image even whites/blown out hightlights are not mapped to 250+ values but rather to 180+ (c.f. third screenshot).   Steps to reproduce: 1. Select a raw file (Canon .cr3 from a R6 II in my case) 2. Go to develop module 3. In the Basic widget switch to one of the adaptive profiles e.g. Adaptive Color 4. Go to the Tone Curve widget and check the histogram; the histogram only use the 3 leftmost quadrants 5. Now switch to a non-adaptive profile e.g. Adobe Color 6.

Hello,  still not working in LRC 14.0.1.  , I have old yellow badges but not new ones on last sync. collection. Any idea ?

The Edit Capture Time command doesn't preserve fractional seconds when shifting the time of multiple photos. For example, if you select a batch of photos taken with "continuous shooting", e.g. at a sporting event, and then use Edit Capture Time to shift their time by 60 minutes, the fractional seconds of each photo will be dropped and the photos will no longer be correctly ordered by capture time. To reproduce, take several photos that were all shot within the same second with the continuous-shooting option of the camera. LR will correctly transfer the capture time into their .xmp sidecars: [XMP] Date/Time Original : 2011:05:13 18:32:44.51 [XMP] Date/Time Original : 2011:05:13 18:32:44.52 [XMP] Date/Time Original : 2011:05:13 18:32:44.53 Then select those photos and invoke Edit Capture Time. Use either the "Adjust to a specified date and time" or the "Shift by set number of hours" option to shift the time by 1 hour. Observe that the fractional seconds in the sidecars is now dropped: [X

Have updated to LR Classic CC 7.3  Develop module when using the crop tool it shows the last image cropped for about 1 second before showing the current selected image.

I think I found a bug in LrC when soft proofing. Typically when you edit a picture and then hit the compare button, you are shown on the left the original picture and on the right the edited picture, like on the top part of the following screenshot.But if you do soft proofing this comparison is broken, as you can see in the bottom part of the following screenshot, where I am being presented left and right with the same edited photo. Steps to reproduce:1- Click on soft proof2- Click on create proof copy3- Click on compare button  Before/After Button (Compare is a Library Feature)4- Click on single photo to show only edited picture5- Remove proof copy (only from LrC)6- Click on compare > l  Before/After Button (Compare is a Library Feature)   Result:Left edited phot and right edited photoExpected:Left is unedited/Right is edited Reproduction was done on version 14.5.1 Mod Comments in Bold

I am working under the Edit menu to change the identity plate setup.  I have selected personalized and custom plate, and Show Status and Activity is selected.  I have typed the custom text I want to display and selected the typeface and font size.The issue starts when I select the complementary typeface for the module picker buttons and font size.  The font size starts off as if it's a multiple of the selected size, not the selected font size.  Regardless of typeface, it behaves similarly.It gets better.  Regardless of the size selected in the button picker, each time a different typeface is selected, the size gets bigger by what looks like the same multiple.  The size returns to the original (wrong) font size when the size is manually selected.Here's my machine:Refurbished and nearly new (two months old to me): Dell XPS 13.3" QHD+ TOUCH Laptop 7th Gen Intel Core i7-7560U at 2.4GHz with Turbo Boost to 3.8GHz, 16GB RAM, 512GB SSD using the Intel HD gra

Since the last update opening photo in Photoshop by right clicking in Lightroom doesn't work anymore.   Working on a Mac Mini latest ver. of OSX

I installed the new version 14.4 today. Whenever I attempt to use the new denoise slider, I get this error "attempt to index a nil value".  And then, when I try to use the old-fashioned denoise, I get "image not loaded". I am working on a MacBook Pro with an M2 chip and I already reset Lightroom preferences. Anyone else having this issue?    

Started on a Mac all was fine.  Moved to my Windows laptop.  My pics are on a NAS.  Did a find missing folder and it found the folder find on the PC.  I have upgraded my Mac so I want to move back.  No issues moving over the catalogs and starting the app.  The NAS folder was available and mounted under the Network prior to starting Lightroom Classic.  Had no problems navigating with the folders prior to starting.  Of course LR classic no longer knew where the mounted folder was so I when in did find missing folder.  I was able to navigate to the folder on the mac.  However when I selected the folder on the Mac, I am getting "An internal error has occurred.  invalid path" error.  Even thought I had no issues navigating to the folder...  So, now I have thousand of photos I cannot get to inside LR Classic, but no problems getting to under the Mac...  version is 14.1.1.

When I preview photos in LRC on memory card before import they are small and blurry with my new Canon R5 and R3. My old cameras showed full size and sharp previews.

Most of the documentation for the LrView "bind_to_object" and "key" properties is incorrect and omits important information.  From the LR 14.3 SDK: API Reference LrView.bind() says in multiple places "bind_to_object" is a string. But in fact it is an observable table returned by LrBinding.makePropertyTable(). LrView.bind() omits the following about "key":  A key name for the observed property. If "key" is of the form "x.y", then it refers to the key "y" in the table bound to key "x" in the current bound table.  Are multiple dots allowed, e.g. "x.y.z"? LrBinding.andAllKeys() and LrBinding.orAllKeys() say "bind_to_object" is a string, but it is in fact a table as specified in LrView.bind(). LrBinding: Can the various instances of "key" be in in hierarchical form, as in LrView.bind()?   Lightroom Classic SDK Guide Page 105: Says "bind_to_object:  Optional. The name of an observable table which overrides the value of the

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".