Bug Reports

P: Videos do not play or import macOS High Sierra

Lightroom 8.4 crashing when attempting to access Map or Web modules. No problem accessing all other modules. Using macOS 10.14.6 on an iMac Pro.

1. Import an image and apply metatdata to the Title field. (eg. "Lovely Wiew")2. Export to jpg. The jpg has the Title "Lovely Wiew".3. Recognise the typo (ie Wiew should be View).4. Correct the raw image in Lightroom. Raw image now has a title of "Lovely View".5. Re-export the image, overwriting the existing jpg.6. The jpg still has the incorrect Title value of "Lovely Wiew".after correcting and re-exporting the image, the catelog value for this raw and jpg should be "Lovely View" and the metadata within the jpg should contain the Title "Lovely View".This bug causes me unending levels of grief and hours of wasted re-work time.

I am using Mac OSX and LR CC 2015. I have a workflow that involves importing thousand of raw photos and then sorting them. In order to sort them, I take a group of photos of the same subject and move them to a temp folder and then repeat until all the photos have been moved to sub categories based on there names. I then move the photos out of the temp folder into the original folder and delete the temp folder. While attempting to move the folders containing the photos, one of the folders and the 97 photos under it was lost. There is also a descrepancy in the number of photos copied 97 vs 76. And I can no longer find the photos on my hard drive. i did NOT delete the photos. LR seems to have deleted them. This is a HUGE problem.

LR Classic CC 7.0 Windows 7 w/ATI Radeon 5700no renaming or presets, minimal previews selected(1.8 Gb HD with 171 Gb free at the end of this import)Preview generation/ status update tasks are not quite running in parallel with the file import??:With an import of 887 D500 photos the library grid display shows blank grid area with "importing files" and the file counters do not change from zero for some time.After starting the import yesterday for the first time I thought LR had crashed as there was no changes onscreen for about 5min.However, after cancelling this import and restarting LR I found that there were photos in the destination (not showing in LR though)Removed photos from the hard drive and started everything again this time I watched the file folder in explorer to see what was going on:Started import @ 12:36pm (12:45pm) After 223 photos show up in the destination directory in Windows explorer then LR grid view finally shows 8 thumbnails in the destination folder, the current i

I was going to post this the other day, but since Iended up upgrading to version 9, I though it would no longer be an issue. WhenI was using version 8.4.1, I added a bunch of jpegs to Quick Collection, editedit down to 266 images, then clicked on Web tab & Lightroom crashed.Relaunched Lightroom, reordered one jpeg, again selected Web, and it crashedagain. I believe I then restarted my computer, was finallyable to make website with no crash. I have been using Lightroom for years and don’tremember this ever being an issue previouslySince then, I have upgraded from Sierra (10.12.6)to High Sierra (10.13.6), upgraded Lightroom Classic from 8.4.1 to 9, yet onceagain when I clicked on Web module, it crashed! This time, I had 5 raw (4 NikonNEF and 1 Canon CR2) files selected. Would like to not have to restart computerevery time I need to make a web gallery.I am using an iMac (Retina 5K, 27-inch, Late 2015), 32 GB of ram.

My plugin collaborates with an  application through LrSocket. Unfortunately, when LR shuts down, it only calls LrShutDownApp after the socket no longer functions. I've tested this by sending a message to the application by LrShutdownApp and LrShutdownPlugin. The message gets sent when LrShutdownPlugin is called, but not when LrShutdownApp is. This creates significant problems for any plugin that has an associated application, as you can't get an orderly shutdown of both.Fix--call LrShutDownApp procedures earlier in the shutdown process, prior to killing the sockets.

For whatever reason I'm having this strange problem where sometimes when LR window is active macOS Spaces changes to second of the three Spaces I'm having. I've dragged the LR window to the third space and it doesn't matter what Screen Mode LR is on (Normal, Full Screen with Menubar or Full Screen), macOS changes the view to the second Spaces after a second or two, but doesn't do it always after changing the active app to be LR.I do have two display monitors: one iMac 27" (primarily) and one HP EliteDisplay E241i (secondary) in portrait orientation, and I have the Second Display enabled on the secondary display monitor.What takes? Anyone else having this annoying problem?I would use the Dock option to force LR stay on the third Spaces but then I wouldn't be able to use the Secondary Display option on the secondary monitor (silly LR). I don't want to use LR in macOS System-Wide Full Screen as it would make LR to have it's own Spaces and I'd rather have my workflow in current three Space

I geotag photos on a daily basis, and today, after updating LR Classic CC to version 7.5, I was going to resume my geotagging tasks as usual, but then I started to experience weird issues when placing photos on the map.Most of the time, the problem is that I drag the photo from the filmstrip to the map (in the Map module, of course), and nothing happens (no photo on the map, no gps coordinates in the metadata). If I drag and hold the photo over the map for a few seconds before releasing the mouse button, sometimes it does place the photo.I would say it's even more difficult when I select several photos and try to place them on the same spot at once, but I can't say absolutely for sure.Also, selecting the photo (or photos) and then Ctrl+clicking (Windows) on the map to place them stopped working altogether as soon as I updated to 7.5, no matter how long I kept the keys or mouse button pressed down, or how many times I tried (previously, I was using this shortcut dozens of times a day).S

There is little but annoying problem in the Lightroom (latest CC version on Windows 10) Develop module. The problem arises when the "Enable profile correction" checkbox is unchecked and you are using Tab key to move between fields (I'm often filling color noise reduction values using a keyboard and Tab to move to next field) and you press Tab by mistake on the end of "Detail" section. The focus jumps to the Distorsion field, but as it is disabled (Enable profile correction is unchecked), you are in the trap. It is not possible to change the value, but when you try to get out (clicking by the mouse or using Tab key another time), Lightroom shows "Invalid numeric entry" dialog and after pressing OK sends focus back to that field. The only solution I found is to click on Library in the top panel and after once again "Invalid numeric entry" dialog Lightroom switches to Library module. The error is fully reproducible on fresh photo, but once you click on "Enable profile correction" checkbox

LR Classic 7.1 on Windows 10 v1709Wacom Intuos PhotoVideo Link: https://youtu.be/mVVVyYn0MTEThis problem does not happen in PS, so I think the issue is limited to LR.LR for Windows though. I cannot reproduce the issue on my MacBook Pro running OSX 10.11.6When I make small movements with the Wacom pen, the mask is not applied, it is not until I move a good distance away while still pressing that I get the mask applied.

Lightroom Classic 8.4.1 is starting even thou there is a saved [My catalog].lrcat.lock next to [My catalog].lrcat. I know the .lock-file is supposed to protect the catalog file from beeing opened by someone else. If a .lock-file with the same name as the catalog file is stored in the same folder, I should have to delete the .lock-file before I can open the catalog file.Now, I am able to open the catalog file without deleting the .lock-file. I have seen this before, and a few other users have reported the same behavior in a user forum I am hosting in Norway. So I had to test, and I could also see Lightroom opening the catalog file with a .lock-file next to the catalog file.How can this be? Is it a bug or a non-documented feature?

I just upgraded to the full Catalina this week (October 2019) and it is still giving me only the COPY option and is bogging down my machine (2015). I set the permissions on my external drive all to read and write and have been trying to prompt the error message but have not gotten anywhere. Is there any update on the solution to this?Note: This conversation was created from a reply on: Lightroom Desktop: Issues with changes to the way drives and volumes are treated....

MacBook Pro (Retina, mi-2012) 2,7 GHz Intel Core i7 4 hearts16 Go 1600 MHz DDR3NVIDIA GeForce GT 650M 1 GoIntel HD Graphics 4000 1536 Mo OSX 10.15.1 (19B88)LR Catalogue is on a SanDisk Extreme SSD Media with 932 Gb Free Since Mac OS Catalina Lightroom Classic freezes after hitting "import" with Nikon D850 files. - The files are read in the import section- The files are placed in the right folder on my SSD even though LR is reporting import still occur- During that freeze, all sections what so ever display the corect amount of photos in the corect folders but will only display "Charging" instead of showing photos- Have to force quit the App- When restarting LR some photos made it into the library but at least half of them didn't (All photos are at the right place on my SSD) What I've tried - Reboot : Same Issue- Uninstall/Install LR : Same Issue- Tried to import them directly from the folder in the lightroom catalogue : Same Issue- Photos can be import

All of my regularly used Adobe products are crashing very frequently.Photoshop & Acrobat the most, multiple times a dayLightroom occasionallyAll up to date on OS and Adobe CC. Multiple restarts. Frequently, but not always, happens when switching from one adobe product to another. No other software on my computer is acting this wayThis is very aggravating__Mojave 10.14 (18A391)MacBook Pro (15-inch, 2016)2.9 GHz Intel Core i716 GB 2133 MHz LPDDR3Radeon Pro 460 4096 MB

Export doesn't always choose a new name for files exported with the option Existing Files: Choose A New Name when exporting to case-sensitive volumes.  To reproduce:1. Import a photo with an upper-case file extension, e.g. DSC02512.ARW, that resides on a case-sensitive volume.2. Export the photo with these options:Export To: Same folder as original photoAdd to This CatalogExisting Files: Choose a new name for the exported fileImage Format: Original3. Observe this error message:The fix is simple -- when checking whether the file already exists, LR should use the original path to the photo unmodified, rather than lower-casing the extension.Someone tripped over this bug with an Export preset that duplicated cataloged photos:https://community.adobe.com/t5/lightroom-classic/problem-with-virtual-copies/m-p/10751757#M163989(And yes, that user had a good reason for not using virtual copies.)

For several years now, users have been asking for a way to import only the RAW file when shooting RAW+jpeg. In fact, it's never been satisfactorily explained to me why I would ever want to import the jpeg into Lightroom. I do all my post work on a desktop workstation, but I shoot tethered to a laptop, to which I only import jpegs for reasons of speed and storage (the image pops up immediately, and I don't have to constantly trash all the RAWs to save HD space). Once I'm ready to import, I have no further use for the jpegs. I can't even imagine a reason I'd want to bring them into Lightroom. There is no way to do this in Lightroom's import interface, and I guess there never will be, and I'd made my peace with that, until Lightroom learned a new trick recently. Several imports in a row now, Lightroom has imported the RAW and the jpeg for most of the card, but skips the RAW for several images and only brings in the jpeg. This is not immediately apparent, as you can imagine. Fortunate

Hi I am using a D700 nikon tethered in Lightroom (8.1) with os High Sierra  vers 10.13.6. An issue I am currently experiencing even after updating Lr is when I have Lr open tethered and I also have Photoshop open. After using lightroom and then switch to Photshop (leaving Lr open in tethered mode) and return to Lr the tethered live window is still there but the camera does not fire (even though the button in the tethered window is lit live for use) I have to close and re-open Lr to continue while client looks on.

Synchronize Folder > Scan For Metadata Updates can cause frequent spurious metadata conflicts for TIFFs that are stored on NAS.  Over the years many people have reported spurious metadata conflicts that Adobe hasn't been able to track down, and many of those reports involve photos stored on NAS.  Here's a recent report:https://feedback.photoshop.com/photoshop_family/topics/before_after_comparison_of_metadata_conflicts...While the particular use case here may not be that common, it may provide a reproducible test case that points to the bug (likely a race condition) underlying all those other persistent reports.Here are the steps that consistently produce the spurious conflicts in my configuration:1. Connect to a network volume on a 2013 iMac running MacOS 10.14.6. The volume is mounted with SMB 3.0.2.  2. Place 4 1800 x 1200 TIFFs (about 13 MB each) in a folder on the network volume.3. Import them with Add into a LR 9.0 catalog running on a 2019 Macbook Pro

[LR is treating a .jpg as a metadata sidecar of a .mov even when Treat JPEG Files Next To Raw Files As Separate Photos is checked.  See here for a recipe to reproduce the bug: https://feedback.photoshop.com/photoshop_family/topics/lr-adding-metadata-from-jpg-into-mov-file-on-...]BackgroundAfter a phone change, I ended up with files with the same filename (except file type) residing in the same image folder (JPG + HEIC/MOV)On import of all files into LR, I saw that the order of the files was totally wrong (when sorting on capture time)Some files were months off and with 500+ images in just one importSpent a great deal of time debugging this and found that LR seem to add/overwrite metadata in .MOV files (which by default is lacking many fields usually present in images) IF on import, there exists a JPG with the same filename in the folder. If so, much of the metadata from the .JPG is copied to the .MOV file!? Doing an import w/o the JPG present, no fields are touched

Assign a color label to a collection, e.g. redThen filter the collections by color laberl = redNow, in the collections panel, we will see a list of these "red" collections, and the number of photos inside each of them.Problem: At this point, if I remove photos from the collections that are being displayed, the photo count next to the collection name doesn't update until I remove the color label filter back to "All".Not a huge deal, but a follower from my youtube channel shared this with me, I was able to reproduce the issue and I thought it might be worth reporting it here.I'm using Lightroom 9.0 on Windows 10 1903.Thanks.

In the past it was possible to easily copy metadata from video files in lightroom classic to an edited copy of the video by using the built-in "Copy metadata..." and "Paste metadata.." functions. Since last patch of Lightroom Classic this does not work anymore. All fields in the copy dialog are empty even if the source video has metadata. However, the copy process still works with pictures. Only video files seem to be affected by the bug.

Using "add" to add items to the catalog.  If I click the import button the right side of the import window is correct and looks like this:Note the "Apply During Import" section.   However, if instead of clicking import I drag a folder to the Lightroom icon the "Apply During Import" section is missing.  It also look like the last used develop and metadata settings are applied to the images.This is a regression.  Now the import window looks like this.

I am using Lightroom Classic 8.4.1. I created a book and saved it. As I had a previous crash in lightroom (which seems to be quite often since I upgraded), I had to import some of the photos from a previous catalog to keep the editing. However, as soon as I do this, the entire book disappears! Nevertheless, the photos on the film strip still seem to be selected in the book, as you can see on the attached picture. It looks as if the book was not displayed correctly. It has happened the same thing doing other changes. I really think there is a big bug with the Book Module, and it is frustrating. Any help?ThanksH

[See this reply for a precise recipe for reproducing the bug: https://feedback.photoshop.com/photoshop_family/topics/bug-image-disappears-from-the-filmstrip-after...[See this reply for workarounds: https://feedback.photoshop.com/photoshop_family/topics/bug-image-disappears-from-the-filmstrip-after...]Externally edited images do disappear from the filmstrip when a filtered view is active.To reproduce the problem:1. Create several folders with several tiff images.2. Import the images in Lightroom.3. Add the 'flower' keyword to every image.4. In the Library module, in the 'Keyword List' panel click the arrow right to the 'flower' keyword. This will make Lightroom to show all the images that has the keyword 'flower'.Now comes the problem.Edit one of the images on the filmstrip in PS (Ctrl+E). After changing the file and saving it, when returning to Lightroom the image disappears from the filmstrip.When checking the image in the folder (clicking the correct folder in the Library)