Bug Reports

Hi, When trying to synchronize folders, Lightroom Classic treats differently folders having a special character (e.g., an a vowel with an accent). For example, on the folder "Mickaël", all pictures are treated as missing, and need to be removed then reimported. See screenshot below: Conversely, folders without special characters are treated normally. Note that this happens on all folders having special characters, which means around 12,000 photos are affected. Needless to say, I am not interested in doing a massive synchronization at this stage because of this problem.   I recently imported my catalogue from Lightroom 6 to Lightroom Classic CC. My photos are stored on a Synology NAS and mounted as SMB remote folders.   Thanks

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   Auto-Stack By Capture Time sometimes stacks photos whose capture times are separated by more than specified by Time Between Stacks.  To reproduce:   1. Create a new catalog.   2. Make a copy of a raw.   3. Import the raw and its copy into the catalog.   4. Select the copy, do Metadata > Edit Capture Time, and change its time to one year earlier.   5. Do Photo > Statcking > Auto-Stack By Capture Time, with Time Between Stacks set at the default 0:08:00.    Observe that the the two photos are stacked, even though their capture times are separated by a year:     Doing Metadata > Save Metadata To File followed by Read Metadata From File and then auto-stacking doesn't avoid the bug.   I've observed that sometimes exporting the catalog as a new catalog avoids the bug, sometimes not.   A couple other

I have been doing bird photography and importing hundreds of images, and I rely on Embedded Previews for my intial triage/culling. I have ALL of the options for replacing embedded previews disabled (Idle time, etc). Yesterday, I imported 1400 photos into my Lr 11.2 catalog, and Lr built Standard Previews for every file. Sometimes, it leaves me a few Embedded Previews, but this is maddening.    The Embedded Preview feature is ideal for those of us who need to triage quickly, including viewing images at 1:1.   Not sure if there's something I'm missing, or if this is a bug in Lr 11. 

Issue:  Lightroom Classic Version Number: 13.1 OS Version Number: Windows 11 23H2 Steps to reproduce: Create a publishing service, e.g. publish to harddrive Manually put a single video into the corresponding collection Hit the publish button   Expected result: Video gets published to harddriveActual result: A warning dialog appears saying "This collection can't be updated. An internal error occurred: assertion failed!"   This took me a while to figure out. I'm a long time user of Jeffrey Friedl's Folder Publisher and all of a sudden it started failing with the above message. After quite some testing I found out that it didn't even get as far as starting the plugin, but failed on the collection itself. Then found out that it occurs only when I add a video and also for the regular publishing service that comes with Lightroom. I tried different video formats, doesn't seem to matter.  

When a Mac computer is set to a primary language and region not supported by LR (e.g. Hungarian/Hungary), and LR's Preferences > General > Language is set to Automatic (Default), LR fails to read the keyboard shortcuts in the file TranslatedStrings_Lr_en_US.txt even though the LR user interface is displayed in English and the English shortcuts are active.   This causes confusion for users of my Any Shortcut plugin, a disproportionate number of whom are running LR in unsupported languages with non-English keyboards (and thus want to adjust the English shortcuts that don't work well on their keyboards).   Tested on LR 13.2 / Mac OS 14.2.1. I haven't tested Windows, though it's very possible the same bug occurs there.  To reproduce:   1. In Mac Settings, General > Language & Region, set the Primary Language to be English (US) and the region to be United States, and restart the computer if the language and region get changed.   2. Create this

En el filtro por nombre de Biblioteca->Carpetas ignora los textos más allá del caracter 32.  PROPUESTA: Permitir filtrar por cualquier texto de los nombre de las capetas.

When searching for specific folders in the folder section of the Library module, the search engine is generally case insensitive, except when using letters with accents. Latest version of LRC used (13.2). Steps to reproduce: 1. Having a folder named "Saint-Étienne" (capital E with accent) 2. Search for "étienne" 3. No result found 4. Search for "Étienne" 5. Results found      

LR 13.2 won't save the current flag to XMP if the field XMP:Pick is missing from the file and no other metadata field has been changed in the catalog. To reproduce:   1. Download and open this tiny catalog: https://www.dropbox.com/s/1yvu2uib5uup416/pick-bug.2024.03.10.zip?dl=0   2. Select the one photo and do Photo > Set Flag > Flagged. Observe that the pick flag now appears on the thumbnail but Metadata Status is still Up To Date (incorrect)   4. Do Metadata > Save Metadata To File.   5. Run "exiftool -xmp:pick 7.jpg" and observe there's no output (incorrect).   6. Change the caption to "Hello world!". Observe Metadata Status is now Has Been Changed.   7. Do Metadata > Save Metadata To File and observe Metadata Status is now Up To Date.   8. Run "exiftool -xmp:pick 7.jpg" and observe the correct output:     Pick : 1       9. Do Photo > Set Flag > Unflagged and observe Metadata Stat

Since LR Classic v13.0 & 13.0.1, I cannot work in a collection anymore due to systematic crashes.

keyword:setAttributes() can't change the case of a keyword's name, e.g. from "a" to "A", even though the user can do that in the UI. To reproduce in LR 13.0.1 / Mac OS 14.1:   1. Download this tiny catalog:  https://www.dropbox.com/scl/fi/r17o9uf94v3plsr4i5yxs/keyword-name-bug.2023.11.29.zip?rlkey=wnvyv921uso57zqsq75w83eds&dl=0   2. Copy the script "keyword-name-bug.lua" from the catalog folder to the Scripts subfolder in the Lightroom settings folder.   3. Open the catalog in LR. Observe it has one keyword named "a".   4. Do Scripts > keyword-name-bug, which should rename that keyword to "A" and display "true". But observe the rename fails and it returns "false" (incorrect).   5. In the Keyword List panel, right-click the keyword, do Edit Keyword Tag, and change its name to "A", demonstrating that users can change the case of keywords.   6. In the Keyword List panel, rename the keyword to "x".   7. Do Scripts > keyword-name-bug, and ob

Lightroom Classic 13.2 (and also some erlier versions) Camera Raw 16.2MacOs 14.2.1   Hi,I found that sometimes Lightroom refused to export with an "unknown error"Other similar images did export.After some comparison I found out that when texture was applied to an image the error occurs.  

It is a display problem in the Japanese version   Click the bottom of the histogram to create a smart preview.There is an error in the message displayed at that time. After the capacity MB, there is "つ" left."つ" is a classifier for expressing 1 to 9.We don't use "つ" to indicate capacity.It seems that the expression used in the previous version remains even after the specification change.   I think that "つ" is difficult to use as a unit to represent the number of smart previews, so I think that "個" is better.

function ConfigDialogs.CameraFilm(f, propertyTable) return f:group_box { title = 'Adding Camera and Film', fill_horizontal = 1, --------- Camera -------- f:row { f:static_text { title = "Camera Name:", alignment = "left", }, f:edit_field { alignment = "left", width_in_chars = 20, immediate = true, value = bind "CameraName", },…. width_in_chars = "11",This works on MacOSX (and it should not) and fails on Windows (correct)  

The Adobe Stock publishing service uploads a keyword even if Include On Export is unchecked. To reproduce:   1. Create the keyword "Test", unchecking the attribute Include On Export.   2. Apply Test to a photo.   3. With the photo selected, select Will Export and observe that Test is not displayed.   4. Drag the photo to Submit To Adobe Stock under the Adobe Stock publishing service, select Submit To Adobe Stock, and click Publish.   5. When asked, click Yes to Go To Adobe Stock To Complete Your Submission And Start Selling.   6. Observe that Test appears in the Keywords for the photo on Adobe Stock: See the attached screen recording.   This bug doesn't occur with other publish services, pointing the finger at the Adobe Stock plugin.   Tested with LR 11.0.1 / Mac OS 11.6. 

When Will Export or Keywords & Containing Keywords is selected in the Keywording panel, LR sorts the keywords case-sensitively, whereas it should sort ignoring case.   Tested in LR 13.0.1. To reproduce:   1. Add these keywords to a photo: apples, Bananas, cats, Dogs   2. Observe the keywords are correctly ordered case-insensitively with Enter Keywords and in the Keyword List panel:   3. Observe the keywords are incorrectly ordered case-sensitively in Will Export and Keywords & Containing Keywords:        

The Help for Library and Develop keyboard shortcuts shows "Shift" instead of "Umschalt":     These two lines in TranslatedStrings_Lr_de_DE.txt should be corrected:   "$$$/AgLibrary/Help/Shortcuts/SetColorLabelsShiftKey=Shift + 6-9""$$$/AgLibrary/Help/Shortcuts/SetRatingsShiftKey=Shift + 1-5"    

[Updated 2024-01-03 to include the problem with transform().] In Mac LR 13.1, plugins cannot set or change the selected items in a simple_list() control; when they try, the operation() and transform() callbacks of the binding also stop working. This worked up through LR 13.0.1, and it continues to work in Windows LR 13.1. The bug impacts several of my plugins, including the popular Any Filter.To reproduce: 1. Download and install this plugin:https://www.dropbox.com/scl/fi/ti1rgaf4v43arshtncuus/simple_list-bug.lrdevplugin.2024.01.03.zip?rlkey=au86pe5yb7ynaoiqfmjlkqr51&dl=0 2. Do File > Plug-in Extras > simple_list-bug. 3. Observe that no item in the simple_list() control is selected (incorrect, "2" should be selected): 4. Click item "2" and observe that the operation() and transform() callbacks of the binding are invoked: 5. Click the Set Selection button, which tries to set the selection of the simple_list() to "1", and observe that the sele

Just aquired newly released Canon RF24-105mm F2.8 IS USM Z lens. A profile for correction for this lens is on the list of lenses added in December 2023.  Applying the Distortion Correction profile in LR Classic and Photoshop Camera Raw produces edge artifact instead of improving distortion. At the edges, the image shows a pattern of stripes perpendicular to the edge and extending about 5% inward. This artifact occurs in LR 13.1 and Photoshop 25.3.1 with Camera Raw 16.1. It disappears if I deselect Profile Corrections. It is not present when I view the image with other software like the Windows photo viewer FastPictureViewer or in Canon's Digital Photo Professional, so it's specific to LR Classic or Camera Raw 16.1 with Distortion Correction turned on and not due to a problem with the CR3 raw files. If I force use of a profile for a different lens, the artifact disappears. That is perhaps a useful verification that the native profile is bad, but using a mismatched profile isn't goi

  Hello. What exactly is "Debug Capture Time"?

There appears to be a bug affecting all recent versions of Lightroom on high-DPI Windows devices. It affects both CC and standalone versions, up to and including the current version (2015.6.1).The issue is that when using the white balance dropper tool in the Develop module, the target location Lightroom uses does not correspond exactly to where the point of the dropper is located. Specifically, it seems to reference a position about 5 or 6 millimetres above the point of the tool.The issue also affects the manual defringe dropper in the Lens Corrections panel. Other local develop tools seem not to be affected (brush, spot healing, HSL/Color/B&W picker, etc.).To be clear: the issue affects Lightroom when the device is used in standard desktop mode with a regular mouse as the pointing device. It is not an issue with the touch screen, the pen or Lightroom's touch mode.The problem is described in detail with screenshots here (in the original post and in my reply):https:/

I would like to get some feedback on  the follwing issue.   USed H/W: HP Z6 G4, 2 CPUs Intel 6136 Xeon3.0 12C 128 Gb of RAM GPU Nvidia RTX 4070 ti Super Primary disk 500Gb SSD and 2TB SSD gen 5. Windows 11.  64 WKST Plus   Issue: DeNoise , "Lightroom not responding"   Example: Denoising a Nikon RAW file from Z9.  (Size ~55Mb) Lightroom Denoise estimates a 7 s process time. This fits well with the time the GPU is active and staying at about 90% usage. Once the GPU stops after 7s the systems seem to be idling for time of 2 minutes before it has completed the task and returned a DNG file to my disk. During these 2 min the message the message "Lightroom Framkalla Not responding" apperas at the top of the Lightroom window.Have also run a test by selecting 16 RAWfiles and recorded times. Result The GPU runs for 4 min and 36 s ( It seems to run one RAW-file at the time at a similar GPU time of operation (7 sek) but also a short paus between each  RAW files p

The tone curve is broken in Lightroom Classic 13.0. You can move the black point vertically and horiziontally at the same time, this however is no longer true for the white point. The white point only allows you to go in one direction at a time. So if you were hoping to bring down the highlights while also bringing up the brightness, it's no longer possible.

In the latest version of Lightroom Classic in the watermark panel. Click Italic and you get bold and visa versa. Noticed this after the update to the new version. My water mark had gone from Italic to bold. (Windows)

I have a 13-inch M1 2020 macbook pro. It's fully up to date with venture and lightroom classic is fully up to date. When I go to tether capture, before the camera is even plugged in, lightroom completely crashes when i hit "okay"  I restarted the computer, restarted LR, restarted creative cloud, updated permissions, gave full disk access, uninstalled and reinstalled LR, all of it. It still does the same thing.   It's not the camera because I don't even have it connected when I'm launching tethering. I've tried using my hard drive and external hard drive as the location, but there's always the same end result.

System: Mac M1 Air 16gb/512gb OS: Sonoma 14.3.1 LRC Version: 13.1 Release ---------------   Three Issues: 1) I have a preset folder with six custom presets.  When doing multiple exports using the batch export feature, LRC often doesn't launch the same number of processes as there are presets selected.  I select 6 presets and it will only do 4 sometimes, 5 others.  Sometimes it does all 6.  I have to examine the export folder, see which ones it missed, and go back and re-export the ones it didn't do.  Annoying.   Potential Fix:  If LRC can't do all of the processes because of system limitations (I don't know why on a Mac M1 that would be the case), at least inform the user which ones are being done and which are not.  Perhaps a loop to do sets consecutively with proper UI notification would be a good approach.   2) When doing multiple exports, a dialog comes up for each process, "Preparing to export".   "number of processes - 1