Bug Reports

In lightroom 11.5 (on mac os catalina 15.7) when i export an image, i select watermark in the export window, then choose 'edit watermark' and then i can select my different watermarks to see which one fits best. In 11.5 whenever i choose a different watermark, it changes to 'edited' and i have to save it with a new name in order to select it. In 11.4.1 and earlier versions, i could select one of my watermark presets that i wanted and click 'done' and that watermark would be applied.   The workaround is to see what watermark fits the image best, then cancel (for i do not want to save a watermark preset that i have and that i have not made any changes to), then choose cancel, and then in the export window, scroll to the watermark i want in the watermark drop down window.

Lightroom classic has been incredibly unstable on my P14s Gen 3 (AMD). My symptoms after editing or flicking through just a handful of photos: Crash with the error message that reading the catalogue failed Main UI stop updating, but second window still works   I've already sent so many bug reports, with the option to get permit getting contacted, but I hear nothing back.    My best guess is that it overshoots the amount of video ram that's allocated. Even the Adobe info panel indicates >100% utilisation. Is it possible to manually reduce GPU RAM allocation? Or is that caused by another issue? I'd greatly appreciate something that can help me stop these constant crashes.

This problem just recently started. I believe I upgraded my Mac M1 to Ventura and updated Lightroom to the latest version since this stopped working. I have no problem using Nikon transfer to transfer the images from both cameras.    When I select Add Photos in Lightroom then select Connected Devices (Lightroom does recognize both cameras when they are connected), I see the camera flashing its green indicator as it typically does to reflect that Lightroom seems to be reading. While it is reading, Lightroom displays the message "No images can be imported...." Prior to this issue, that message would be displayed until Lightroom finishes reading the camera or camera card. Now that message remains indefinitely.    So I am wondering if there was something in either the OS update or Lightroom update that has caused this to stop working.  

Hi all-   I am running a IMAC with Monteray v12.6.1 currently.  This IMAC is 1 year old using the new INTEL chip. I downloaded the new release of LR Classic [v12 ] and discovered that when I insert a memory card to download images, LR does not detect and open the import mode as it use to do.  I have checked the preferences and made sure the "Show import dialog when a memory card is detected"  box is checked.  I have also shut both computer and LR down completely and rebooted to make sure both had a clean start, and it still will not recognize the memory card when inserted.  Everything I have done or used as it was before the new release.   I have contacted a few friends and they have confirmed the same issues.  Anyone else having this problema d ndoes anyone have a solution?   Thanks   Ralph

I am consistently finding all spot removal adjustments rendered as pink block artifacts after converting to compressed DNG. I am using LR Classic 10.1.1 on a 2017 15 inch MacBook Pro running macOS Catalina 10.15.7. I've seen the problem with a Canon R5 (raw and c-raw), Canon 5DmkIII, and Fuji X-T3 (RAF). The artifacts don't immediately appear - only when rendering 1:1 - so they are easy to overlook. I can remove the artifacts by modifying each spot removal adjustment in some way (often I'll just select an adjustment and nudge the feather slider up and down by one so the adjustment isn't affected). Also, there doesn't seem to be a problem when adding spot removal adjustments to images after they are converted to compressed DNG. Not sure how long this problem has been around - I've just discovered it when testing compressed DNG as a possible way to manage file sizes from the R5. Here are screenshots showing the original raw, compressed DNG, and exported PSD...      

I have noticed that when I zoom to fill in Print mode Lightroom classic the colour seriously degrades, has anyone else experenced the same?

Video syncing is inconsistent.  Some videos are only showing up only in LR iOS Mobile while others only show up in Light room Classic CC. Lightroom Classic CC v 7.4 Lightroom iOS Mobile v. 3.3.0.7E41A6  (running on ios v 11.4) issues reported are seen on an ipad and iphone 6 - identical results Windows 10 PC   LR iOS  Mobile  shows 263 photos in the All synced photos, which include 9 videos. LR Classic CC shows 254 photos in the All synced photos and does not show the 9 videos. LR Cloud shows 263 - (254 photo and 9 videos). the 9 videos have auto imported into my collection and into the LT Classic CC catalog and now do reside in my windows 10 PC HDD three of the videos were removed from the synced collection  They are no longer in the Classic CC all synced count,  but continued to exist in the iOS all synced and can be viewed in iOS mobile 6 are new from yesterday and show in the collection, tha iOS all synced, but do not how in the Classic CC

Several dozen key assignments in the TranslatedStrings files are syntactically invalid, causing them to be ignored by LR.  The errors include:   - Using the translation of a modifier instead of the internal name, e.g. "Wahl" instead of "Option".   - Including spaces (e.g. "Cmd + s" instead of "Cmd+s").   Here are the errors my script discovered; a CSV containing the offending lines is attached:        

Hi everyone. Has anyone else encountered this problem. I can rename a single file, but not a batch rename of 726 files anymore. When I export to jpegs the rename function works fine. Any help would be appreciated. Cheers, Andy.  

There is a bug ion Lightroom classic where you cannot remove a preset. Regular Presets remove fine on the export panel, but if it has any Postprocess action (I use Jpeg Mini and Metadata Wrangler ) you cannot remove the preset. Even if you remove the post process action, you cannot remove the preset. When you select it the remove stays greyed out and the action activates automatically (even if you removed it a few seconds ago from that preset).  The only option you have is to select the preset (remove is greyed out) right click and delete. I think this is a bug and confusing users. The remove option should be not greyed out and work properly when you want to remove a preset even if an action is bound to it.

Issue: LR Classic performance on macOS x86_64 drops when a 2nd screen is connected Lightroom Classic version: 12.0.1 [ 202210260744-9e008017 ] OS and version: macOS 12.6.1 (21G217) Machine: iMac (Retina 5K, 27-inch, 2017), 24 GB RAM, Radeon Pro 580 8 GB   Steps to reproduce: 1. Connect a second monitor (in my case a Dell U2212HM) 2. Run LR Classic and edit photos in Develop, note performance especially when adding a few masks; mouse pointer often gets sluggish. Performance marginally improves when disabling other panels, i.e. Detail and Lens Corrections, but remains low and sluggish. The fan often spins up briefly when using brushes. Performance is low even if the second monitor shows no LR Classic windows (in my case just macOS's desktop)  3. Quit LR Classic, no need to reboot the machine 4. Disconnect the second monitor 5. Reopen LR Classic and keep editing, note performance increases and is on par with what the machine should support, even with all other dev

JPEGs exported by LR are missing the PixelXDimension and PixelYDimension EXIF tags (image width and height), required by EXIF Version 2.32 (and prior versions going back to at least EXIF Version 2.2, 2002).  This trips up software libraries expecting to find those mandatory tags.    Tested on LR 12.0.1 / Mac OS 12.6.1 and LR 6.14 / Windows 10.   To reproduce:   1. Export any photo from LR as a JPEG.   2. Run this Exiftool command on the exported JPEG:   exiftool -a -G -EXIF:ExifImageWidth -EXIF:ExifImageHeight file.jpg   (Exiftool calls PixelXDimension and PixelYDimension "ExifImageWidth" and "ExifImageHeight".)   Here's the relevant section from the EXIF Version 2.32 specification (page 44):   Note that Photoshop correctly writes those tags, though it also writes EXIF:ImageWidth and EXIF:ImageLength, which violates the standard in a different way (page 28):        

Hi. I'm writing Ligtroom plugin, and faced the fact that at least LrStringUtils.upper() and LrStringUtils.lower() doesn't work as expected. For example for LrStringUtils.upper() documentation says:       Converts a string to uppercase using the operating system's localized case conversion. Unlike the Lua string.upper function, this function properly converts characters outside the 7-bit ASCII space.       In practice: it's not any different from the string.upper() - only characters a-z are properly converted to uppercase. Here is my test code:       local LrDialogs=import("LrDialogs") local LrStringUtils=import("LrStringUtils") local s1=tostring(LrStringUtils.upper("ТеСт-TeSt-óó")) local s2=tostring(LrStringUtils.upper("тЕсТ-tEsT-óó")) LrDialogs.message(s1..", "..s2..", "..tostring(s1==s2))       The result is       ТеСт-TEST-óó, тЕсТ-TEST-óó, false       As you can see - only latin

I have a collection of photos, some are originals with a 2x3 ratio, and some derivatives with a 1x1 ratio. I am trying to reset the crop on all of them to "Original", both by selecting "Original" and hitting "Reset".   Example: If I highlight both photos, select the 2x3 file as my reference and sync, it will make the 1x1 into a 2x3, not keep the original ratio. Reverse happens when I select the 1x1 and sync. Unless this is a feature and not a bug, selecting Original apect ration/hitting Reset should flat out reset the cropping, not adopt the reference crop ratio. I could go to each photo and Reset, but I have 100+ photos, and this seems to be a bug.

Issue: Memory usage/utilization is skyrocketing up to 13-14GB and start swaping memory to SSD, with the healing brush feature with "Auto" or all "Custom" in performance tab options selected Provide Lightroom Classic version: Lightroom Classic version: 12.1 [ 202212072312-d7ab524b ]Provide OS and version: Mac OS 13.1.0 [22C65]Application architecture: arm64 Graphics Processor Info:Metal: Apple M1Init State: GPU for Export supported by defaultUser Preference: AutoAND User Preference: GPU for Export enabledAND User Preference: GPU for Image Processing Enabled Issue: Provide good steps to reproduce the behavior:Step 1: open any photo to processing,Step 2: use healing brush few times, add some point,Step 3: wait for LR eat memory from 2,5-3GB standard to 12-13 GB and check resource monitor ONLY when User Preference: GPU for Display Enabledthis problem does not occur Expected result: memory should remain at the same level than user optiom: GPU for Display EnabledActual result: memory utiliza

In Lightroom ist es anscheinend nicht (mehr) möglich, entwickelte Fotos auf ein Laufwerk zu exportieren, welches ein Windows Subst ist. Es kommt lediglich eine verwirrende Fehlermeldung "Einige Exportvorgänge wurden nicht durchgeführt. Die Datei konnte nicht geschrieben werden. DSCxxx.NEF". Auf dieses Verzeichnis/Laufwerk besitzt Lightroom Schreibrechte. Es kann z.B. während des Exportes ein Unterverzeichnis erstellen. Nur Fotos werden keine exportiert. Die XMP Sidecar Dateien können dort hin geschrieben werden. In Lightroom 4, 5 u. 6 ging das problemlos.   PC, Intel i7 12. Gen Windows 10 21H2 Lightroom Classic 12.0.1 Ein Subst Laufwerk wird z.B. per "subst x: c:\fotos" erstellt. Entwicklung von Nikon NEF, Export als JPG.   Schritte zur Reproduktion: - Windows Subst Laufwerk erstellen - Verzeichnis mit NEF Dateien am Subst Laufwerk in Lightroom importieren - Bild entwickeln - Bild exportieren (gleiches Verzeichnis mit Unterverzeichnis. Export als JPG.)   Erwartung: - Exp

My Lightroom Classic keeps crashing. Made sure I had the most recent update. Updated my Mac operating system to: Ventura 13.1. It's still crashing. Any advice?

LR Classic 14.4.1 on IOS 12.3.1 When generating Previews, it stops when it meets a videofile.

Hi,   I'm having an issue when I edit images from Lightroom in Photoshop. I have applied a lens correction profile in Lightroom. When I open the image to edit it in Photoshop, the lens correction is no longer applied.     I found a couple other past posts with this or similar issues and the only suggested solution was to roll back Camera Raw. However, having just updated PS to v24 and upgraded my LR catalog to v12 (and done lots of work in it), there's nowhere to roll back to without going back a major release (and losing lots of work in LR).     I'm using: LR 12.0.1 PS 24.0.0 Camera Raw plugin v15.0.0.1264 Windows 10 v22H2     Please let me know if you have any questions or need further information from me.   Thanks, John

Recently I updated my Lightroom Classic on my MacMini M1 from 11.31 to 11.4, then I found that the flat-field correction does not acctully work anymore. (I use Leica M240 with SuperAngulon 21mm)  I did that step by step for many times, I could click the button and the loading bar also run, but the photos changed nothing. I reinstalled the version 11.31 today and it worked, then I tried to install version 11.4 and it didn't work again. So I think it might be a bug of 11.4 either on all computers or on Mac. 

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   In some circumstances, the smart-collection criterion "Rating is greater than <no stars>" matches photos with no stars.  Tested on LR 11.1 / Mac OS 11.6.2. To reproduce:   1. Make a new catalog and import two photos.   2. Set the rating of one photo to 1 star; leave the other photo with no stars.   3. Create a smart collection with two criteria, "Keywords contains <blank>" and "Rating is greater than <no stars>", in that order. When you add the Rating criterion, be sure not to click any of the stars:   4. Note that both photos are matched by the smart collection. But only the photo with 1 star should be matched.   5. Right-click the collection and do Export Smart Collection Settings.   Observe that the exported text file incorrectly contains these lines:   { criteria = "rating", operation = "&gt

The field "bitDepth" works in catalog:findPhotos() but not with photo:getRawMetadata ("bitDepth").   That field is labeled Bits Per Channel in smart collections and Bits Per Sample in the Metadata > DNG panel.

The shortcut Shift Z is assigned to Window > Secondary Display > Loupe - Live. On Mac, it works exactly once and then is ignored (though it works correctly on Windows).  Tested on LR 11.5 / Mac OS 12.5.1 and Windows 10.   1. Restart LR.   2. Do Window > Secondary Display > Loupe - Normal.   3. Do Windows > Secondary Display > Loupe - Live and observe the mode changes to Live in the upper-right corner.      4. Do Windows > Secondary Display > Loupe - Normal and observe the mode change to Normal.   5. Type Shift Z and observe the mode change to Live.   6. Type Shift Z again. On Windows, it toggles the mode between Normal and Live. On Mac it does nothing until you restart LR, though the menu command Windows > Secondary Display > Loupe - Live continues to work as expected.   This was discovered while working with Per Berntsen, who observed changing and flaky behavior trying to change shortcuts in Translate

Shift Z is assigned to both New Depth Range Mask and Window > Secondary Display > Loupe - Live (all languages).  When editing an image with a depth map, Shift Z invokes the New Depth Range command until you open the secondary display window, at which point it invokes Loupe - Live.  Even after closing the secondary display window, Shift Z will no longer invoke New Depth Range Mask until you restart LR.   Test on LR 11.5 / Mac OS 12.5.1 and Windows 10.   To reproduce:   1. Restart LR.   2. Edit a photo with a depth map.   3. Shift Z makes a new Depth Range mask.   4. Reset the photo and repeat step 3.   5. Do Window > Secondary Display > Loupe - Normal.   6. Shift Z toggles between Loupe - Normal and Loupe - Live, rather than opening a new mask.   7. Close the secondary display window.    8. Shift Z no longer creates new mask.   This behavior may be related to the flaky behavior of Shift Z on Mac:

The Help windows displaying keyboard shortcuts have many errors (about 500).  These errors include: - Showing the wrong key, e.g. Command + ] instead of Mayús + : for Rotate Right in Spanish. - Showing Delete on Windows instead of Backspace, or Backspace on Mac instead of Delete.   - Showing the internal name for a key instead of the user-interface name, e.g. Esc instead of Escape. - Showing the English name for a key instead of the translation, e.g. Shift instead of Maj in French. - Inconsistent capitalization, e.g. Touche Gauche and touche Gauche. - Variant names of the same key, e.g. Touche flèche gauche and touche Gauche. - Using \ in TranslatedStrings instead of ^L. - Inconsistent spacing around "+", e.g. "Shift+F" or "Shift+<space>F" instead of "Shift<space>+<space>F". I've attached the file "errors.txt" containing the complete list of mistakes. My soon-to-be-released Any Shortcut pl