Bug Reports

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.    

This issue has returned.   The catalog opened ONCE (and only once) after updating to LrC 10.2; I do this as a test everytime I update LrC.   Now, a few days later, I get the pop-up with the error text: "The catalog could not be opened due to an unexpected error."

When I bracket exposure or "motor drive" on my Pentax K-5 II, and sort the files by shutter press time, they do not show up in the right order. To see them in the right order I have to sort by filename (which breaks if I use two cameras or loop my counter past 9999).When I look at the exif data, capture time is only shown to a resolution of one second. What the software should do, when sorting by time, is if photos were taken in the same second, sort them by the index number in the filename.

I have been patientilly waiting for help with these issues in LrC Book Module, posted in the now closed Adobe Photoshop Forum. I don't understand what I am to do to get help with these ongoing issues. I was working with @8510810, and I thought that after uploading example files and promises that the engineers would look at the issue, I don't understand what I am to do now. Has Adobe given up of trying to solve long standing issues and closing past reports is a convienant way of telling their customers to go away? I hope not and I really would like Adobe engineers to know that the book module does not work very well.   Issue #1 I'm making a book in LrC 10.2 on a Mac Pro 10.15.7 (Catalina). Some of the custom pages include a photo description cell and the filename is automatically included. When I highlight the cell and press delete, all is well, it deletes. However the next time I open LrC and go to the book module to continue working, the deleted photo description cell reappe

Though there were otherwise just cosmetic changes made to the SDK version 11 "Lightroom Classic Programmers Guide", there was one serious mistake. On page 9, as part of changing occurrences of "Lightroom" to "Lightroom Classic", this sentence from previous versions was deleted:   "Lightroom 5 uses version 5.1.4 of the Lua language."   That sentence should be retained and edited to say:   "Lightroom Classic uses version 5.1.4 of the Lua Language"   It's very important to tell plugin developers which version the SDK uses because:   - The mainstream Lua release is now Lua 5.4.3 and there are significant differences between 5.1.4 (the version LR uses) and 5.4.3. - Most programmers coming to the SDK aren't familiar with Lua and will get confused when they read documentation for the wrong version.    

The LR 11 SDK API Reference for LrPhoto documents two new methods, photo:copySettings() and photo:pasteSettings().  But as documented, they don't do anything.  Update: The documentation is highly incomplete and needs to be clarified. See below. To reproduce: 1. Copy this script into the file "copypaste.lua" and save it in the Scripts subfolder of the "Lightroom" preferences folder:   local catalog = import "LrApplication".activeCatalog () local photos = catalog:getTargetPhotos () if #photos ~= 2 then import "LrDialogs".message ("Select exactly 2 photos") return end photos [1]:copySettings () photos [2]:pasteSettings () catalog:withWriteAccessDo ("copy/paste", function () photos [1]:copySettings () photos [2]:pasteSettings () end)    2. Restart LR. 3. Choose a photo and set its Exposure to +5. 4. Select that photo and another, with the first photo most selected. 5. Do the menu command Scr

Just upgraded to 11.1 and am getting unexpected error on starting up across two different catalogs(have not tested more). I downgraded to 11.01, and was able to open Lightroom Classic without a problem.  Backed up the library, rebooted my Mac (iMac 5K Retina, 2017) running 11.6.1, reinstalled 11.1 and it seemed to run ok for about 2 days.  This morning got the error report again and have downgraded to 11.01 again   Any suggestions? Thanks

Since the lightroom update, colour grading videos has been messed up for some reason. When I turn UP the temperature, the video gets cooler on the main panel, but the preview in the navigator gets warmer like I wanted. When I export, the navigator view is what gets exported, but the main panel view is just messed up. Someone please help!! Photo below:  

I'm trying to copy GPS coordinates from one photo (taken with phone) to others (taken with camera). The bug is specifically that when I try to use "Add GPS Coordinates to Selected Photos" then nothing happens and no GPS data is added to the selected photos. Background: When I highlight and drag the "unGPS'd" photos onto the map the pin goes to the wrong location. (I'm aware this is a bug that goes back a very long time.) So I tried the known work around which is to select the photos in the film strip that I want to copy the coordinates to, and then right click on the coordinates of the photo that is already on the map and use "Add GPS Coordinates to Selected Photos".  That worked for me in LR 10. I've upgraded to LR 11 & Windows 11 and this workaround no longer works. Now, nothing happens.    System info details in the attached text file.   Regards   John Godfrey

Normal screen copy for a mask: Screen copy for color range: You cannot see the figures on the right. No way to expand the tool window. Display: 2560x1440, Font: middle size When using a large font (150%) the window size is good, but unfortunately this window takes 1/4 of the screen! Too much. I don't know where to contact the support, I post this bug here.

I imported a 9138x6310 TIF file and performed numerous adjustments including several masked adjustments.   The image exports fine at reduced resolution (2048x1414) but if I try to export at full resolution Lightroom gives the error: "An unknown error occurred. (1)". If I click "Turn off Masks" the image (without masks) exports at full resolution with no error. The exports are performed with the "Export..." command.   If instead I attempt to export with masks on via Publish Services ("jf Flickr: in this instance) the following error is reported: "Couldn't render image: AgNegative:renderToFile: <AgErrorID>dng_error_unknown</AgErrorID>".   Lightroom Classic version: 11.0 [ 202110120910-0bccc70d ]Operating system: Mac OS 12.0.1 [21A559]Application architecture: x64Logical processor count: 16Built-in memory: 65,536.0 MBDisplays: 1) 4096x2560 Graphics Processor Info:    Metal: AMD Radeon Pro 5500M (full copy of system info attached)

I have a Wacom Intuos Pro. In LRC 10, I could use the back of the pen ("eraser") to temporarily switch the brush tool from A or B to Erase. This functionality seems to have broken with the update to LRC 11 when using the updated Mask tool. When I use the back of the pen now, it just adds to the brush stokes instead or erasing them.   Any advice on how to fix that?   I'm on Mac OS Catalina, LRC 11.0.

I simply highlight that the algoritm of Super Resolution doesn't work properly with Fujifilm RAF from S5pro.   The final result have wrong ratio. Both side was enlarged but with different ratio.   Here an example (screenshot from Lr but same behavior in Lrc): Original image: RAF 4256x2848  (12,12Mpx) Enlarged: DNG: 11907x3984 (47,43Mpx  ratio 3.9 compared to the original 12Mpx)

Over the years Lightroom has fixed most Windows high-DPI scaling issues with the UI, but unlike the image flag mode icons, the Compare mode Select/Candidate indicator icons still do not scale. This makes using Compare mode tricky at times as they are virtually impossible to see in the filmstrip.   I have a laptop with a 4K screen and I set Windows to either 200% or 225% scaling. Please note this is not a multi- or external-monitor issue, it's just the native display, and Lightroom is otherwise correctly responding to the system screen resolution & scaling settings, by giving me crisp high-DPI UI graphics & text but also correctly scaling bitmap UI assets like the flagged/rejected icons which render at the appropriate size.   See attached image

When the left sidebar is unpinned/collapsed but temporarily expanded, it interferes with the Display module Info view.   Repro steps: 1) Collapse the left sidebar with TAB or by clicking its left edge. 2) Switch to one of the Display module modes: press E, C or N 3) Enable one of the image Info display modes: press I 4) Hover over the sidebar's left edge so it expands   The sidebar partially covers the image area, but not the Info overlay which renders over the top of the sidebar, creating a visual mess.   Incredibly, when I had an Adobe Support operative look at this last night, they told me this is working as designed. I really hope that was a mistake.   Windows 10 Lightroom Classic 11.1   Other users on DPReview forums have confirmed they also get this issue.