Bug Reports

When you create a metadata preset using Save Current Settings As New Preset, LR incorrectly rounds the coordinates of the selected photo to the nearest second before saving them in the preset.   When the preset is applied to another photo, it will get the rounded coordinates, rather than the original.    On average, this can result in the second photo being about 17m / 55' away from where it should be.Tested in LR CC 2015.10 / OS X 10.12.3.To reproduce:1. In the Map module, select a photo A in the filmstrip.2. Paste these coordinates into the Metadata > Location > GPS field:37.899630, -119.221138(which is 37° 53' 58.668" N, 119° 13' 16.0968" W).3. In the Preset dropdown, select Edit Presets.4. Do Check None and then check the box to the right of GPS.5. Save the preset as "Test GPS".6. In the filmstrip, select another photo B and apply the metadata preset Test GPS.7. Zoom in the map all the way and observe that photo B is about 12m from photo A.8. Open the file "Tes

Hi,I've found a bug in Lightroom Classic, including the newest version. I'm using Windows 10.Please don't tell me that accents are special characters and software can't handle them. We are in unicode world and any char is easy to handle. So what's the problem?Duplicates detection is not working well for images with uppercase accent letters in the filename and it will import the same images multiple times. Detection is working fine with lowercase accent letters in the filename.I've tried "synchronize folder" and if there is any new image, it will import the image and than every image with uppercase accent letter... Usual import dialog has the same problem. How to reproduce?Let's have any image in LR catalog. Rename to Á.jpg. Click on Import. Choose directory which contains this image and check "don't import duplicates". This image with uppercase accent letter will be imported anyway. Which characters?I've tried "Á, Č, Ě", but there will be much more letters.Probably from

I’ve tried the forums and Google regarding the following issue. It seems that after updating to PS 2019 v20 or later, the dropletfeature in LR’s export fails if more than one file is selected at a time.  The only workaround seems to be to create thedroplet’s shortcut on the desktop or other directory, then manually select (byFile Explorer or File Finder) and then drag the whole folder to the shortcut.  Not sure if this is the case with Mac since I’mon Windows, but others on the forum are having the same problem with notresolution as late as 10/16’s post (before mine today).  Yes, this workaround  seems to work, but that goes against all objectivesof Adobe to make things easier and more efficient, not less so by requiring anintervening export, then an out-of-application drag/drop.  Please passthis along to the appropriate  to see if we can get a fix a.s.a.p.   I used this feature many times fordirect-to-slideshow alterations to cataloged file

Lightroom 7.2 is crashing when syncing.  I have to stop syncing (it has about 9,000 synced images with 2,000 pending) to avoid crashing.  I deleted my entire syncd library and have been rebuilding it in batches.  The problem was there before 7.2 upgrade today but still it happens.  There are no sync errors.  It is very frustrating.  Please help.Part of Crash report:Process:               Adobe Lightroom Classic [11405]Path:                  /Applications/Adobe Lightroom Classic CC/Adobe Lightroom Classic CC.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier:            com.adobe.LightroomClassicCC7Version:               Adobe Lightroom Classic [1156743] (7.2)Code Type:             X86-64 (Native)Parent Process:        ??? [1]Responsible:  &nbs

HiI use LR Classic 2019 for my photo and video archives. My Sony RX100mk3 shoots hd video in the MTS format. Adobe says it supports the file format but the recent 2019 LR Classic update has been nothing but trouble. Originally it completely messed up the capture date of the MTS video files. I posted here about the issue and got no response (https://feedback.photoshop.com/photoshop_family/topics/lightroom-still-inconsistent-capture-date-tim...?). In a response to that issue I thought I could try creating a new catalog of the same files/folders. That actually created MORE problems because now all of the metatdata on all videos has been lost as well. And the capture date issue still persists.So does ANYONE have any ideas about what the problem is? One thing I thought of is that since you can't technically write metadata to a video file maybe that info is stored elsewhere and was misplaced when I created the new catalog. When I look at the same video files in the old catalog the metadata i

I have a problem - with folders containing Polish letters... I did "synchronize" on main folder, as I copied a bunch of folders with pictures from another disc into, and suddenly pictures I had in the catalog for years showed up again. And if I look into the library, the same picture is displayed, say, 5 times. If I select four of the thumbnails and tell Lightroom to remove the pictures from the catalog, all 5 are gone (even the one I haven't selected) - so it is not a problem of duplicated files, but a corrupted catalog. Of course I've checked the folder in Explorer and the files are not duplicated. Seems that Lightroom has a problem with non-Latin characters... Other users report the same issue with German, Greek etc.

Throughout the process of working on images, I frequently must switch Treatment modes back and forth from Black and White to Color. In Lightroom Classic CC 7.5, the channel mixing panel no longer preserves the opposite treatment's settings when switching between treatments. The issue can be replicated by changing the Treatment to Black & White, altering the mix settings in the B&W panel, then toggling the treatment to Color and back again. The black and white mix settings will have been reset. The same holds for the opposite — working in Color, then changing to black and white and back again.This completely foils workflows in which one must toggle back and forth between modes in order to refine mix settings (e.g. assessing the image in color, switching to b&w to make changes, and so on). As a photographer who must often produce both color and b&w images, I have traditionally kept both versions in the same file in order to consolidate my library a bit. This problem preve

[LR 8.0 broke this again, and Adobe has reopened the bug. See All Replies.]LR 7.4 broke the keyboard shortcut for Group Into Stack for German. For previous versions, it was assigned to Cmd/Ctrl+G. But in 7.4, Preferences is also assigned to Cmd+G (Preferences was previously assigned to Cmd+W).The workaround (and Adobe's fix) is to change this line in TranslatedStrings_Lr_de_DE.txt: "$$$/Application/Menu/Edit/Preferences/KeyWin=Cmd+g" back to the original: "$$$/Application/Menu/Edit/Preferences/KeyWin=Cmd+W" (LR 7.4 makes no other assignments to Cmd+W.)  See this article for editing TranslatingStrings:https://www.lightroomqueen.com/custom-keyboard-shortcuts/Yet again, no quality assurance for changes to keyboard shortcuts. At a minimum, before allowing a change to TranslatedStrings to be checked into the main branch, there should two people doing a "diff" and reviewing each edit.

I tried to import photos into lightroom from an old harddrive into it's original folder on the same harddrive. I accidentally canceled it and now all the unimported photos are gone from the harddrive. Where did they go?Full story: working on a macbook proconnected an harddrive from a few years ago with old photos to macbook proopened lightroom>importnavigated to the folder I wanted, selected it, selected destination folder as the same folder as where the images were coming fromstarted the import, accidentally hit cancelwent back to original folder (through finder), and only the initial photos that started importing before I hit the cancel button are there. They're doubled, but all the other photos in that folder from that shoot are gone. Is there a way to find those? Where did they go? I've searched by image name, and nothing comes up for the missing files.Thank you.

Unfortunately, while 7.4 fixes the problem with photo:applyDevelopPreset(), it doesn't address the related problem with preset:getSetting().  See this previous post for the test script: https://feedback.photoshop.com/photoshop_family/topics/lr-classic-7-3-resets-settings-when-develop-p...Note: This conversation was created from a reply on: Lightroom SDK: photo:applyDevelopPreset() changes all settings, not just those of....

In Lightroom Classic CC 8.1, the inputs for develop settings accept alphanumeric characters instead of only numeric ones, which causes accessibility issues because it unnecessarily breaks keyboard shortcuts while the input is in focus.I'm a heavy keyboard user in Lightroom, so a common workflow for me in the "develop" tab is to move from setting to setting using the tab key, then modify the setting using the up and down keys, or by directly typing a number, and pressing "J" to toggle shadow and highlight clipping. In Lightroom Classic 8.0 and below, this worked fine. In Lightroom Classic 8.1, pressing a keyboard shortcut like "J" while an input is selected results in this:This of course results in a error message because "j" is obviously an invalid value, so why let me enter it to begin with? Could you go back to the previous behavior, which was ignoring non-numeric values on these inputs, so the keyboard shortcuts aren't broken?

Hi,Steps to reproduce1. Select a few images having all a different caption.2. Use the EMail photos... command or Export using the Email preset.3. Select "Include caption metadata as a description label" before sending.In the sent email, the captions are in reverse order.This bug is not absolutely new. We already had something similar when exporting JPEGs.

[Update: There are two symptoms of the same underlying bug introduced in LR 7.3:- preset:getSetting() returns all develop settings, not just those set by the preset- photo:applyDevelopPreset() changes all settings, not just those of the presetSee this post for a script demonstrating both:https://feedback.photoshop.com/photoshop_family/topics/lr-classic-7-3-resets-settings-when-develop-p...-- John Ellis]I use a script that uses "photo:applyDevelopPreset". If i use it with a partial preset (that have only a few or only one setting) it resets all other settings to default.Reverting to previous version until this is fixed.

When doing a pano merge of several files taken with a Phase One IQ3 100 back, the merge is always in the wrong orientation.  I have tried merging several horizontal panos, and LR always creates a vertical pano.  After merging I can use the rotate tool to obtain correct results, so the issue isn't serious, but it is a challenge to evaluate the pano when it's vertical, since it is much smaller due to the limit of the screen height.

Many places in the Map View have active text that if you click on it, a little note comes up saying "This place is at this address, View on Google Maps." This includes National Forests, Parks, etc. In my opinion, this pop-up is totally useless.But, more importantly, it keeps one from being able to select photos if they overlap with the active text. If you click on one of the little numbered place markers, the photos at that place are selected, then immediately the pop-up from the text below is activated, and the photos are deslected! The only solution I have found is to use View > Map Style > Satellite, which gets rid of these active text elements.Otherwise, selecting photos in map view is impossible. I'm enclosing a movie, which I hope demonstrates the problem.Lightroom Classic CC 7.1. Mac OS High Sierra 10.13.2.  

After upgrade I noticed as follows:While creating background task (for example exporting approx 200 photos with adding them to the catalogue) LR behavior is changed in Library view:a) the filters are constantly deactivated when new photos are added in background, it is impossible to choose another set of photos to create new export taskb) the folders tree view is all the time repositioned in such a way, that at the top visible is a row which is currently updated. It is hard to scroll down/up to select other folder...

Since the installation of mojave on my mac lightroom try to synchronize all my photos making the application using dizaines of Go and making it crashing.

If you export a book to jpeg and have the Page Grid turned on under guides.  The guide lines actually export in the jpeg!  Guide lines are not supposed to show in the export, and they don't show in a pdf export.  I almost send in an order with grid lines on the pages.

[Update: The shortcuts for rotate left and right were incorrectly changed in German, Spanish, French, Italian, and Swedish.  See here for details:https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-keyboard-shortcuts-for-r...- John Ellis]Hi Adboe,I like working with LR and it's the software product I use the most. It's a good piece of software and I never had any troubles working with it and I always was a happy user. (German keyboard layout on a Mac) But in the new LR version the keyboard shortcuts to rotate images have been changed, unfortunately to the worse. From (Command+) and (Command+.) to (Command+<) & (Command+#). You did fix something that was not broken.Here's what these new shortcuts do:1) They only work for me when an image I have fully zoomed into an image.2) The shortcut to rotate an image clockwise (Command+#) is the same as the one to zoom into an image (Seriously?! Did no one double check that before the release?).3) In the previous

I like the new feature in Lightroom 7.4 to add a color label to folders. However, when a (color added) folder is missing there is no way to remove the color lable. Also there is no way for adding a color lable to folders that are missing. Am i missing something?

... so it looks like in transform (CTRL-T) the movable center point with that crosshair icon doesn't snap correctly to the positions of the outer corner- and midpoint-handles.Please investigate.Seen in PS CC2019 (oct), Windows8, German.

Great to see the addition of the 'Has Edits' filter to the library of Lr 7.2 Classic. However, I was disappointed when I tried it on my library.During the catalogue upgrade from Lr 6 to Lr 7, I updated the Process Version on all images to the current Version 4. When the 'Has Edits' filter is applied, images that have had their process version updated are selected. Since this selects ALL my images since the upgrade to Lr 7, and only those images with actual develop settings that have been imported since the upgrade to Lr 7, the new 'Has Edits' filter is pretty well useless.In Collections, a Smart Collection can be created with Develop->Has Adjustments, which only includes images with develop adjustments, as expected. Using the new Develop->Has Edits in a Smart Collection includes images with develop adjustments and with the updated process version.The criteria for the Has Edits filter shouldn't include the images with an updated process version because over time, this will include

There's a bug in the Print module. Prints do not print as cropped on screen. It seems to only affect rotated images, here verticals, auto rotated to fit image cells. Notice on screen shots that the crop hasn't been maintained between screen/gui and print. It affects both Print to Printer and JPEG file, whether draft or not.The partial pixelation on screenshots are done in post. Focus on the borders/cropping on the top most row on the sheet of 4 image cells. Notice the bucket and shoe are cropped differently between gui and print.I hope you can quickly fix this, as it's frustrating not being sure my prints come out as intended.Using version 7.3.1 of Lightroom Classic CC, on macOS 10.13.5.

When you import a photo containing GPS coordinates and altitude, address lookup incorrectly overwrites that altitude with its own altitude derived from Google Maps. This bug was introduced in LR 7.3, 7.4, or 7.5, since it doesn't occur in 7.2, 6.14, or 5.7.1.To reproduce:1. Turn off Catalog Settings > Metadata > Look Up City, State and Country...2. Import this photo, which has an altitude of 32' recorded in its metadata:https://www.dropbox.com/s/dvrhnr59al2klf3/altitude-bug.2018.10.12.JPG?dl=03. Observe the Metadata panel correctly shows the altitude as 32.0'.4. Remove the photo from the catalog.5. Turn on Catalog Settings > Metadata > Look Up City, State and Country...6. Import the photo again.7. Observe the Metadata panel incorrectly shows the altitude as 0.0'.Note that the altitude provided by address lookup can differ by tens of feet from that shown by Google Earth Pro, which indicates that address lookup is not returning the altitude for the exact GPS coordinates

Create a preset called TEST that changes ONLY the Exposure.   This can be ANY adjustment but we will use exposure for this example.  Select a photo1. Apply preset. TEST. (Its added to History)2. Add Contrast.  (Its added to History).  This adjustment CAN NOT be an Exposure adjustment or the Preset will record in History in step 3.  3. Apply preset TEST  (Its not added to History) (It appears to the user it didn't work!)4. Add Highlights.  (Its added to History)5. Do an Undo.   (popup says "Undo Highlights")6. Do an Undo.  (popup says "Undo preset TEST" although this step is not in History)7. Do an Undo.  (popup says "Undo Contrast)IMPORTANT NOTE:  Step two can not be an Exposure change using the above Preset example.  If the Preset was only for Clarity than step two could not be Clarity.  It appears that for some reason Lr is checking to see if the preset is making changes to the sliders before recording a history step.It