Bug Reports

Issue:  Lightroom Classic Version Number: V15 and V14 OS Version Number: Windows 10 Steps to reproduce: import a Photo with GPS geo-location tags the location fields (state, country, city, details) will be set automatically and shown greyed out Edit and change e.g. the city Navigate away from photo and come back (Added by Mod) Expected result:  the city shows the new value (not greyed out) and all other greyed out location fields stay with their old value derived from the GPS-coordinates.Actual result: the city shows the new value (not greyed out) and all other  location fields have their old values removed/cleared.   This is annoying if you have to adapt a lot of locations (typically CITY) where the default is not suitable. In V13 it worked as expected. I have 80,000 geo-tagged aerials where this information is crucial.

If I have an active tether session and then click on the gear icon to update the tether settings and making any changes to a live tether, hitting the return button causes LR to crash. It will not crash if I click on "Ok"   I have a team of computers using the following: LR 11.0 or later Big Sur or Catalina  Canon 6ds or canon 6dII.     This is an issue on all computers using the above set up.

LrStringUtils.compareStrings() doesn't compare strings containing digits correctly.  For example, it says that "a9b" comes before "a10b":It appears that compareStrings() is comparing sequences of digits numerically, e.g. as the numbers 9 and 10 in the example above.   While that definition can be useful in some cases, such as ordering filenames containing sequence numbers, it is not generally useful for sorting.  The SDK should restore the traditional meaning to compareStrings() and optionally provide a second compare function for the current functionality.

I have one image with two virtual copies (A - original, B, C).All images have presets applied.When I quickly switching from A to B and then to C (using arrow keys on keyboard) the preset from the image B is being applied to image C.   MacOS 12.4 Lightroom Classic 11.4.1 Camera Raw 14.4.1   Here's a screen recording. The only input is right arrow pressed twice. You can see that the preset from image B (B'n'W) is being applied on image C. https://youtube.com/shorts/QP12dwse9ms?feature=share   

Lightroom issue. When I import a few Pictures sometimes some Pictures has a wanring "Lightroom can't read the Picture" (germen). The Picture is correctly imported, I also can open it with other programs. I'm able to remove the Picture from Lightroom (and Hard Drive), restart Lightroom an try to import it again (from Disk oder CF-Card). Import succeeded but the error still remains. I'm using Lightroom 3.4.1. Thanks for suggestions!

hiI have a problem after the last update, the sidebar with the navigator does not work, it is partially obscured. the new installation did not help, resetting the preferences does not help, I also tried to change the panel display options, nothing helps. While the English language is set, everything is fine, I am asking for advice and possible help.          

Keyboard shortcuts for Create A Depth Range are missing for ES, IT, and SV.  All other languages assign Shift +Z.   ES, IT, and SV assign Shift + Z to Create  A Radial Gradient, while all other languages assign Shift + M.   This is as-coded but surely not as-designed (what possible design rationale could there be?) -- it's just a clerical error.   To make those languages consistent with all the others:   - Assign Shift + Z to Create A Depth Range - Assign Shift + M to Create A Radial Gradient (currently assigned Shift + Z)   Shift + M is not currently assigned in those three languages.   $ grep -i view/depthrange/key *.lproj/*.txt de.lproj/TranslatedStrings_Lr_de_DE.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=Shift+z" es.lproj/TranslatedStrings_Lr_es_ES.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=" fr.lproj/TranslatedStrings_Lr_fr_FR.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=Shift+Z" it.lproj/TranslatedStrings_Lr_it_IT.txt:"$$$/AgDevelop/Menu/V

Since I upgraded to lightroom classic from lightroom 5.7.1, imports are now importing duplicate images, even though I have checked don't import suspected duplicates. It happens on both my nikon and canon camera images.

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   You can't create a preset group containing a space when the option Preferences > File Handling > When A File Name Has A Space is set to Replace With An Underscore. Originally reported by David Brookens: https://www.lightroomqueen.com/community/threads/masks-as-presets.44625/    To reproduce:   1. Set the option Preferences > File Handling > When A File Name Has A Space to Replace With An Underscore.   2. In Develop, create a preset, and in Group, select New Group.   3. Enter "X Y" for the group name, and observe that Create is greyed out: 4. Instead, enter "XY" and observe that Create is now enabled.   5. Set the option Preferences > File Handling > When A File Name Has A Space to Leave As-Is.   6. Repeat steps 2-3 and observe that Create is not greyed out.   Obviously, preferences about file namin

In past versions of Lightroom Classic, if a map location was marked as "Private", all location data (including both GPS data and hand-entered IPTC location data) would be stripped from the photographs on export. As of Lightroom Classic 11.4, it appears that the "Private" switch on locations is no longer being honored: exported photographs that have been marked as being at a private location are exported with all location data included.   STEPS TO REPRODUCE 1. Create a location in the Map module, checking the box to mark the location as private. 2. Select a photograph and apply the location to it. 3. Export the photograph. Make sure that the checkbox 'Remove Location Info' is unchecked. 4. Inspect the metadata on the exported photograph (on MacOS, use the Finder's Get Info)   EXPECTED BEHAVIOR Latitude, Longitude and other location-related metadata should not be included.   ACTUAL BEHAVIOR Latitude, Longitude and other location-related metadata are present in the exported

Currently if you select the 'high' option for export sharpening, the resulting image is less sharp than the 'standard' option. The outputted file for the 'high' option is identical to the 'low' option.

Hello,over quite a long time it was easy to take photos with my android smart phone in heic format and import it and use it in LrC on my iMac.But suddenly, the heic images are not supported any more by LrC - they can still be open on the iMac. It's possible to load the files to the cataloge, but not even the preview in LrC is working. Unfortunatelly I can not upload these files here. I put them to my nextcloud server - hopefully the link will not break:https://cloud.hoststar.at/s/DjLJT22oZ8HofDk Can please somebody explain, whats the reason why the one file is supported and the other one not?And my be even tell me, what to do to make the not supported image work with LrC?(Until I have no better idea, I have to convert all my not any more supported heic files to jpgs and import then and for new pictures, I also have to use jpg as file format. You can imagine - this workarround is something I don't like to go...)

I have been living with this problem for a while where I get errors trying to move folders and files and rename folders in Lightroom Classic.Some of the time I can unselect al files and try again and it works but not always.Normally for clients I work catalog by catalog so don't really deal with the issue heaps but ive started going through all my old catalogs and preparing them to merge into one so now i'm seeing the error repeatedly.I've posted an example of it in an unlisted video to show the problem.You can see here https://www.youtube.com/watch?v=T10d5ZTGl6w&feature=youtu.beHelp appreciated , the lack of information and a simple "retry" button would save me so much time even with the problem in place.I've still got hundreds of catalogs to go and in each hundreds of folders so i'm going to see these errors a lot.Seems like lightroom is doing something with the files in the background and tripping over itself.ThanksRob

Hi, I'm using a new Wacom Intuos Pro with latest Firmware. According to Wacom's Diagnosis Tool the pressure sensitivity works fine from 0-100%.However, in LR I cannot use the pressure sensitivity as I'm always getting the full 100% (e.g. when using the adjustemnt brush). I know this was an issue in the past but should be solved by now.I'm using Windows 10, latest release, on a high perfomance PC.Does anyone have a clue where I need to search for a solution? Without that feature the tablet is almost useless....BTW: It's working in Photoshop without any problems...Thanks!

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.