Bug Reports

If I make a gradient mask adjustment, then select subract using brush, the left and right bracket keys no longer manage the brush size but instead increase or decrease the star rating of the image.  The brush mask itself works fine with the bracket keys changing the brush size.  It seems only to happen when the brush is being used to modify an existing mask, although I did not test beyond the example cited.  Is there something I'm doing wrong or is this a true bug?

Broken: LrC 12.1 Working: LrC 12.0.1 OS: Win11 22H2 GPU driver: Nvidia gameready 527.56 (disabling GPU acceleration does not resolve the issue)   32bit TIFF files (such as 3D renders, astro stacks, HDRs from third party tools, etc) are not being rendered correctly in Lightroom Classic 12.1. The bug is new in 12.1, 12.0.1 handles them correctly/as previous versions did.   Here's how 12.0.1 handles this file:   Here's the same file, with the same develop settings and export settings, from 12.1:   The highlights and shadows adjustments simply flatten the contrast of the image. Additionally, in 12.1 the white balance slider is now relative(-100 to +100) instead of absolute (showing a kelvin temp). As if 32bit TIFFs are being treated as non-raw/non-linear files or something like that?   Here's a sample TIFF: https://drive.google.com/file/d/1WvqO09WhL3QtTVw4SEaCost6ChcwKJYX/view?usp=share_link   Steps to reproduce: Load any 32bit tiff, the sample file linked

Issue: Attempt to add Mask by Objects switches to different work space on Mac   Lightroom Classic version: 13.0.1 [ 202310121438-d2af310c ] macOS 13.4.1   Step 1: MacBook Pro with multiple Spaces active, Lightroom Classic has been set to full screen Step 2: Add New Mask and select the Objects option Result: MacBook switches to another work space and Lightroom Classic is no longer visible. Attempts to go back to Lightroom results in immediate switch to another work space. Only way to make it stop is to get out of full screen mode.   Expected result: Lightroom Classic should stay on the screen and allow mask to be added

I'm a Lightroom plugin developer, one of my products is The Fader (https://www.capturemonkey.com/thefader/), which can crossfade between different develop settings.  It operates on normal sliders, but it can also create smooth transitions between tone curves.In order to operate, it needs support from Lightroom to set sliders and tone curves.  The SDK provides few methods for this:1) LrPhoto:applyDevelopPreset, which works almost, but it has problems updating the display when GPU is enabled: https://feedback.photoshop.com/photoshop_family/topics/lightroom-sdk-photo-applydeveloppreset-doesnt...2) LrDevelopController.setValue, which has been my solution since Lightroom 6.0.  It has a few quirks, but it did get the job done.  ToneCurvePV2012 (/Red/Green/Blue) were not mentioned specifically on the documentation, but they were working in LR 6.0-6.8, something along the lines of:LrDevelopController.setValue("ToneCurvePV2012Red", {0,0,40,50,200,220

I've had a problem getting my collections to sync for over three months now. Lr Classic used to magically sync my dozens of collections, and over 5,000 files, and did it without any hiccups for several years. Then, suddenly in late July it just stopped working. It would just hang trying to update any new items in any collection, and still does.   I have called support, opened two separate tickets, and followed everything they asked me to do, plus everything ever mentioned here at least three times, and still there's no fix. I even exported a large collection of my portfolio as DNGs, created a new Adobe account, created a new macOS account so everything would be in a clean state, and tried syncing about 1,000 of my photos from that account. LrC still got stuck with 200 photos remaining to sync. Why can't the entire sync database just be reset so we can just start from scratch?   I'm frankly at wit's end. I totally fell in love with LR Classic sync, and used it across my macOS

After LR suggests addresses for a photo, editing one of the location fields erases the other suggested location fields. This bug was fixed in LR 7.5 in 2108, and the fix worked through 10.4. But then 11.0 broke it again, most likely another bug in the metadata caching in <catalog>Helper.lrdata introduced in LR 11.0.   I never noticed this, and probably many others didn't notice this, because they were using the Commit Locations command of the Any Tag plugin, which is required to work around other, unrelated bugs with suggested addresses.   To reproduce in LR 13.0.1:   1. Drag a photo with no location metadata to the map and wait for LR to fill in the location fields with a suggested address:   2. Change one of the suggested fields or a blank field (e.g. Sublocation):   3. Select another photo in the filmstrip and then select the original photo. Observe that the suggested fields have been cleared:    

It crashes when I try to startup the program soo I am effectively locked out from LR Classic    MacBook Pro M1 with 34 MB memory, Latest version of Sonoma. 

Although in prior versions it did, Lightroom Classic does not automatically reopen when I have it opened and want to swwitch catalogs using File>Open Recent> [Select Catalog].  It just shuts down.  When I manually reopen it chooses the catalog I last selected, but this used to happend automatically without manually reopening it.  Running this from Macbook Pro M1 laptop while running OS X Monterey 12.5.1. Any suggestions are apprecited. 

Panic!!! Windows 11, quite powerful PC with dedicated GPU, i7 13th gen 32GB RAM.I updated to LrC v13 and updated the catalog upon opening. Now if I import a NEW photo and go to the development module, LrC crashes. no problem with photos already imported.

Getting the below error then lightroom just shuts down, i have uninstalled the app and reinstalled still happen, any help would be greatly apprecaited?  

With the new Lightroom Classic 13 update, on windows ten, with LR set to have the panels reversed for left-handed people (thanks for that, Adobe, I love it) - when in compare view and changing the flag status, almost every change of flag status on the RIGHT image is applied to the left image instead. I did manage to get ONE reject to apply to the right image, but every other one was applied to the left (removing it from view, with a flag filter set to unflagged). Flag changes to the left side work as expected. This is new with the 13 update.

The menu command Tools > Point Color incorrectly uses the same TranslatedStrings keyboard shortcut entry as Tools > Fringe Color Selector, likely a copy/paste error. To reproduce:   1. Add this line to TranslatedStrings_Lr_en_US.txt:     "$$$/AgDevelop/Menu/View/DefringeColorSelector/Key=Cmd+y"       2. Observe that ⌘Y appears as the shortcut for both menu commands:   Tested on LR 13.0 / Mac OS 13.5.1.  

The Metadata browser's Keyword column in hierarchical view shows inconsistent counts for directly assigned keywords containing child keywords.     My personal catalog has many, many such instances of this. They're easy to find: Configure the Metadata browser with two Keyword columns, the first with View > Hierarchical and the second View > Flat. For example, "Dubrovnik" shows a blank count in Hierarchical and a count of 79 in Flat:   To reproduce:   1. Download this tiny catalog and open it in LR: https://www.dropbox.com/scl/fi/hckz8qbeqk3nynnrtbojj/keyword-column-bug.2023.07.30.zip?rlkey=ymrubwdaxhhilg29haycrf2v8&dl=0   2. Do File > Library Filters > Enable Filters.   3. In the Library Filter bar, click Metadata.   4. Remove the last two columns, leaving two columns.   5. Configure the second column to Keyword / View > Flat, the first column to Keyword / View > Hierarchical.   6. In the Keywording panel, set Keyw

The method photo:getFormattedMetadata() supports the key "trimmedDuration", but it isn't documented in the API Reference.  For example:  

The SDK documentation of photo:getDevelopSettings() in LrPhoto has a typo:   Orientation: (string)   should be:   orientation: (string)   (lower-case "o").

When looking at the Metadata for a photo while in LrC, clicking on the filter button beside some of the metadata fails to successfully apply the appropriate filter. The problem seems to be that the action populates the first column of the metadata filter criteria with the wrong metadata. For example, I click on the filter button beside the aperture of an image in the metadata for that image. The first column of the metadata filter then gets populated with the various possible lenses. The resultis that the results window just shows "Loading" and the process is hung. Clicking back on the desired folder populates the window without the filter. The same problem can be repeated by selecting the small filter button for shutter speed. Again the first column of the metadata filter is populated with lenses and the filter fails in the same manner as described above. I am working on a Windows machine with the latest build of LrC. My OS is Win 10 and is up to date.

When filtering in the Collections panel, right-clicking a collection set and doing Create Collection puts the wrong collection set in Inside A Collection Set.   To reproduce:   1. Make a new catalog.   2. Make two collection sets, XXX and YYY.   3. In the Filter Collections box, type YYY and then select YYY:   4. Right-click YYY and do Create Collection.   5. Observe that it incorrectly shows Inside A Collection Set: Smart Collections rather than YYY:   6. Clear the Filter Collections box, right-click YYY again, and do Create Collection.   7. Observe that it now correctly shows Inside A Collection Set: YYY.    Tested on LR 12.4 / Mac OS 13.4.          

LR 12.3 added support for file formats JPEGXL (JXL) and AVIF but forgot some things:   - The smart-collection criterion File Type is missing JXL and AVIF as values.   - The Metadata panel's File Type field is blank for JXL and AVIF photos.   The Metadata browser's File Type column does show JXL and AVIF. (And in case you're wondering, HIF files show up as file type HEIC in all these places.)

Auto Sync copies a previously made crop, even though the Auto Sync was off when the crop was made.  To reproduce (see the attached screen recording):   1. Make a new catalog and import three raws.   2. Do Preferences > Performance > Camera Raw Cache > Purge Cache   3. Edit the first raw in Develop.   4. Open the Crop tool.   5. Grab the lower-right corner of the crop and move it up, rotating the photo about -30 degrees.   6. Click the Close button in the Crop tool.   7. In the filmstrip, shift-click the third photo to select all three.   7. Click the Auto Sync toggle on the Sync button.   8. Move the Exposure slider to about 3.5.   9. Observe that both the Exposure change and the crop are copied to the other two photos.   10. Observe that the History for the other photos shows the change to Exposure but not Crop.   Tested on LR 12.1 / Mac OS 12.6.1.   See the original report here: https://community.adobe.com

In the Polish help and tooltips for keyboard shortcuts, Powrót is used three times and Enter/Return twice. If you opt to use Enter/Return, then be sure to use Enter or Return consistently on Windows (currently Enter is used once, Return once).   Tested on LR 12.5.   From the Any Shortcut plugin's Analayze command:   LR screenshots:                

On Windows 11, the SDK's LrSystemInfo.summaryString() and .osVersion() report the wrong version of Windows:  "Windows 10 - Home Premium Edition (x64)" "Windows 10 - Home Premium Edition"  This makes it difficult for a plugin to work around the Windows 11 SDK bugs. Help > System Info also reports Windows 10 rather than Windows 11: According to this Dell support article, there appear to be many places where Windows 11 reports itself as Windows 10, which Microsoft labels "as-designed" (or "feature not a bug").  One way to differentiate Windows 10 and Windows 11 is by looking at the version: 10.0.2200 and greater is Windows 11.  Unfortunately, the SDK doesn't report the version.

My system has worked perfectly for many years, but I’m encountering strange issues on import in Lr Classic that have recently plagued me.    When importing via a plugged in thunderbolt cable into my R5s: - image previews no longer load into the thumbnails, or will load dramatically slower and one at a time. (Whereas they used to snap into each empty thumbnail cells immediately) - sometimes it will show no photos to import (which was frightening the first few times to see). I’ll cancel and reopen the import prompt which usually works after the second or third try. - sometimes import window will show photos from other shoot days but not my most recent images. I’ll cancel the import prompt and reopen. Often it’ll all load in after a few tries. - If I get through these issues, the most difficult part is actually importing. Import can take 5 minutes before starting, if I’m lucky. (It used to start within 10 seconds.) Two out of three times the import completely fails to start.&nbs

I'm using a MacBook Air, Ventura 13.5 OS. LrC crashes once I hit enter on a "tether capture". Tried rebooting, reintstalled LrC, even tried multiple older versions to no avail. I'm using a Canon 5D Mk III. Worked fine on Friday. Multiple crash reports were sent.    Ended up using my older MacBook with Monterey 12.6.8 with LrC 12.5... works fine. 

Hello,   I would like to report a translation mistake in the french version of Lightroom Classic (in version 12.5 but it could be present in other versions, didn't verify) : on the splash screen, "Reading preferences..." is translated in "Préférences de lecture..." which is a misinterpretation ; the correct translation is "Lecture des préférences...". (Same sentences in english, but different meanings in french). 

Editing an existing smart collection saved with the criterion "Aperture is greater than f /1.0" doesn't properly display "f /1.0" on Mac. It works correctly with values less than 1.0 and greater than or equal to 1.05.   To reproduce:   1. Create a smart collection with the criterion "Aperture is greater than f / 1.0".   2. Right-click the smart collection and do Edit Smart Collection. On Mac, observe that the value field is incorrectly blank:   But on Windows, observe that the value field still shows the correct value, f /1.0:   Tested on LR 12.3 / Mac OS 13.4 and Windows 11.