Bug Reports

the tool diameter. when I shift-click, I can make retouches with the retouch tool, in a straight line from click 1 to 2 to 3 etc. Good for straight lines like cables etc. But I used to be able to change the diameter of the tool and still SHIFT-click, so I could erase a small pole to a larger reflection of the pole in the water. This does no longer work: it works for as long as I keep the same diameter, but no longer when I change the diameter.

after 8 months of struggling with this issue, and 6 months since the bug has been officially recognized by adobe, I am still experiencing an issue with using "b" to choose images for quick collection in GRID VIEW missing approximately every other photo if done in anything other than a glacial pace. It appears if you quickly select a sequence of 10 images (for example) by using the 'b' key every other one adds and then IMMEDIATELY removes itsself from the quick collection (you can see it happen very fast in the prompt on the screen 'added to quick collection, then removed from quick collection) it only happens in grid view, it has happened on new and old catalogs, several different computers, one of the bigger updates late last year initiated the bug for me, I've been using LR virtually every day since 2008. One of the tech support people was able to reproduce it on his computer as well.  Many others suggest I have a computer issue or resource issues (i had an i9 macbook

Issue: "Remove this keyword from selected photos" not working in Loupe mode   Lightroom Classic version: 11.4.1 [ 202206241800-b406ce4c ]Windows 10   Steps to reproduce the issue:Switch to Loupe modeSelect multiple photos in the filmstrip in Loupe viewRight click on a keyword and click "Add keyword to selected photos"Right click the same keyword and click "Remove this keyword from selected photos"   Expected result: Lightroom Classic should remove keywords from all selected photosActual result: Lightroom Classic removes keyword only from the active photo - the remaining selected photos still have the keyword applied. Comment: The "Remove" behaviour is inconsistent with the "Add keyword to selected photos" command, which adds the keyword to ALL selected photos in the Loupe view.   It is possible to go to the Grid view and use the "Remove this keyword from selected photos". However, this step should not be required as the two commands (Add/Remove) should work identica

Hi,The problem I describe below is not new (I observed this at least since version 3) but this time I took the time to investigate more deeply...From time to time, LR tells me that the XMP file of a given image is no longer in sync with the metadata in the catalog. Most often, this is correct because I made changes without recording the XMP file (Ctrl-S - I'm not using the automatic XMP updating mode). But very often, this information is simply wrong. I didn't change anything to the image and suddenly, the little down arrow appears in the upper right corner of the thumbnail.Hitting Ctrl-S may or may not fix the problem. Sometimes, the little down arrow reappears after a few seconds or minutes although I didn't do anything (hands away from keyboard and mouse).I recently did the following test for multiple images unduly displaying the "metadata status changed" flag. I compared the following values :1. Windows "last modified" timestamp for the XMP file.2. Value of the xmp:MetadataDate fie

The new release seems to have an issue with watermarks.   What looks still okay in the watermark editor (as it did in previous versions) gets messed up during export, with light color watermark turning to grey.   See attachments.

Lightroom crashes everytime I click on a video file (MP4), attached is the video of the crashes. I have send a crash report 

This issue was reported to me by multiple LRTimelapse users that use my LRTExport Lightroom Plugin to export their timelapses. Symptom: Exporting sequences of multiple thousand images via a custom export plugin consistantly makes Lightroom Classic 11.4 (and later prereleases) crash. This happens on Windows and Mac machines. There is no problem, with shorter sequences of several hundreds of images, as it appears.   I could reproduce the reports from my users on my machine (Windows 10), latest NVidia drivers, etc.   To exclude the chance of any programming errors in my rather complex LRTExport plugin, I coded a very simple, basic custom export plugin. This simple plugin, also crashes when used to export several thousand images, you can use it to reproduce the issue: https://www.dropbox.com/s/4om4748izdlaw1y/Gunther_Wegner_SimpleExport.lrplugin.zip?dl=1   The more images I export, the faster and more often the crash happens. With 4000 images for example, often after 10 imag

The method folder:getPhotos() always returns the empty array on device folders created by cloud sync.  To reproduce:   1. Install this script as "lrmobile-folder-bug.lua" in the Scripts folder and restart LR:   local LrDialogs = import "LrDialogs" local LrTasks = import "LrTasks" local catalog = import "LrApplication".activeCatalog () LrTasks.startAsyncTask (function () local folder = catalog:getActiveSources ()[1] LrDialogs.message (string.format ("%d photos in %s", #folder:getPhotos (), folder:getPath ())) end)     2. In the Folder panel, select a device folder created by cloud sync.   3. Do the menu command Scripts > lrmobile-folder-bug.lua and observe this output:   Tested on LR 12.0.1 / Mac OS 12.6.1.    

LR won't start up.  Tried updating to V12: Same result.  Downgraded to V11.0:  Same result.  Updated Photoshop (thinking there might have been a shared resource), then update V12 again: same result.   Crash reports sent.   HELP!!  This has shut down my photography.

Hi, Running LrC/12.0 on Windows/10. and have discovered a problem with the backup taken when LrC exits.   The "lrcat-data" folder is missing from the zip file if there has been no AI Mask work performed since the last backup even if the catalog contains AI Masks.   1)  Cteate an AI mask on an image 2)  Shut down LrC, and have it take a backup (I have Optimize and verify unchecked) 3)  Observe that the "lrcat-data" folder is present in the backup zsip file. 4)   Open the LrC again with same catalog 5)  Do whatever you want but don't create or touch any AI Masks 6)  Close LrC and again have it back up 7)  Observe that the zip file contains the catalog but not the "lrcat-data" folder  

Hi. I just updated to Lightroom Classic 12.0, running it on Windows 10 x64 21H2 (same thing happens on Windows 11). When I'm trying to view system info (Help > System Info...) LrC gives error message: So it is unable to view system information, which is frequently reqested by support or here on forums. Please fix this. Thank you.

I want to report an apparent bug. I am using an M1 chip Mac Mini with Monterey 12.6 OS and Lightroom 12. Using the masking tool, having selected a Subject and then going to subtract an Object from the section, as soon as the cursor crosses from the menu to the picture window, the Mac automatically opens a new Mac Desktop window, it won't let you remove an object.  It is not a feature I would use often and I was merely trying it as an option but the same does not happen if subtracting the same object using a brush. Easily worked around but no doubt a bug nevertheless.

I have a 2021 m1 pro macbook running 12.6. I just updated LR classic to 12, and upon attempting to open LR informs me that I must update my catalog from v11 to v12. it starts to update, then at the 'optimizing catalog' phase, it crashes.   I have tried restarting, running a system diagnosis test, reinstalling LR, and confirming all permissions in security/privacy.   the following is the crash log:    ------------------------------------- Translated Report (Full Report Below) -------------------------------------   Process:               Adobe Lightroom Classic [801] Path:                  /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom Classic Identifier:            com.adobe.LightroomClassicCC7 Version:               12.0 Code Type:           &n

When there are two keywords assigned to a photo that have the same name but different case, e.g. Activity > march and Months > March, the keywording panel fails to fully qualify the keywords,  showing "march, March" instead of "march < Activity, March < Months":Further, if you type "March" in the keywording panel, you'll get an incorrect list of auto-complete suggestions "march" and "March", rather than "march < Activity" and "March < Months":If you type "March" and hit enter, you'll incorrectly get "march < Acitivity".  If you type "March" and use the mouse to select the suggestion "March", you'll incorrectly get "march < Activity".In general, LR aggressively ignores case of keywords everywhere except here.  Looks like a programmer forgot to do a case-insensitive comparison.

I'm using Lightroom Classic 11.2 on an iMac with OS 12.2.1.   When I select several .avi video files and try to export them as .mp4 video files via a preset which saves them to a specific folder, it will export a couple but then the progress bar just stays the same and it never finishes the rest. It's like it gets stuck.   Expected result: 5 or 6 (or more) selected .avi files get exported to a folder as .mp4 files.   Actual result: 1 or 2 .avi files get exported to a folder as .mp4 files and the rest never get done while a progress bar stays on in LRC until I cancel the operation (I've waited 20 minutes and 10 minutes on separate occasions.)   I end up cancelling out and exporting them one at a time which works and is faster but is labor intensive. It prevents me from exporting more of those files.

For no reason in particular, LR started to show my name as seen below. I have no idea how to fix it. When I log in to my account, it just has first and lastname without the "%20" in it. Does anyone know how to fix this?    Thanks so much!

Calling preset:getSetting() on the attached develop preset "Test LUT Preset.xmp" (which refers to the attached creative profile "Test LUT Profile.xmp") returns incomplete results:   {--table: 1 EnableCalibration = false, EnableColorAdjustments = false, EnableDetail = false, EnableEffects = false, EnableGrayscaleMix = false, EnableLensCorrections = false, EnableMaskGroupBasedCorrections = false, EnableRedEye = false, EnableRetouch = false, EnableSplitToning = false, EnableToneCurve = false, EnableTransform = false, Version = "14.4.1"}   Adding the line:   crs:ProcessVersion="11.0"   to the preset causes preset:getSetting() to return the correct result:   {--table: 1 EnableCalibration = false, EnableColorAdjustments = false, EnableDetail = false, EnableEffects = false, EnableGrayscaleMix = false, EnableLensCorrections = false, EnableMaskGroupBasedCorrections = false,

The API Reference for LrFileUtils.createAllDirectories (path) incorrectly describes the return values.  The correct description:   Return values (Boolean) True if there were no errors, false if there were errors creating directories in the path. (string or Boolean) If there were errors creating directories, a string describing the error; otherwise, true if one or more directories were created, or false if all the directories already existed.

In Spanish (es_ES), French (fr_FR), and Swedish (sv_SE), the shortcut Shift + S is assigned to both Before Only and Destination Gamut Warning (in Soft Proofing). Typing Shift + S always invokes Before Only.     The relevant TranslatedStrings lines:   "$$$/AgDevelop/Menu/View/BeforeAfter/Before/Key=Shift+s" "$$$/AgDevelop/Menu/View/OutputGamutWarning/Key=Shift+s"   All languages assign Shift + S to Destination Gamut Warning.

The LR 11.4 SDK documentation has a few related minor mistakes:   Page 14 of the Lightroom Classic SDK Programmers Guide:   - LrCatalog:getCollections() should be LrCatalog:getChildCollections() - LrCatalog:getCollectionSets() should be LrCatalog:getChildCollectionSets()   The API Reference page LrCollection.htm:   - "Retrieve the objects for all the collections by calling LrCatalog.getCollections()." should be "Retrieve the objects for all the top-level collections by calling LrCatalog.getChildCollections()."   Highlighted by @ivan238028450jmx:  https://community.adobe.com/t5/lightroom-classic-discussions/remove-photos-form-collections/m-p/13047823#M280907

After the last upgrade (LRC 11.5) the behavior of the export window during the resizing is changed, so now is not possible to enlarge the Preset coloum: due to this fact some preset with long names become unreadable.   Probably this is linked to the Anchor properties, so I suggest to change the Anchor properties or introduce the possibility to resize the "Preset" section.   Here a comparison betweent the two version (11.4.1 and 11.5) during the resizing: Here the resizing with 11.4.1 - The preset area become larger Here the resizing with 11.5 - The preset area remain fixed              

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   The Metadata panel's field Absolute File Path doesn't show renamed file names until LR is restarted. To reproduce:   1. In Metadata > Default, use Customize to put the Absolute File Path field below File Name.   2. Select a photo, click in File Name, and change the name.   3. Observe that Absolute File Path hasn't changed (incorrect):   4. Restart LR and observe Absolute File Path now shows the new file name.   Tested on LR 11.5 / Mac OS 12.4.   These bugs with stale metadata fields keep trickling in after the change several releases ago to the optimized metadata-display architecture.  Perhaps a two-pairs-of-eyes code review is warranted.  

Hi!  I tried opening Lightroom to continue editing some images in a catalog but I keep getting this error message.    I tried all the troubleshooting techniques but nothing has work so far, please help me figure out what's happening;    Error Report:  <?xml version="1.0"?><!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"><crashreport serviceVersion="4.7.0" clientVersion="4.7.0" applicationName="Adobe Lightroom Classic" applicationVersion="11.5" build="[202208080927-8a575c91]" source="Windows-Client" crashType="n/a"><time year="2022" month="8" day="24" hour="11" minute="33" second="55" timeoffset="-300" timezone="Eastern Daylight Time"/><user guid="779df0a4-07e1-44a3-821b-864743934608"/><system platform="Windows Server 2016 Standard" osversion="10.0" osbuild="14393" applicationlanguage="en-us" userlanguage="en-US" oslanguage="en-US" ram="35999" machine="Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz" model="Intel64 Family

On Mac in German (de_DE), Cmd + W is assigned to Preferences, but it doesn't work, because Cmd + W is a Mac global shortcut that closes the current window.   "$$$/Application/Menu/Edit/Preferences/KeyWin=Cmd+w"   Tested on LR 11.5.

In Windows LR 11.5 Japanese (ja_JP), Ctrl + Y is assigned to both Create Virtual Copy and Redo:   "$$$/AgLibrary/Menu/Shared/CreateVirtualCopies/Key=Cmd+y" "$$$/Application/Menu/Edit/RedoWin/Key=Cmd+y"   When the Redo command isn't greyed out, Ctrl + Y invokes Redo, otherwise it invokes Create Virtual Copy.