Bug Reports

I'm testing with a Canon RAW files from a EOS 7D with EF 70-200 L IS USM lens.I have set the Develop Default Setting for this camera to enable "Remove Chromatic Aberration" and "Enable Lens Corrections".1) When I import the files and have Build Previews set to "Minimal" the 2 check boxes ("Remove Chromatic Aberration" and "Enable Lens Corrections") are checked and the correct Make, Model and Profile are found.2) When I import the files and have Build Previews set to "Embedded & Sidecar" the 2 check boxes are checked BUT Make, Model and Profile are "None". HOWEVER if I click on the photo, go to the Develop module, click on a different photo in the filmstrip then click on the original photo the correct Make, Model and Profile are displayed most of the time.I also noticed if I click Auto tone or if I adjust a slider and then hit Command-Z then the correct Make, Model and Profile are displayed.

In the Map module, right-clicking a zoomed-out map bubble for multiple photos and doing Set All To The Same GPS Coordinates doesn't work. To reproduce:   1. Drag two photos on the map very close to each other.   2. Zoom out until there's one bubble that includes both photos.   3. Right-click the bubble and do Set All To The Same GPS Coordinates.   4. Zoom back in and observe that the two photos still have different locations.   5. Click on each photo in turn and observe they have different GPS coordinates in the Metadata panel.  (And observe that the bug displaying multi-line fields in the Metadata panel is still unfixed after a year.)   See the attached screen recording.   Tested on LR 11.0 / Mac OS 11.6. 

I have a 300-image (NEF) folder where I highlighted all images, turned on Auto Sync, then adjusted the sharpness, noise and applied lens corrections. LR Classic has taken about 15 minutes to process 50% of them. When inspecting the CPU, it's only being 10% utilized (out of 1600%)... basically the system is idle. -- 8700K@5GHz with 64GB 3GHz DDR4 ram.

Issue:  Lightroom Classic 11.3.1 and 11.3 OS Version Number: Windows 10 21H1 Steps to reproduce: Open Lightroom Classic Wait 30 seconds See the crash window   Expected result: Lightroom Classic working normallyActual result: Lightroom Classic not working at all.

When importing from a camera connected to USB (at least for a Canon EOS 40D Firmware 1.1.1 in my case), lightroom generates wrong folder names when organizing folders by date, at least for the "2011/2011-07-22" format (I guess it's the same for the other formats). I use Lightroom 3.4.1 on Windows XP 32 Bit SP 3 and my time zone is CET+DST (Paris, Berlin). I shot six photos an hour apart around midnight CET+DST from 21:30 on Thursday to 02:30 on friday (I changed the camera's time for that) and got the following folder/file structure using a USB connection to the camera: 2011\2011-07-21\20110721-213022-IMG_0314.CR2 2011\2011-07-22\20110721-223033-IMG_0315.CR2 <<< wrong folder 2011\2011-07-22\20110721-233041-IMG_0316.CR2 <<< wrong folder 2011\2011-07-22\20110722-003049-IMG_0317.CR2 2011\2011-07-22\20110722-013055-IMG_0318.CR2 2011\2011-07-22\20110722-023102-IMG_0319.CR2 Clearly, the two marked files are in the wrong folder. Note t

The LrPhoto methods photo:getDevelopSnapshots(), photo:applyDevelopSnapshot (snapshotID), and photo:deleteDevelopSnapshot (id_global) are not documented in the LR 11 SDK. The latter two methods only work in Develop, not Library.

iMac at OS10.15.3 and LR Classic at 9.2 Develop Module: The spot removal cursor disappears when it is positioned on the actual image meaning that I cannot see where the spot removal is going to take place on the image. Resetting prefs, graphics card off or on, uninstall/reinstall does not change the behavior. The spot removal tool works perfectly on separate test catalogs built using 9.1 and 8.21. Adobe Support has done 3 remote sessions and not fixed the problem. I think this is a bug in 9.2. Does anyone have a solution?

Mac OSX 12.01, Apple Silicon M1 LightRoom Classic 11.2   After upgrade from 11.1 updating any published collections (to disk) is very slow and gets stuck.  One or 2 get published, then progress stalls Re-installing 11.1 solves the problem.

Issue: Keywords created since upgrading to 11.2 are not coming up as auto complete suggestions in the add keywords field when keywording an image.   Lightroom Classic Version Number: 11.2 OS Version Number: Windows 10 v21H1 & v21H2   Steps to reproduce: Step 1: Create a new keyword in the catalogue. Step 2: Select an image and start to type the keyword into the add keyword field in Keywords section.   Expected result: The new keyword should automatically appear as an auto complete suggestion when adding keywords to an image. For example, keywords ‘car’ & ‘caravan’ exist in my my catalogue prior to updating to v11.2. Now after upgrading to 11.2 I now add a new keyword ‘carousel’ I would expect all 3 of these keywords to appear after typing ‘ca’ into the add keyword field. However, only ‘car’ & ‘caravan’ show and ‘carousel’ is missing. Keywords added prior to v11.2 are working but new ones added in 11.2 are not. This happens on both my workstation and laptop (s

I recently upgraded from Lightroom 6 to Classic (11.1) and I have been attempting to create a time lapse video. When I export and view a video (made with 400 photos) I see what appears to be dropped frames in the video. They appear as black flashes. It occurs the most when I export using a user template that is set for 30 frames per second. Slower FPS speeds still have flashes but they are only at the beginning 2 seconds of the video. This does not happen with version 6 using the same templates. I have searched the web for a solution to no avail.  I have tried recreating the template from scratch and had the same results.   Steps to recreate: From the Library - select the photos for the time lapse Go to Slideshow Select the user template Click Export Video Select Video Preset 720P (other sizes have the same issue) Expected result is a video that show all photos selected Actual result: A video with numerous black flashes   OS: Windows 10 with latest maintenance applied LR

  How to reproduce:   Place Clone or Heal Tool onto image. Slowly drag the size slider and observe jumps in size.   When you reach size 75 and increase the size, you will suddenly see a jump to 37.   Can anybody confirm this in LRC 11.3 on Windows 10?        

When opening LR Classic 9.2 it maximized its window size to take my entire screen no matter what the window size was when I had closed LR.  I have an iMac with Catalina 10.15.3.  Uninstalled LR 9.2 and installed LR 9.1 to fix the problem.  Its was too much of a PIA to have to resize the apps window every single time I opened LR to justify the upgrade's features.

In LR 11, when photo:getDevelopSettings() is invoked on a photo with a graduated filter, radial filter, or an adjustment brush that was added in LR 10, getDevelopSettings() returns neither the LR 10 nor the LR 11 representation of those masks.  It should trigger the incremental update of the develop settings and return the LR 11 representation.   This is an issue for users of one of my most popular plugins, Any Filter, searching for photos with masks -- photos from LR 10 and earlier won't always be returned.   -------------------------------------------------------------------------------------------------------------------------------- To reproduce in LR 11.1:   1. Start LR 10.4 and make a new catalog, setting Catalog Settings > Standard Preview Size to 1024.   2. Import a raw with Build Previews: Standard, edit it, and add a Graduated Filter, Radial Filter, and Adjustment brush.   3. Go to Library Grid view (very important).   4. Use the Show Cat

I posted about this a few years ago but this problem remains unfixed.   I regularly make large "Blurb Photo Book"s in the LR Book Module that bump up against the 440 page limit using standard paper.  I also have really lousy internet.  I sometimes have to print a "PDF" book to a thumbdrive to upload at a different location with faster internet.  This works well.   The problem occurs when I want to switch back to a "Blurb Photo Book" from "PDF" in the Book Module.  I get the following error message: Clearly this is a serious problem for me and one I dont dare try to experiment with to work around.  I believe it would not be difficult to set the Blurb Photo Book paper to "standard" paper to avoid this problem.

I use the slideshow option quite a lot. Just upgraded to the Apple Silicon LR version to use on my M1 MiniMac.    I'm on Big Sur 11.3. Haven't yet upgraded to 11.4.   LR 10.3 doesn't like my mp3 music files. Existing slideshows don't play embedded music, and deleting and trying to re-add music files results in the error message "music file is not well formed".   I can downgrade to previous version and everything is fine. I've tried reseting my preference file, but it didn't help.   Anyone else seeing this?

The Keyword List doesn't update properly when you undo a move of a keyword. To reproduce:   1. Make a new catalog.   2. Create the parent and child keywords A > B.   3. In the Keyword List, drag B to the top level.   4. Do Edit > Undo Move Keyword.   5. Observe that B still incorrectly appears at the top level.   6. Restart LR.   7. Observer that B now correctly appears under A.   Tested on LR 11.2 / Mac OS 11.6.2.

Issue:  Lightroom Version Number:  Classic 11.1 OS Version Number: MacOS 12.0.1 Printer: Epson P800, driver version 20   Printing crashes LR when parameters are set wrong Steps to reproduce: Select 1 image and enter the Print module Select Printer (bottom right button) to bring up the printer panel In Printer panel, set to print, say, pages 2-5 (where only 1 image has been brought into the print module). (This can happen accidentally if the previous print run included more than 1 image) Expected result: Either an error message, or the print module should reset the printer panel if there are fewer images in the panel than are referred to in the panel.Actual result: LR crashes.

I've discovered a glitch in Lightroom Classic and can reproduce the issue each time. I'm using a 2021 MacBook Pro with M1 Max. I'm using Lightroom Classic Version 11.1 and macOS Monterey Version 12.2.   In the Develope Module, expand the Transform panel on the right. Then expand the Masks panel. When you hover your cursor over the Transform panel, the entire panel will start shaking / glitching. When the Masks panel is closed, the issue is resolved.   Please see the video below showing this issue occuring.

al presionar el boton anterior se copian correctamente los ajustes de la fotografia anterior pero si en la foto anterior desactivo por ejemplo los ajustes de COLOR - EFECTOS - TRANSFORMAR o cualquier otro en la fotografia siguiente no se desactivan, en el anterior LR los cambios copiados eran completamente copiados, esto me sucede incluso si lo hago sincronizando los ajustes en varias fotografias. muchas gracias de antemano

Buenas! Estoy con problemas al abrir lightroom. La computadora estuvo mucho tiempo sin uso, cuando la volvi a encender actualice todo lo de Adobe. Funcionan el resto de las aplicaciones pero lightroom tira este error. Ya probe instalando una versión anterior pero tampoco funciona. Tengo Windows 10.     

You have a serious bug in Lightroom that has been there for several years and I at least reported to you twice on previous versions of Lr. It has been ignored.This happens when both Lightroom, and Photoshop are up to date (ACR up to date).When I select a number of photos in Lr which I have cropped and edited, to further edit in Photoshop by clicking CMD E (Mac), on occasions, (it does not happen all the time) some photos do not open in Photoshop. For example, I usually have about 30 photos selected and when I open in Ps, I find only 27. I have to go back to Lightroom, find those that were missed and open those again. This is NOT user error, as I am 100% certain that I am SELECTING ALL before I hit CMD E.The way to overcome this is to have Photoshop (ACR) a version behind Lightroom so that when I try to open the photos from Lightroom, it will ask me whether I want to render in Lightroom instead, and that way all photos get exported to Photoshop.Please do not keep on ignoring t

I've been using Lightroom for many years, and I've never experienced this problem until the last two updates to the application. When I upload photos to Lightroom, the app creates a folder that is by default named with the date, in this format: 20210403. I usually rename the folder, in Lightroom, with something more descriptive, just after the upload is complete. For example, 20210403_family-gathering. Starting with the previous version of Lightroom, after I perform this action, Lightroom loses the connection with the files in the newly renamed folder. A question mark appears on the folder in the Navigation panel, and in Loupe view, every photo now displays a small exclamation mark in its upper right corner. When I click on an exclamation mark, a dialog box appears, like the first one of three that I've uploaded. When I click on "Locate," another dialog box appears. For example: The first file, which is highlighted, is the one that is missing (although at this point, Lightroom has lo

I'm using LRC's print module with a layout of 12 cells at one A4 sheet. All cells contain the same image. I have Cut Guides: Crop Marks active. The crop marks are displayed on screen but not printed eventually. What could be wrong? Thanks, Jan  

When a collapsed stack and an unstacked photo are selected, Collapse Stack expands the stack. Surely it's not intended behavior that "Collapse" expands.   To reproduce:   1. Select a collapsed stack and an unstacked photo.   2. Do Photo > Stacking > Collapse Stack.   3. Observe that the stack expands.   A better design would be: The Stacking menu contains two items, Collapse Stack and Expand Stack. If the selection contains no expanded stacks, Collapse Stack is greyed out. If the selection contains no collapsed stacks, Expand Stack is greyed out.   Tested on LR 11.2.

When using my brand new Galaxy S21 Ultra in Pro Mode and importing raw DNG images into Lightroom Classic 10.1.1 the Noise Reduction module does not work at all.  (Other basics do, such as exposure, saturation, etc.)  Yet, my DNG files from my prior Galaxy S20 Ultra do just fine in Lightroom along with DNG files from other devices such as my drone.  This problem was duplicated and verified by another user in the Lightroom Classic forum.   Footnote:  I also received this error message when attempting to upload this image to the Adobe Support Community - Lightroom Classic forum.     The attachment's 20210205_235657.dng content type (image/DNG) does not match its file extension and has been removed.