Bug Reports

The Accessibility fields Alt Text and Extended Description in the Metadata panel's IPTC tagset were added to LR 13.1, but the implementation is incomplete:   1. In the Library Filter bar and smart collections, they aren't searchable via Any Searchable Field, Searchable Metadata, or Searchable IPTC (like the other fields in the IPTC tagset).   2. In the SDK, the method photo:getFormattedMetadata() doesn't support the keys "altTextAccessibility" and "extDescrAccessibility".   3. The Lightroom Classic Programmers Guide should document the tagset field ids "com.adobe.altTextAccessibility" and "com.adobe.extDescrAccessibility", in two sections:   Token Patterns (page 62) Custom Metadata Tagset Example (page 77)

Local-adjustment presets saved with default tone curves won't reset tone curves back to the default values.   To reproduce on LR 13.1 / Mac OS (see the attached recording):   1. Make a Linear Gradient mask.   2. Save a local-adjustment preset named Clear.   3. Change every setting in the local-adjustment panel, including the tone curves.   4. In the Preset menu, select Clear.   5. Observe that every local-adjustment setting has been reset back its default value except for the tone curves.

If you've applied a local-adjustment preset X to a mask and then use the local Point Color tool, the preset menu doesn't change to show X (edited), and you can't update X with the current settings.   To reproduce in LR 13.1 / Mac OS (also see the attached screen recording):   1. Create a Linear Gradient mask.   2. Set the mask Exposure = -4.   3. Save as a local adjustment preset X.   4. Change any other local adjustment other than Point Color, and observe that Preset: changes to X (edited).  Resetting that adjustment to its default value changes Preset: back to X. 5. With Point Color, use the eye dropper to select a color. Then change all of its sliders to non-default values.   8. Observe that Preset: still shows X rather than X (edited), and the Preset menu won't let you update X with the current settings. This is incorrect.

"Date" is one of the filter options in Lightroom Classic's library module.  When I take a raw file (with all date fields) and "Edit in Adobe Photoshop 2024", the file that is returned to Lightroom shows up as "Unknown" in that date filter.  A "sync" operation between the old and new files is needed to restore the date information.   This has been an issue for a few months, and wasn't fixed in the last update.   Running LR Classis 13.1, Photoshop 25.3.1, on Windows 10

Apple ProRaw images taken in Apple's camera app on my iPhone 14 Pro generally work well in LrC these days, which is great. In LrC I often use the "Apple ProRaw" profile.   When I perform a panorama merge of these images, however, LrC reports that the resulting .dng file is using the profile "Apple Embedded Color Profile" but shows an exclamation mark: "Profile missing." See attached screenshots.   I wonder if this is an inadvertent result of LrC's rule that only Apple ProRaw files have the option of the LrC ProRaw profile, and that the merged file is not recognized by LrC as a ProRaw file. Can this please be improved, or is there a workaround?   Thanks, Wallace

The new Metadata panel Last Exported Date field doesn't always match the corresponding History step. This occurs when the photo is exported in one time zone and LR is currently running in another.    To avoid confusion, the Last Exported Date field should always show the date shown in the History step. This would be consistent with how LR handles capture time, always showing the time in the time zone when the photo was captured, regardless of the computer's current time zone.   See this very small catalog for an example: https://www.dropbox.com/scl/fi/8ri9yej3y9pj5k8f5e1gl/exported-date-bug.2024.05.23.zip?rlkey=dx2ppke4b0m6ono8j5h3bn1md&dl=0      Test in LR 13.3 / Mac OS 14.4.1.

In French, Window > Secondary Display > Loupe - Live has invalid keyboard shortcuts defined in TranslatedStrings_Lr_fr_FR.txt:   "$$$/MultiMonitor/LiveLoupeShortcut/Mac=Maj+Z" "$$$/MultiMonitor/LiveLoupeShortcut/Win=Maj+Z"     Localized versions of key modifiers ("Maj") aren't allowed in shortcut definitions. Those lines should be:   "$$$/MultiMonitor/LiveLoupeShortcut/Mac=Shift+z" "$$$/MultiMonitor/LiveLoupeShortcut/Win=Shift+z"   (Note the lower-case "z".)   Tested on LR 12.0.

When looking at photogaph information under metadata, the fractions shown for shutter speed are too small. They appear to be about 3 point type. Is there any way to change the style so they're more legible (e.g. 1/3) or increase their size. This is on MacOS and the font preferences are already set to large. "Use typographic fractions" is unchecked, but seems to make no difference. The screen shot below is much bigger than actual size, but these are the fractions I'm talking about.  

In Help > Develop Mode Shortcuts, LR 13.2 added Cycle Upright Mode under the View Shortcuts heading, whereas it should be under the Mode Shortcuts heading. The View Shortcuts section contains commands controlling what is displayed, while Mode Shortcuts has all the commands for controlling the editing tools such as Enter Healing Mode and Cycle Heal Type. It's inconsistent to have Cycle Upright Mode in one section and Cycle Heal Type in the other:    

The GPS-Positioning doesn't work anymore. I have installed the latest version of Lightroom Classic. When I start allocating GPS-Positions on the map, nothing happens. When I restart Lightroom it works for one or two images and then it stopps working again. I've never had any issues with GPS-Positioning before. So, I wonder what the problem is. Edit 05.02.2024: Please refer to my failure description in my comment below..... I am on LRC-Version 13.1 and MAC OS 14.3!

Running 13.1 on intel iMac, Sonoma.  Grab the eyedropper for white balance and the loupe window gets stuck on the first color it touches.  Still can pick different spots to change WB, but the loupe never changes as you move around image.  This is new since Sonoma upgrade.  Restarts, etc., did not resolve.

I defined several mask presets early in LrC 12, primarily settings for Clarity and Saturation and combinations of the two. After upgrading to LrC 13.0.1 last week, I noticed something that seems strange. While the history for images where I used one of those presets shortly before upgrading, the history panel shows something like “Mask1: Update Refine Saturation Adjustment” (which make sense, but isn’t as clear as using the name of the preset like “Mask1: Clarity +50” or “Mask1: Clarity +50 Saturation +50” would be IMO), but if I apply any of these presets now (after upgrading to LrC 13.0.1), the history panel shows “Mask1: Update Point Colors” which seems completely wrong, since I have never used the new point color either globally or in a Mask.  I also tried creating a new, identical preset, with a different name, and when I apply it the history panel shows “Mask1: Update Point Colors” just like with the preset created earlier. I've attached a couple of my mask presets, but I se

Issue: The Color Mixer Target Adjustment Tool does not choose the correct color(s) for H/S/L adjustment when HDR editing is enabled.    It should choose, and then adjust, the color/two-color mix that is clicked on. However, that selection seems to be skewed in HDR-enabled images. For example, blue sky will register only as magenta if using the target tool. This problem occurs in both non-HDR and HDR areas of an HDR-enabled image.   If HDR editing is then disabled for the same image, the target adjustment tool will identify and adjust the appropriate colors when going to the exact same spots.   Video attached of incorrect behavior in HDR editing mode. The image used in the video is a JPG, but I have confirmed this behavior also occurs on a DNG.   --   Lightroom Classic v13.2; MacOS v14.3.1; MacBook Pro M1 2020

HiThere is a small error in Polish translation of word "Contains" in Text search menu /see attached photo/.In Polish it should be "Zawiera" not "Operator Contains" i think 😉Wersja Lightroom Classic: 13.1 [ 202312111226-41a494e8 ]Ustawienie języka: plSystem operacyjny: Mac OS 14Wersja: 14.2.1 [23C71] ThanksPaweł Słowik

Since the latest version of Lightroom 3.0, it has been introduced that a photo loads faster than its actual colour. Sometimes I have to wait a second after opening a photo to get the correct colouring. This is very annoying as it's hard to focus on comparing the photo against the previous one. Is it possible to turn this off somehow? I would prefer to wait even a second for a photo to appear already with the correct colour scheme rather than initially having to preview a false version.

See screenshot. (1) The cursor was on the sky (trust me!). You can see that the LAB values for the A and B channels (shown below the histogram are zero (as they are throughout the image) - not surprising because the image has been changed to B&W. But the histogram and the image clearly show a blue sky. (It's blue because I've applied a mask for the sky with a curves adjustment in the Red and Green channel which makes it blue).  But why do the LAB values (which are zero in A and B) not reflect the histogram and the image? (2) Why would LR allow colour in a B&W profile? I would have expected that applying such a profile would remove all colours? Educate me please!  P.S. I'm wasn't trying to create this blue sky. It's just a hangover from the original colour edit after applying the monochrome profile. And yes, I know how to get rid of it. . LR Classic 13.0.1. on Mac Mini 2018

Raw images with a custom camera profile not look correct when synced from Lightroom Classic to the cloud.  This is r-e-a-l-l-y inconvenient for updating my Adobe Portfolio.  The images look lousy in lightroom.adobe.com, LIghtroom Mobile (Android and iPadOS).  The workaround is to export as jpg, and then reimport into LrC and sync the jpg to the cloud - but that is unmanageable for more than just a few images.  

Adobe Photoshop Lightroom Classic 13.0.1 Release (Camera Raw 16.0)Windows 10 version 22H2 (Build 19045.3693)   I am using two calibrated monitors, laptop + external.LR's Secondary Window is on the external monitor, showing the Survey view.    LR on the primary monitor is in the Develop module, with two near-identical images selected on the filmstrip. The image with focus on the film strip becomes slightly desaturated on the secondary monitor - the image next to it is shown correctly (!), so this cannot be an issue with monitor profile.   The saturation changes are not immediate or simultaneous. Times below are guesstimated. 1) Focus changed on filmstrip -100ms delay- 2) Image that lost focus regains saturation on the secondary display -100ms delay- 3) Image that has gained focus loses saturation on the secondary display   Same behaviour if three images are selected on the filmstrip. Exiting LR and restarting makes no difference. Problem is not present in t

Sync Metadata clears the Altitude field of all selected photos when just GPS (but not Altitude) is checked (incorrect). Pasting the clipboard into the GPS field also clears Altitude (incorrect).  A metadata preset with just GPS checked also clears the Altitude field (incorrect).   The Altitude field shouldn't be modified when copying just GPS. This is clearly not designed behavior, since otherwise there would be no point in having a separate Altitude checkbox in the Sync Metadata and Metadata Preset dialogs. The bug was introduced somewhere between LR 6.14 and 9.1.     To reproduce on LR 13.2 / Mac OS 14.4.1:   1. Download and open this small catalog: https://www.dropbox.com/scl/fi/fpom4b2bgdhmfdfxjlbhr/copy-gps-bug.2024.04.29.zip?rlkey=gssyo3jfgvpih24t2lcaom1h2&dl=0    2. Observe in the Metadata > Location panel that both photos have non-blank GPS and Location fields.   3. In Library Grid view, select both photos, with 1.jpg most sel

After I copied all my photo files in Lightroom to a new PC, all the photo files have been marked with an exclamation mark in the upper right corner. When I mouse over the exclamation mark, the message appears: "Error writing metadata". When I click on this mark, I get the following message: "There was an unknown error while writing metadata to this photo. Retry?" Below the message there are two options I can click: "Import settings from disk" and "Retry Metadata Export". I don't understand what Lightroom is trying to tell me, nor what the consequences are of clicking these two options.

Dear all   Windows11 LrC 13.0.1   Step to reproduce.    1) Activate GPU. Select several photos with development. Export them. Look at your resource monitor for GPU   2) Deactivate GPU. Restart Lightroom. Select the same photos. Launch the same export    3) A warning message tells you that the GPU is deactivated and ask you if you want to activate to speed up export. Press cancel to keep it deactivated. Look at you resource monitor for the GPU. The GPU and GPU memory is used anyway    Kind regards

I am attempting to tether a Nikon Z9 using Lightroom Classic, but LRC can't detect the Z9.  I am able to download pictures from the Z9 to LRC all day long, and LRC successfully detects my Nikon D850 for tethering.  Nikon Z9 firmware is 4.0.  Mac iOs is 13.4.1.  LRC release is 12.4.  All are up to date.  Any ideas?

The modifiers Ctrl, Cmd, and Opt are incorrectly localized in the shortcuts Help for a number of commands, in all languages. For example, the German help shows the shortcut for Cycle Upright Mode as Ctrl + Tab, but it should be Strg + Tab.   In the listing that follows, lines have the form:   incorrect shortcut (correct shortcut) command (TranslatedStrings id)   For example:   Ctrl + Tab (Strg + Tab) Develop Module > Transform Upright > Cycle Upright Options ($$$/AgDevelopShortcuts/circle_upright_mode/Key)   This was generated by the Any Shortcut command in LR 13.1:   ---------------------------------------------------------------------------/Users/john/Desktop/plugins/anyshortcut.lrdevplugin/TranslatedStrings_Lr_en_US.txt:   Ctrl+Shift+Enter (Control + Shift + Enter) Workspace > Secondary Display > Loupe - Locked ($$$/MultiMonitor/LockedLoupeTooltip/ShortcutWin)Ctrl + Tab (Control + Tab) Develop Module > Transform Upright > Cyc

A keyboard shortcut assigned to Go To Folder In Library via TranslatedStrings will stop working after you go to Develop and back to Library.  This happens on LR 13.2 / Windows 11 but not Mac OS 14.4.1.   To reproduce:   1. Create the file C:\Program Files\Adobe\Adobe Lightroom Classic\Resources\en\TranslatedStrings_Lr_en_US.txt containing this one line:   "$$$/AgLibrary/Menu/Photo/GoToFolderInLibrary/Key=Cmd+Shift+y"     2. Start LR.   3. Go to Library Grid view and select All Photographs.   4. Select a photo and type Ctrl Shift Y. Observe that the current source correctly changes to the containing folder in the Folders panel.   5. Go to Develop.   6. Go to Library Grid view and select All Photographs.   7. Type Ctrl Shift Y and observe that the current source incorrectly remains All Photographs.   8. Restart LR.   9. With the same photo selected, type Ctrl Shift Y and observe that the current source correctly change

When the Fetch Altitude For Coordinates button in the Location tagset of the Metadata panel is pushed while in the Map module, it correctly sets Altitude but it doesn't display it in the Metadata panel. This appears to be an old bug filed in 2019 that didn't get migrated from the old feedback forum: https://community.adobe.com/t5/lightroom-classic-discussions/map-module-altitude-of-the-points-si-0-in-the-gps-coordinates-of-the-photos/m-p/10313076#M136897    To reproduce on LR 13.2 / Mac OS 14.2.1:   1. In Library, select a photo that doesn't have any assigned GPS coordinates.   2. In Map, drag the photo to the map. Observe that it gets assigned GPS coordinates but not Altitude (correct).   3. Click the Fetch Altitude For Coordinates button. Observe that the Altitude field remains blank (incorrect).   4. Go to Library and observe that the Altitude field is filled in (correct).   5. Go back to Map and observe that the Altitude field is filled in (correc