Bug Reports

calling waitForRender() in postProcessRenderedPhotos generates an error ("An unknown error occurred. This photo was not rendered") when called in a "Publish" setting. The same code works just fine in "Export" setting. The same code used to run just fine in the past for several years, this issue is new, a regression.   I also was able to reproduce the issue using the creatorfilter.lrdevplugin sample plug-in that is supplied with the SDK.   You can download a sample plugin demonstrating the issue from here: http://eyalredler.com/stuff/lightroom_bug.lrplugin.zip   To reproduce: 1. Add the plugin in "Plugin Manager" 2. Add the plugin (named "Publish Bug Demo") to an export and export - all should be well 3. Add the plugin to a publish and publish - "An unknown error occurred. This photo was not rendered" is presented for each image   Here's the plugin code (2 files):       --[[--------------------------------------------------------------------------

Hi folks, I sometimes use the "enhance details" feature available from the "photo" menu (Ctrl + Option + I). This is the feature that increases the pixel amount by 4x using Adobe Super Resolution. Then there is another tool in the "library" menu, called "refine photos" which apparently helps with picking/rejecting. Never used it...   So the issue is that in the German translation of LRC, both functions are called exactly the same: Enhance: "Verbessern..." Refine: "Fotos verbessern..."   This is not only wrong (verbessern = improve, so correctly applies to first function "enhance", but definitely not "refine") but also very confusing.   Any chance Adobe will change the translation?   Thanks and best regards John

Issue:  Lightroom Classic Version Number:  12.1 [ 202212072312-d7ab524b ] OS Version Number:  Ventura 13.1 Steps to reproduce: Grid View, Keyword List Metadata, Keyword Shortcut Enter items or Keyword List - Crtl Click or Right Click Use this a Keyboard Shortcut Expected result: + sign should appear after KeywordActual result: + sign does Not apear, but function works.  For example in my list, the + is on a person, Liz, but if I execute the steps I an change the actual shortcut but the + stays on Liz.  

Hallo, ich benötige euer Hilfe.   Das neu installierte Lightroom Classic V12.1 auf Windows 10 startet auf dem PC nur im Online-Modus. Das Progamm ist registriert, die Mailadresse wird online angezeigt und es wurden noch keine Anpassungen vorgenommen.   Sobald der PC offline ist, lässt sich das Programm nicht öffnen. Es erscheint keine Fehlermeldung.   Das ebenfalls auf dem PC neu installierte Photoshop startet offline problemlos. Darüberhinaus startet das zeitgleich, auf einem Notebook, installierte Lightroom Classic ebenfalls problemlos offline.   Wer kennt eine Lösung um Offline arbeiten zu können?   Vielen Dank im Voraus für eure Unterstützung. Michael

Based on posted recommendations here, I updated my LR C to 12.1., however, I still do get the error message and am not able to open LR at all.    What shall I do? Views  

I LOVE the new AI Masks but with the latest update, I was SO disappointed to find that I could no longer select different features like TEETH, SKIN and EYES if I choose ALL PEOPLE.  I can get those options only if I choose INDIVIDUAL people.  While this option accomplishes the same thing as I can add multiple recognized humans, the HUGE bummer is that I can't copy and paste ALL PEOPLE masks and have the AI create custom masks for different photos as the arrangements and people change.  I basically could program it to apply custom filters to any faces recognized in the photos.  Now it will only apply it to the people it recognized in the one photo example I'm using as a source to PASTE from.  This feature has lost all value for productivity.  Am I missing something!!!!?? HELP! 

The Help for "Apply Subject and Sky masks in batch edit" has several errors. It says:   "1. Open a photo in the Develop module....3. Click Copy at the bottom of the Presets panel...4. ...select the photos you want to paste the mask to. You can use the filmstrip for this.5. Once the desired photos are selected, click Paste. You can also press Ctrl/Cmd-V."   - The section title should be "Apply AI masks in batch edit", since the instructions apply to all types of AI masks.   - Step 5, clicking Paste, won't update all the selected photos in Develop or in Library Loupe -- it will only update the most-selected photo.   - The shortcut for Paste is Shift+Ctrl/Cmd+V, not Ctrl/Cmd+V.  And Adobe's convention is to use "+", not "-", in keyboard shortcuts.   * * *   The instructions should be rewritten to use one of the methods that does work:   - Do the Copy/Paste Settings in Library Grid view.   - Use the Sync Settings command.   - Righ

LR can display two "User Presets" groups in the Presets panel when running in other languages.  To reproduce:   1. Start LR in German.   2. Create a preset, putting it in the group "Test Group".   3. Right-click the newly clicked preset and do Verschieben (Move), selecting Benutzer-Presets (User Presets).   4. Observe there are now two groups named Benutzer-Presets:   I observe similar results for Norwegian but not English. (I didn't test the other 13 languages.)  Most likely, some code path is testing a group name against the English "User Presets" rather than the translation of "User Presets".   Tested on LR 12.0.1 / Mac OS 12.6.1.  

Wersja Lightroom Classic: 12.0.1 [ 202210260744-9e008017 ]Licencja: Creative CloudUstawienie języka: pl-PLSystem operacyjny: Mac OS 13Wersja: 13.0.0 [22A380] Steps to reproduce: Change photo name (F2) shortcut Create own template Choose last option (see screenshot) Expected result: "seconds" should be translated to "sekundy"Actual result: "seconds" are translated to "Drugi"

Hello, not sure if this has allready been mentioned.  When I fill in a keyword that has for example 2 psd-images, click on the arrow to view the 2 images and edit one in Photoshop. Then I save the image and return to Lightroom to see that the image has dissapeared. I can still see there are 2 images with that specific keyword but I am not able to see the image I just edited in Photoshop.  One solution is restarting Lightroom, but it's quite annoying to keep restarting Ligtroom every time. Anyone with a similar problem or a fix maybe? I am using a Macbook Pro with all the latest updates. Thanks!

From Lr Classic 11.2 update, photo count of collection does not update on drop photos on collection. LrC Version 11.2, macos monterey 12.2.1  Reproduce step. Drop selected photos from grid view, to filtered collection by name. Expected. Increse count of photos on collection. Actual Result. Count stays before drop.

There is an extremely irritating BUG in Adobe Lightroom. When creating a Smart Collection and you are setting the filter criteria option to PICK FLAG to REJECTED before I select IS/IS NOTReconstruction steps: 1. Select: Pick Flag2. Select: REJECTED3. Select: IS NOTREJECTED value change back to default on step 3: FLAGGED4. Select: REJECTED5. SAVE

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