Bug Reports

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.    

The SDK API reference documentation for catalog:findPhotos's criterion "fileFormat" is missing  file types "AVIF", "JXL", and "PSB".

I agree that something needs to be done to improve the Local Adjustment Presets list. I give my own presets a numerical prefix so they at least sort in some type of order that suits me. And the 'installed defaults' occupy a major area at the top of the list that then requires scrolling down to my user presets. And there are a few useless default presets that do nothing! 'Exposure' does nothing (that I can see)- no sliders set! And what does "Color" do?    

The mask panel doesn't scale correctly with LRc 12.5: all the right values are hidden. Bug appears when French language is selected. English language seems unaffected. Mac OS Ventura 13.5f

I'm not sure if its just me, but the comments icon is missing on the images in the gallery. It WAS on the collection, but disappeared after I restarted Lr. Soo now I have to click through each photo to see if they have a comment or not. Never had this issue before I updated.   Lr 11 Mac OS BigSur 11.5.2 I restarted the app once and the icon disappeared from the collections. I restarted before writing this sentence, and still the same ething.  

Mac OS - Ventura LRc Version - whatever the latest is 12.4??   I was editing some pictures and selected the print module, and LRc crashed.  Now it will not open.  I do notice that LRc is trying to open the print module, then crashes.   I uninstalled LRc, restarted Mac, shut down Mac, nothing seems to work.  If I could get LRc ignore its previous state, i.e. print module, I think it would open again.  Is the a way to clean/clear the previous state.  Maybe I will have to do a fresh install, not thrilled about that but maybe the only way to fix this.   Thanks for any assistance. 

I recently tried to verify integrity of my 50000+ images by discarding all old 1:1 previews and rebuilding new ones. However, on my most recent images – shot in 2018 and 2019 – the process of building new previews stalled at some point and the application froze. I’ve since been able elucidate which were the trouble-some mages: a couple of .mov files from 2018 and then all 2018 and later shot DJI drone video files made the process stall. No earlier video files caused the process to stall. Contrary, Lightroom reported previews to have been built. My workaround to still verify all still images was finally by excluding the 2018 and later video files from the preview building. Is this a bug? What to do about it? Building new 1:1 previews of all files are after all the best way of verifying their integrity, if I've understood things correctly. Would you need copies of any of the troublesome video file? All best from Sweden,   Bosse

Hola! Acabo de actualizar Lightroom Classic y el nuevo panel de Máscaras tiene un tamaño de fuente más grande que el resto de paneles de Lightroom, lo que provoca que no pueda ver los números de los deslizadores.     Ya he ido a Preferencias -> Tamaño de fuente -> Pequeño Pero el panel de Máscara no se hace más pequeño.  ¿Puedes ayudarme, por favor?

I cannot geotag photos in the 'Maps' module of Lightroom 8.2. Drag & Drop does nothing, and right click 'set selected photos GPS coordinates' does nothing. There is no error, no message, no metadata is updated at all. On initial startup, if I am very quick, I can drag & drop a photo successfully. But ~15 seconds after startup it stops working. My issue is identical to those posted here. https://feedback.photoshop.com/photoshop_family/topics/lightroom-8-latest-update-win10-drag-and-drop...v8.2 seemed to solve the problem for many, but it did not help me. I have provided sample photos and logs to Adobe staff already and communicated with them, but as the original thread is now marked 'solved' I have created a new one. I have address book enabled. I am on OS Windows 7 Ultimate.

Help > System Info doesn't show the amount of graphics memory (VRAM) for some Intel Macs, though Apple icon > About This Mac does.  Help > System Info doesn't report the amount of graphics memory for Apple Silicon (M1 and M2) Macs, but that's less important for troubleshooting since their graphics processors share the entire system memory.   Here's a selection of posted outputs from Help > System Info showing the issue: https://community.adobe.com/t5/lightroom-classic-discussions/sudden-slow-processing-selecting-wrong-images-loading-varied-colors/m-p/14047821 https://community.adobe.com/t5/lightroom-classic-discussions/unable-to-use-enhanced-denoise-feature-in-lightroom-classic-12-5/m-p/14025011 https://community.adobe.com/t5/lightroom-classic-discussions/helligkeit-der-bilder-und-farben-stimmen-nach-dem-export-als-jpeg-aus-lightroom-nicht-mehr/m-p/14049362#M333701  https://community.adobe.com/t5/lightroom-classic-discussions/unable-to-use-enhanced-denoi

With Lightroom 6 on Windows 7 I have exactly the same problem as described at http://feedback.photoshop.com/photosh... with Lightroom 5.4. I select a number of images and use the Export dialog, exporting to JPEG. After the export is finished I get a dialog box saying "Some export operations were not performed. The file could not be opened ()", and then lists the file names of the images that were not exported. If I delete the exported JPEGs and try again a different subset of the selected images gets exported. On average around 20 out of 70 selected images don't get exported. Watching the directory where the images are being exported with a file viewer while the export is in progress I can see that the images that are later shown in the "not exported" dialog box list are in fact being created in the target directory but are quickly deleted. I have had one example of exporting of a single image failing with exactly the same error message. I have never had this problem with version 5. I

Overnight and since installing Lightroom Classic 12.2 watermark is being incorrectly located on export. On preview before export the watermark is correctly positioned and clipped at the top. After export, the watermark has moved significantly vertically and is ruining the image. Everything was fine before running the update. Running LRC on MacBook Air with MacOS Ventura 13.1

My Lightroom Classic was auto updated this morning to v12.4.  Now when I try to connect to Photoshelter to upload images using Export the application crashes when trying to connect to the server.  There does not seem to be any issues with Photoshelter as I am able to upload images using other applicaitons.  As soon as Lightroom trys to make a connection to Photoshelter it crashes.  I can't even find a way to initiate a new log in.  Please advise if this is a bug or if there is a work around to reset the settings.

As a followup to my previous reply, I'm providing screenshots of before the watermark problem, and now after the fix. It is still looking pixelated. I doesn't seem as gray as before, but still not the quality I had before the last major LR Classic update. See Screenshots. Disappointed.

LR corrupts an .avif image when it tries to write the file's metadata. To reproduce:   1. Import this .avif: https://www.dropbox.com/s/81x4nrskg541ekj/sample-avif.2023.05.04.avif?dl=0    2. Select the imported photo and do Metadata > Save Metadata To File.   3. Observe these errors:   4. Open the file in Photoshop 2023 and observe this error: (PS has no problems opening the original file.)   Tested on LR 12.4, PS 24.5.0, Mac OS 13.4.