Bug Reports

I recently came across an issue with the GPS coordinates of my videos in Lightroom Classic 10.3.   I have my camera paired with my smartphone so that all my photos and videos have GPS coordinates.   For my photos, Lightroom Classic works exactly as expected. The coordinates are correctly read from the EXIF data and I can see on the map more or less exactly where each shot was taken.   It's a different story with videos, however. I just recently imported a batch of 9 videos. When I opened the map module, all 9 videos were in exactly the same location. (This location was not on my route but it wasn't too far away either - about 50 KM from where I was walking. But it's somewhere I've never been before.)   Investigating further, I opened some of the video files in EXIF tool to check the GPS coordinates. Each of the nine videos in fact had unique coordinates and, after double-checking in Google Earth, I found that these coordinates were accurate. This leads me to believe

Updated Lightroom to 11.0 this morning. The first message I get is "Cannot convert catalog" and reference to an Adobe webpage. I've checked and there is no LRCAT.LOCK file. All my other catalogs have converted with no problems. It's the big one (of course) that is an issue. I'm running an Intel iMac 27in (2019) with 64GB Ram and about 300GB free on the main hard drive. Photos are stored both on the main drive and an external drive. This is a configuration I've used extensively for a few years now and have about 112000 photos in the catalog. The OS is macOS Big Sur v11.6. Any suggestions are appreciated. In the interim I've started a new catalog and am "adding in place" the photo files. That means I'll lose the collections, but I guess there are worse outcomes possible. Thanks.      ...Doug

I'm in the middle of editing a gallery for a client and I've exported about 100 photos so far and just now I got a pop up during export that says "unknown error occurred", and doesn't allow the image to be exported.  Anyone have any idea why this would be happening? I had a remote session with an agent who was no help whatsoever and just sent me here. I'm hoping someone has had experience with this. Thanks in advance!

Hi.My secondary display has a delay showing my cropped photo. If I crop the photo, LR Classic will refresh the second monitor only after I change something on the photo. For example, I crop the photo. The primary monitor shows the cropped area, but the second monitor shows the original area. If I change the crop area to whatever, the secondary screen updates and shows the previews cropped image (not the new crop). If I exit the crop tool, with the image cropped, the secondary display still shows the previews crop. If I change anything on the photo, for example, exposure by 0.1 (or anything else that forces a refresh), the second monitor updates the photo and shows the current crop. So, what I mean is that the second monitor is one step behind the primary display when showing the cropped image.Besides, when I click the crop tool, the primary monitor blinks the photo very briefly and shows the previews photo I was working on, then shows the current photo again with the crop tool enabled.

This hasn't ever happened to me previously and I edit hundreds of images a day, as a wedding photographer. Has only appeared since latest update (so far as I've seen). Edit an image in Develop mode, normally the thumbnail at the bottom would auto update with the new preview/look. It doesn't anymore. Go to Library mode to check, no, no update to the preview, it's still the old look. Force rebuild standard preview (and 1:1 preview) no effect. The Library preview will not update to the new look created in Develop mode. Quit LR, then restart it, the preview is updated. Even did a Sync of one process, which was converting to BW across 5 images. Four of the images changed profile to the new look, the 1st image in the group didn't. Stuck with previous old version of the look. Quit and restart LR it changed to new look. MacOSX 10.15.7

-----Lightroom / System Info:Lightroom version: CC 2015.8 [ 1099473 ] (and earlier)Operating system: Mac OS 10Version: 10.12 [3]Application architecture: x64Graphics Processor Info: NVIDIA GeForce GTX 775M OpenGL EngineCheck OpenGL support: PassedVendor: NVIDIA CorporationVersion: 4.1 NVIDIA-10.14.20 355.10.05.15f03Renderer: NVIDIA GeForce GTX 775M OpenGL EngineLanguageVersion: 4.10-----In the develop module, when one toggles the image view to "After Only" (after toggling to "Before Only") the image blinks / blips. To replicate:1. Open an image2. Go to develop module3. Press \ key to toggle to "Before Only" view of image4. Press \ key again to toggle back to "After Only" view of image -- a blip / blink occurs in the transitionNotes:- Blink / Blip sometimes does not occur until the second toggling of before / after using the backslash key- Behavior is the same whether using the backslash shortcut key, or selecting appropriate options from the View menuThis bug is significant becaus

Possible regression bug starting with LR Classic 11.0 (and still present in 11.4.1): during export, with  "Remove person info" is selected, exported JPEG files still contain person information. This was not happeing in versions up to 10.4. This may cause some trouble, as personal info could be shared unexpectedly.

Today I noticed Lightroom Classic was displaying incorrect metadata for recent imported videos (taken with iPhone X). My older videos have correct metadata, so what changed? Appears to be an issue specific to M1 Macs.   Here is what I found...   On M1 Mac Mini: 1. Get info in Finder for MOV files shows the expected metadata. Created date/time is correct, and other details such as latitude longitude are displayed. 2. When I import these files into Lightroom, the metadata for capture date/time is incorrect. Lightroom displays the date/time the video was imported into Lightroom for capture date/time, which is clearly not when the video was captured. The GPS box is blank and no camera info is displayed.   On Intel Mac: My Lightroom catalog and masters are on an external drive, so I connected to an Intel MacBook. I imported the exact same MOV file. This time, Lightroom displays the correct capture date/time (matches the created date/time as seen in Finder). The GPS box pulls

If you move a set of photos from one folder to another in Lightroom Classic, and the folder you are moving the images to has any duplicate file names, there is an issue where you will get an error message properly indicating the duplicate file names, but there is also an associated bug where the non-duplicates will not be transferred or handled correctly by the catalogue links and you'll receive the (!) icon causing you to have to relocate the files.  As the files move in the operating system, Lightroom doesn't update the links after hitting the duplicates.  As an example, you may move 10 images of your dog from your 'Recently Imported' folder to your 'Pets' folder.  If there are 2 duplicate file names in dogs, you'll receive an error noting that (properly), but a portion of the 8 remaining photos (not all) will have the (!) error symbol indicating the source file cannot be found, even though it remains in the same 'Recently Imported' folder in this example.  Once y

With the latest Adobe update, all AI-based masks (e.g. sky, subject) that are part of a preset are updated automatically when applying the preset to a new picture or when hovering over the preset to get a preview of what the changed picture will look like.   So far, so good. On our M1 MacBook Pro, everything works like a charm. Previews are created instantly. When you click on a preset, all changes are applied immediately. Works perfectly in LrC, LR, and Camera RAW. However, not on an iPad and not on the smartphone and we were not able to get an answer from someone at Adobe when this will be supported.    HERE COMES THE REAL P'ROBLEM. When you try to use the same function on a Windows 11 machine, IT DOES NOT WORK. Generating a single preview can take up to 2 minutes. Alternatively, the GPU produces an error message, the application freezes or the software tells you that the AI-masks could not be computed. When you click on a preset, a window appears telling you that sett

The Develop module no longer properly renders the Grain Effect settings in LrC 10.2, which appear much more pronounced and correct in the Library module and exported files. I tested with GPU enabled and disabled with LrC restarted and the issue persists on my Windows 10 system.   The below screenshots are with LrC 10.2 using Grain settings Amount 100, Size 50, and Roughness 100.  

Lightroom Classic version : 11.4.1 Lightroom Mobile version: 7.4.1 MacOS Version: 12.4   When I try to sync a photo from LR Classic to LR CC, in grid view the thumbnail is displayed as an icon of a cloud w/ an exclamation point, on iPhone, iPad and Web views. Additionally, when I hover over a thumbnail on Web, it displays a message of "Open Lightroom on [computer name] to continue syncing." despite both Lightroom Classic and Lightroom CC being open on the computer.   The thumbnail is displayed correctly in the desktop app. If I make an edit to a photo, the thumbnail then shows up correctly on all platforms.   If I roll back to 11.4 and sync photos, their thumbnails are displayed correctly.   Steps to reproduce: 1. Click the sync icon next to an album in LR Classic, or add a photo from the catalog to an album that has Sync enabled. 2. Wait for the Cloud icon in the upper right corner to display a green checkmark. 3. Open Lightroom on iPhone, iPad, or Web. 4. Look at

Hello... I am finding that the Amount Slider defaults to "100" and grays out when I set the amount to 115 when I use PG02 in the "Portraits Group" presets. It seems to happen at only that preset, and only that amount.   LrC v. 11.4 Windows 10

Issue: Converting to DNG removes star rating   Lightroom Classic 11.4 MacOS 12.4   Steps to reproduce: Rate files with 1 star Convert Sony A1 raw files to DNG with the following settings: Only Convert Raw files Delete originals after successful conversion File extension DNG JPEG preview medium Embed Fast Load Data Use Lossy Compression   Expected result: new DNG files should maintain the star rating as they have done in previous versions of LR Acutal result: as soon as the Raw file is converted to a DNG, the star rating disappears

Issue: Lightroom Classic 11.4 does not render local adjustments for older files unless they are first opened in Develop   Lightroom Classic Version Number: 11.4 OS Version Number: macOS 11.4 (Intel) Steps to reproduce: find an older file that has local adjustments, export from Library view file is rendered without local adjustments (Masks) open file in Develop module, without doing anything, export again file is now rendered correctly, WITH local adjustments (Masks)   Expected result: file will be rendered with masks, in step 1Actual result: file is rendered without masks, at all, in step 2   Video: https://www.dropbox.com/s/7wukaii7gbp4ml0/lrc11-4-export-bug-demo.mp4?dl=0

Using LR Classic CC.I just transitioned from a 6 year old Lenovo W510 laptop to a Dell XPS 15 Touch. I immediately noticed that Collections and Publish Services were missing in LR on the Dell. Just gone. There is a huge black space instead. I reached out to adobe.forum for help and tinkered while waiting. Meanwhile, I stumbled across an interesting behavior: If I closed Folders, Collections and Publish Services appeared! Yay! But when I re-opened Folders, Collections and Publish Services vanished again. I use all of these extensively, so this is a huge annoyance and inconvenience.I was advised to removed/re-install LR, but there was no change in behavior. It turns out that LR has some inexplicable/undocumented limit as to how many folders it can show (!). How I know: I have 627 folders and about 15 or more were expanded. That is, each was showing their numerous sub-folders. I closed all the sub-folders so that only the 627 main folders were listed under Folders and Collection

When a plugin attempts to set a photo's PerspectiveVertical to a non-zero value and PerspectiveHorizontal to 0, LR throws   "An internal error has occurred. ?:0: attempt to index a nil value"   If both of those settings are non-zero, or if ConstrainToCrop is 1, no error is raised.   To reproduce, run this script:   local LrApplication = import "LrApplication" local LrTasks = import "LrTasks" local catalog = LrApplication.activeCatalog () local photo = catalog:getTargetPhoto () local settings = { CropConstrainToWarp = 0, PerspectiveAspect = 0, PerspectiveHorizontal = 33, PerspectiveRotate = 0, PerspectiveScale = 100, PerspectiveVertical = 0, PerspectiveX = 0, PerspectiveY = 0} LrTasks.startAsyncTask (function () catalog:withWriteAccessDo ("Update", function () photo:applyDevelopSettings (settings) end) end)     Tested on LR 11.0.1 / Mac OS 11.6.

The SDK methods photo:rotateLeft() and :rotateRight() have a disastrous bug -- they can rotate all the photos in the catalog. To reproduce:   1. Save the script below into "rotate-bug.lua" in the Scripts folder.   2. Open a test catalog with at least 10 JPEGs.   3. Rename one of the photos to be "xyz321.jpg".   4. Run the script "rotate-bug.lua".   5. Observe that just that one photo gets rotated.   6. Set the filter "Filename Doesn't Contain xyz321.jpg" and observe that file is no longer visible in Grid view.   7. Run the script "rotate-bug.lua".   8. Observe that all the photos in Grid view get rotated!   Underlying this bug is another (old) bug: photo:rotateLeft() and photo:rotateRight() rotate all the photos in the current selection, rather than "photo" (and only "photo"). To work around this old bug, a plugin must use catalog:setSelectedPhotos() to select the photo it wants to rotate. But as this bug report demonstrates, if that ph

Images that are exported from LRC 11.2 and then uploaded to Adobe Stock lose the exported synonym keywords. This also occurs using the LRC Adobe Stock Publish App. Issue:  Lightroom Classic Version Number: 11.2 OS Version Number: Windows 11 64 bit Steps to reproduce: Include synonyms with your keyword tag. Check that the synonyms are to be exported. Assign the keyword to the image. Export the image. Verify that the synonyms were also exported .  Upload to Adobe Stock. Expected result: All of the keywords and synonyms should be recognized and uploaded.Actual result: Only the keyword without synonyms is recogniozed.

Hi,For some years I have been keywording my images in Lightroom, using keyword hierarchies to manage them. Recently, when I try to upload to Adobe Stock, it only takes the bottom level keywords, and none of the hierarchy keywords they are in. This happens if I use the Stock plugin, or export and upload directly or via FTP.  This problem doesn't occur for other agencies, and the keywords are correctly embedded in the JPG file details, so I'm at a loss as to why adobe Stock doesn't see them - any suggestions as to what i am doing wrong ??ThnaksRoger

I have never had this issue in previous versions of Lightroom (or Photoshop, if it's a Photoshop problem), but whenever I open an image (jpg, psd, tiff) from Lightroom into Photoshop and do some editing there, when I get back to Lightroom the [+/-] icon appear on the image ("Photo has development adjustments") and on the Quick develop panel, next to "Saved preset", appears "Custom".   As I said, I have never seen this behaviour before.   Thank you for your consideration.   -------------------------------------------------------------- Thread moved to Lightroom Classic 'Bugs' forum

When you do Preferences > Presets and check Override Global Setting [sic] For Specific Cameras in a catalog that contains no raws, the message "Please wait while loading camera models" incorrectly appears and never goes away. This fools some users into thinking that LR is just slow and that camera models will (or should) eventually appear: https://community.adobe.com/t5/lightroom-classic-discussions/please-wait-while-loading-camera-models-new-lightroom-installation/td-p/12889593   When there are no raws in the catalog, this message should be displayed: "The catalog contains no raw photos, so the list of cameras is empty."     Tested in LR 11.3.

The Metadata panel's Caption field doesn't correctly display the results of appending text to the captions of multiple selected photos. It works correctly in LR 11.2 and earlier but not in LR 11.3.1, and it appears to be another symptom of the change in LR 11.3 to cache metadata in <catalog> Helper.lrdarta.   Tested on LR 11.2 and 11.3.1, Mac OS 12.3.1.  Steps to reproduce (also see the screen recordings):   1. Make a new catalog and uncheck Catalog Settings > Metadata > Automatically Write Changes Into XMP.   2. Import three photos with no caption in their metadata.   3. Set the captions of the photos to "A", "B", and "C" respectively.   4. Select all three photos.   5. In the Metadata panel, with Selected Photos highlighted, observe that Caption displays "< mixed >".   6. Set the input cursor after the ">" and type "X" and then return. Observe that Caption now displays "< mixed >X".   7. Select just the first pho

Cropped size in pixels is now missing in Library, the full original size is just repeated

  Content moved to correct post