Bug Reports

In LR 11.5 Norwegian (nb_NO), comma (,) is assigned to both Show Filter Bar and Decrease Rating. When a photo is selected, Comma invokes Decrease Rating, otherwise it invokes Show Filter Bar.   "$$$/AgLibrary/Menu/View/ShowFilterBar/Key=," "$$$/LibraryMenus/MenuShortcut/DecreaseRating=,"    

In Japanese (ja_JP), the shortcut Shift + Q is assigned to both Create Luminance Range and Constrain Aspect Ratio. Typing Shift + Q always invokes Create Luminance Range even when the Crop Tool is open.     The relevant TranslatedStrings lines:   "$$$/AgDevelop/Menu/View/LuminanceRange/Key=Shift+q" "$$$/AgDevelop/Menu/Photo/ConstrainAspectRatio/Key=Shift+q"     All languages assign Shift + Q to Create Luminance Range.

In Spanish (es_ES) and Swedish (sv_SE), the shortcut Shift + R is assigned to both Open In Reference View and Constrain Aspect Ratio. Typing Shift + R always invokes Open In Reference View even when the Crop Tool is open.     The relevant TranslatedStrings lines:   "$$$/AgDevelop/Menu/View/ReferenceActiveView/Key=Shift+R" "$$$/AgDevelop/Menu/Photo/ConstrainAspectRatio/Key=Shift+r"   All languages assign Shift + R to Open In Reference View.

LrC 11.4 est suivantes,Les titres des nouveau presets proposés ne sont pas traduits exactement de la même façon depuis l'anglais vers le français et donc les Styles : Cinematic et cinematic II en anglais devientent Style : Cinématographique, Cinéma II et ; Subject: Travel, Sujet :Voyage et Subject : Travel II, Objet : Voyage II.Ainsi, les titres ne se suivent pas dans un ordre logiqu et alphabétique dans la version française.

In Japanese (ja_JP), LR has an incorrect assignment for Library Loupe Zoom Out -- it is currently "Cmd + ," but should be "Cmd + -".   Typing "Cmd + ," in Library Loupe opens Preferences.   In Develop, Zoom Out is assigned "Cmd + -" (and it works).   The offending lines in TranslatedStrings_Lr_ja_JP.txt:     "$$$/AgLibrary/Menu/View/ZoomOut/Key=Cmd+," "$$$/AgLibrary/Help/Shortcuts/Zoom_out/Key=Command + ,"  

In Norwegian (nb_NO), the menu command Window > Screen Mode > Full Screen Preview is incorrectly assigned the keyboard shortcut "i" instead of "f".    In Library, Develop, Map, Book, and Print, "i" is also assigned to Cycle Info Display, Cycle Info Display, Show Map Info, Show Info Overlay, and Show Info Overlay respectively. Every other language assigns "f" to Full Screen Preview. The offending line in TranslatedStrings_Lr_nb_NO.txt is: "$$$/Application/Menu/Window/FullscreenPreview/Key=i" The localized help shortcuts correctly show "f": "$$$/AgDevelopShortcuts/Full_screen_modes/Key=F" "$$$/AgLibrary/Help/Shortcuts/Full_screen_modes/Key=F" "$$$/AgPrintShortcuts/Full_screen_modes/Key=F"      

Version of the app: Lightroom Classic 11.4   Platform and OS version: Windows 10 Pro 21H2   Basic steps to reproduce the problem:  Export a set of 480 RAW files with various develop edits, to 8-bit TIF   Expected result: The progress bar in the Lightroom modules panel/bar and and Windows taskbar button should show accurate ratio and percentage of completion while the export job is running.   Actual result: When the Lightroom modules panel/bar is minimized, the progress bar only moves up to 7% of the length until the entire job is completed. If the modules panel/bar is maximized, the progress bar shows an accurate proportion. The Windows taskbar button displays from 0% to 3% when 30% of the job is complete, and up to 7% when 60% of the job is complete. It never goes over 7% even when the job nears 100% completion. The green progress bar in the taskbar button reflects the same erroneous progress value.

The keyboard shortcuts for Rotate Right shown by the menu commands Help > Library Module Shortcuts and Develop Module Shortcuts are wrong for many languages. Similarly, the the keyboard shortcuts for Create A Radial Gradient shown in the help window for the Masks panel are wrong for several languages.   LR 11.4 corrected some of the previous incorrect entries but introduced new ones.   The tables below, extracted from TranslatedStrings, shows the incorrect help entries in red:      

Lightroom no me permité usar el shortcut: shift + M para girar imágenes ¿Alguien tiene el mismo problema?

In Japanese, comma (,) is assigned to both Increase Slider Value and Select Previous Basic Panel Slider:     "$$$/AgDevelop/KBSC/incrementTargetAdjustmentValue=," "$$$/AgDevelop/KBSC/targetPreviousAdjustment=,"     Typing a comma invokes Select Previous Basic Panel Slider.   Tested in LR 11.5.

When LR is set to Russian or Thai, the Windows help for shortcuts uses "Command" and "Option" rather than "Control" and "Alt". Google image search for "russian keyboard windows" and "thai keyboard windows" confirms that it should be "Control" and "Alt".   For example, here's Help > Library Module Shortcuts:    

The keyboard shortcut assignments for five commands in Swedish (SV) have unambiguous typos.     In Swedish on Mac, Create Saved Book, Create Saved Print, Create Saved Slideshow, and Create Saved Web Gallery are assigned Cmd + Shift + s, whereas in every other language those commands are assigned Cmd + s.   Similarly, in Swedish on Mac, Update Metadata Based Captions is assigned Cmd + Shift + m, whereas in every other language that command is assigned Cmd + m.   The differences in the Swedish assignments arise from using Cmd+S and Cmd+M in TranslatedStrings, rather than Cmd+s and Cmd+m:     "$$$/AgLayout/Menu/Books/UpdateMetadataBasedCaptions/Key=Cmd+M" "$$$/AgLayout/Menu/Book/SaveTemplate/Key=Cmd+S" "$$$/AgLayout/Menu/Print/SavePrint/Key=Cmd+S" "$$$/AgLayout/Menu/Slideshow/SaveSlideshow/Key=Cmd+S" "$$$/AgLayout/Menu/WPG/SaveWebGallery/Key=Cmd+S"     On Windows, Cmd+S is interpreted by LR as Ctrl + s, but on Mac it is interpreted as Cmd + Shi

I just updated both Lightroom Classic and Photoshop to the latest versions (11.1 and 23.1)   I'm in Lightroom and I have an export action that ends with opening the current image in Photoshop (see screenshot below)   If the folder path where the image resides has parenthesis in it (even just one bracket, actually), Photoshop fires up but no image is open. Could you please look into this?

In Norwegian (nb_NO), the shortcuts assigned to Rotate Left (Shift + J) and Rotate Right (Shift + -) don't work.   In Library, Shift + J invokes View > Grid View Style > Cycle View Style (which is assigned J).  In Develop, Shift + J invokes Tools > Create New Mask > Color Range (which is assigned Shift + J).   In Library, Shift + - works, but in Develops it decrements the current Basic slider.   Note that shortcut help in Library and Develop is also wrong, showing Command + [ and Command + ] as the shortcuts. The offending lines in TranslatedStrings_Lr_nb_NO.txt are:   "$$$/AgLibrary/Menu/Photo/RotateLeft/Key=Shift+j" "$$$/AgLibrary/Menu/Photo/RotateRight/Key=Shift+-" "$$$/AgLibrary/Help/Shortcuts/RotateLeftKey=Command + [" "$$$/AgDevelopShortcuts/Rotate_left/Key=Command + [" "$$$/AgLibrary/Help/Shortcuts/RotateRightKey=Command + ]" "$$$/AgDevelopShortcuts/Rotate_right/Key=Command + ]"    

Hallo zusammen!   Leider funktioniert in LR Classic (hier 11.3.1. / Mac OS Monterey), deutsche Sprachversion, die Ordnersuche nach Namen in denen Umlaute vorkommen nicht. Z.B. Bäume, Äste, Hügel …    Wenn man jahrelang ein Ordnungssystem was über die Ordnernamen funktioniert aufgebaut hat, ist das äußerst ärgerlich.   Hat jemand eine Idee, wie man die Ordnersuche bei der Eingabe austricksen kann?   Ansonsten an die Entwickler: bitte diesen Bug bei der Lokalisierung unbedingt beheben!   Vielen Dank für jeden Tip / Hilfe.   Hubertus

LR handles camera model names containing parentheses inconsistently (e.g. "iPhone SE (2nd generation)").  The model name shown in the Metadata panel and returned to plugins via photo:getFormattedMetadata () discards everything from the first parenthesis to the end, while smart collections and the Camera column in the Metadata browser see the entire model name. I first noticed this using my Any Filter plugin. 1. Make a new catalog. 2. Import the attached photo. 3. In the Metadata > EXIF panel, observe that Model is "iPhone SE": 4. Observe that the Camera column in the Metadata browser shows "iPhone SE (2nd generation)": 5. Create a smart collection "Camera contains words 2nd generation". 6. Observe that the smart collection matches the photo. 7. Exiftool shows that EXIF:Model is:  $ exiftool -a -G -s -model IMG_2955.jpeg [EXIF] Model : iPhone SE (2nd generation)   8. Observe that photo:getFormattedMetdata ("camera

Locking the crop aspect ratio doesn't work after copying/pasting a crop or after using LrDevelopController to set a crop from a plugin.  Attempting to resize the locked crop will reset the aspect ratio to Original.  This appears to have broken in a recent version, and it makes my Any Crop plugin significantly less useful.To reproduce:1. Go to a raw photo in Develop.2. Open the crop tool and make sure the aspect ratio is unlocked (Settings > Constrain Aspect Ratio is unchecked). 3. Use the crop tool to set a long, narrow crop.4. Close the crop tool.5. Do Settings > Copy Settings, Check None, check Crop, then click Copy.6. Go to another raw photo in Develop.7. Do Settings > Paste Settings.8. Open the crop tool and lock the aspect ratio (Settings > Constrain Aspect Ratio is checked).9. Resize the crop by dragging one of the corner crop handles. Observe that the aspect ratio immediately reverts to Original (bug).10. Do Reset to reset all the photo's dev

Rotate Left and Rotate Right are not greyed out in the right-click context menu for videos in Library:   They should be greyed out.   Tested on LR 11.5 / Mac OS 12.4.

Allowed the upgrade to 11.4 LR Classic happen. Follow that by an import of some new images. Adjusted and then exported using my usual pre-set that includes "simple watermark". No watermark showing in created image. Today I experimented with exporting an image from my last imporot prior to upgrade.  No changes to any data including the export preset. No watermark showing on the exported duplicate image. Something is amiss. Opoeratingi system is OSX 11.6.6. As a workaround I created a custom watermark text. But I really like the "simple watermark" that gets the data from the copyright data field that way I don't have to worry about the mark being different than what I put in my data for each image. Is this an image data disconnect or a disconnect with system fonts? In either case I would have expected the simple watermark capability to work like before.   Regards,

I've had two sessions with Adobe support for Lightroom Classic Case ADB-25583947-S0X9.  Neither has solved a problem that's been going on for two months.  They promised another share session and CLAIM they are not able to get through to me.  All I get is a voicemail saying they've tried on both my contact numbers BUT neither phone rang, I've not been on either phone and this has happened two days in a row.  Then I get an email with a link for a share session.  I click on the link and get message that I was trying to use an invalid session key.  I WAS NEVER GIVEN A SESSION KEY, JUST THE DAMN LINK.  It seems to me that Adobe is out of ideas on trying to fix my problem and just trying to frustrate me so I will give up.  Adobe, please I hope somebody who really cares at all will read this and try to help.

When synching a number of folders, resulting in some photos from being added, and other being removed, empty photo-objects result in the library in place of the original photos. These do not show when browsing by folder, but do show when selecting All Photographs and filtering for instance by date. They result in a blank, gray photo thumbnail, that does not have a file name or any other metadata associated (therefore the assumption these are NULL). Optimizing the catalog does not improve this situation. Issue occured on 8.1 and remains on 8.2. Working with the files now becomes very slow, as Lightroom has great problems handling the NULL objects.

Als Benutzer kann ich keinen Kopiennamen im Feld "Metadaten > Kopiennamen" eintragen.Trage ich einen Namen der Kopie ein, wird dieser nicht gespeichert. Trage ich zusätzlich eine Bildunterschrift ein, dann wird der Kopiennamen und die Bildunterschrift gespeichert. Lösche ich die Bildunterschrift wieder, dann bleibt der Kopiennamen erhalten. Meine Lightroom Classic Version ist die 11.4.1   Ich habe Lightroom Classic neu gestartet, auch den PC komplett heruntergefahren und neu gestartet. Das Problem tritt trozdem weiterhin auf.  

Lightroom classic v10 (Win) does not sync aspect ratio changes to cloud. Images appear distorted (stretched) when you view them on mobile devices. Using the edit mode in cloud based Lightrooms shows that the aspect ratio change has not come through during sync.

Issue:  Lightroom Classic Version Number: V15 and V14 OS Version Number: Windows 10 Steps to reproduce: import a Photo with GPS geo-location tags the location fields (state, country, city, details) will be set automatically and shown greyed out Edit and change e.g. the city Navigate away from photo and come back (Added by Mod) Expected result:  the city shows the new value (not greyed out) and all other greyed out location fields stay with their old value derived from the GPS-coordinates.Actual result: the city shows the new value (not greyed out) and all other  location fields have their old values removed/cleared.   This is annoying if you have to adapt a lot of locations (typically CITY) where the default is not suitable. In V13 it worked as expected. I have 80,000 geo-tagged aerials where this information is crucial.

If I have an active tether session and then click on the gear icon to update the tether settings and making any changes to a live tether, hitting the return button causes LR to crash. It will not crash if I click on "Ok"   I have a team of computers using the following: LR 11.0 or later Big Sur or Catalina  Canon 6ds or canon 6dII.     This is an issue on all computers using the above set up.