Bug Reports

This is driving me nuts.  All of my presets aren't working properly.  I reset all of my settings, etc. When I import photos with a specific preset it doesn't apply it properly.  It's like it's applying the old Lightroom algorithm.  This is frustrating.PLUS, it doesn't work when I create a brand new preset in this version of Lightroom.  I setup a new preset that will apply Auto Settings and when I import it still applies old settings, it seems like it's using the Auto Settings from a few versions of LR ago.  It's applying settings on import, but not the correct Auto Settings if that makes sense.  All of the other settings, like Clarity, Sharpening, etc still work.  Oh, and Auto White Balance doesn't work on import at all anymore and hasn't since the update before this most recent one.In the past, what 'fixed' it for me was to go to the user presets file and open one of the presets with Lightroom (right click, open with Lightroom) and then it worke

Importing a file, renaming it in Lightroom, then importing any other file with the same name generates incorrect records and does not import subsequent files. This is happening when scanning to a folder with autogenerated names, then using LR to import the files and rename.1) Scan some slides to a folder named e.g. YYYY-MM-DD-sequence.TIF2) Import into Lightroom (synchronise folder)2) Rename or move those files elsewhere using Lightroom3) Scan more files which are again auto-named, with the sequence restarting at 1 because the first ones are no longer there4) Import the new files (synchronise folder)Actual: LR notices the new files but creates duplicate records for the first set of images, even if they have been moved to a different folder and renamed. Removing one of the duplicate records actually removes both records, requiring a second "sync folder" to re-import correctly.Expected: LR creates new records for the new files in the correct folder.

When I use the targeted HSL Saturation tool to select a color, the Magenta slider gets highlighted, but as I move the cursor, it's the Red slider that does most of the moving. Then the undo bezel shows "Magenta" as getting undone (even though the changes to Red get undone also).  Here's a screen recording:https://www.dropbox.com/s/kvnxhcs0v0iehda/lightroom-hsl.2018.08.29.mov?dl=0Tested in LR 7.5 / Macos 10.13.6..

Hi, I've noticed this issue with LR Classic 8.1 and Win 10 (1803). I had experienced this problem on a few occasions, but couldn't notice a pattern until now: it only happens with desaturated tiff images (maybe with psd's too). Then I found this report, but I see that, in theory, it was fixed with v7.5.Anyway, I've captured this small video to show the issue, so that others can check too:https://youtu.be/AmBHYC90McsIs it me or is this same problem back? I've also tried disabling GPU, it didn't seem to make a difference.Thanks.Note: This conversation was created from a reply on: Lightroom Classic: Luminance range masks do not work for grayscale images.

Using LR 8.1with Windows 10 ver1803 when exporting a JPEG file to DNG file format the DNG file does not appear in the LR catalog and the Library module’s Import and Synchronize Folder functions become grayed-out and unusable. Closing and reopening LR restores the Import module and Synchronize folder functions and the DNG can be imported. The DNG file is being created, but not added to the catalog. Using any other file format (raw, TIFF,PSD) works as expected with no issues. I uninstalled LR 8.1 and chose the option to ‘Delete All Preferences,’ but the issue remains!The JPEG to DNG file format export fails as described above when using the below Export module settings. If 'Add to Stack’ in the Export module's 'Export Location’ pane is NOT checked the JPEG to DNG Export works as expected.

In Lightroom Classic CC, if "Replace illegal file name characters with:" is set to "Similar Characters", all export presets will show a filename preview as follows: (filename).(space)(space)(file extension of original file)..(new file extension). For example, if the export is from original file Photo.tiff to jpg, the preview will show "Photo.  tiff..jpg". Exports will be named correctly (without all the extraneous characters), but the extra characters are worrying when in the Export panel.

I recently upgraded to Lightroom 6.2.1 So far there has been a lot of fuss over the import dialog... ok, well sure, it has a few issues, but they can be either worked around or just revert back to 6.1.1 I would like to report and ACTUAL bug in 6.2.1 My D drive recently ran out of space... I tried deleting some stuff I didn't need, but still it kept running out of space... So I finally ran windirstat and had a look at it.. Nearly HALF of my drive was FULL of D:/temp/Adobe Local/Lightroom/caches/video/media Cache Files. Now here's the kicker... NONE of these video files are even on the hard drive that has my catalog on it. My lightroom database is on drive L:\ all my lightroom photos and very few lightroom videos are all on L:\ I have a few scans on drive K:\ that I import to lightroom... but these videos are ALL on Drives E:\ and F:\ here's another thing.. I knew Adobe wasted space caching videos, and I do have a GOPRO and I record a little video,.. .VERY LITTLE, maybe 1 video a year...

Several years ago (yes, YEARS, not months) the View Info menu option and short-key (I) in LR's Print Module stopped working. Clicking the option on or off in the menu nor using the short-key (I - capital i) resulted in ... nothing happening.I and others have repeatedly reported this problem during all these YEARS, only to be promised it would be solved "in the next update"... which were obviously all promises that were never kept. Why is such a huge bug being allowed to live on for years, annihilating a very useful feature that allows users to see on what printer and what paper size the print is going to end up on before risking to waste hugely expensive ink and professional paper? Why do developers no longer check the functions they build into their software?Why do support engineers ignore or stop following-up on bugs that are being reported by users who pay for software that is released in alpha-phase, leaving the beta-phase to the "community" of users, and never even bothe

Hi,I'm seeing some strange behavior when using *presets* to call *enhanced profiles* that are based on  top of *custom RAW DCP profiles*... **Basically the preset preview look right, but the changes don't "stick" after selecting**You can see a video demo of bug and example files here: https://www.dropbox.com/sh/xbftfuwwbd0pjq7/AAA9LxB81dZf_Tp5gs3fzUpia?dl=0As an example: I have a regular preset called "Custom Preset". The preset is calling an enhanced profile called "Custom Look Profile." Inside that custom look profile, it is using a custom DCP profile called "Custom DCP Example" as it's base (instead of Adobe Standard). The preset preview appears correct when hovering over it... But after I apply it, the moment the mouse leaves the preset name, the image changes unexpectedly...(may be hard to see in this example, but look at the sky detail change).You can see see that the enhanced profile has been selected on the right, but it seems to be

Hello, I am using the DNG Flat Field Plug-in for Adobe Lightroom. It has worked flawlessly for since January, but now I'm getting errors, when I try to apply it. I have already tried to reinstall the plugin, but this does not solve the issue. I get the error message, attached below. The error only occurs, when GPS data is attached to the dng files. As the plugin was last updated 2013, I think, there's a incapability causing this issue. As this plugin is necessary for people using technical cameras like me, it would be great if you could update the plugin, so that it works without hassle with the Lightroom CC 2015. Maybe you could also code the feature inside of Lightroom. Thanks very much!Kind regards, Sebastian 

It would be handy to allow users to select an Import Preset as a default, instead of what appears to happen that none are selected when you open the Import dialogue pane.Even with only one configured (See screenshot) I still have to go in & select it each time.

When Trying to restrict the effect of a gradient in a grayscal image with a luminance mask there is no visible difference in effected areas.Running Mac Os X 10.13.4 on a 2014 Macbook Pro 15"

[All the problems with the tone curve toggle switch not getting copied by Copy/Paste Settings, Auto Sync, Sync, Snapshots, and SDK's photo:getDevelopSettings() were fixed in 7.4.  Adobe has decided not to fix the problem with presets: https://feedback.photoshop.com/photoshop_family/topics/pv2012_snapshots_not_saving_tonecurveenable_s...][See this post for a precise recipe for reproducing the bug: https://feedback.photoshop.com/photoshop_family/topics/pv2012_snapshots_not_saving_tonecurveenable_s... Also, the SDK method photo:getDevelopSettings() fails to return the parameter "EnableToneCurve", which is surely a symptom of the same underlying bug. See:https://feedback.photoshop.com/photoshop_family/topics/pv2012_snapshots_not_saving_tonecurveenable_s...--John Ellis]I created a snapshot, made some adjustments, then selected the snapshot, but it looked different than when I took it.Traced it to the ToneCurveEnable setting which was disabled when I took the sn

On Mac, you can enter an accented "o" by holding down the "o" key and then selecting the appropriate variant:But when you do that in the Metadata panel's Caption field, you just get a plain "o". However, you can use the Mac's Input menu to enter an accented "o" (both the Latin Small Letter O With Acute and the Latin Small Letter O followed by Combining Acute Accent).Screen recording: https://www.dropbox.com/s/zkyp4pfw8031vgt/holding-down-o-key.2019.04.22.mov?dl=0Tested on LR 8.2.1 / Mac OS 10.14.3.

When I upload images to Adobe Cloud via LR CC (on Desktop and my iPad), when I try to sync those images back to LR Classic CC, occasionally I will get corrupt images. Basically, it's not the entire file I uploaded. Everything looks OK in LR Classic CC until I try to export the corrupt image.To be clear, it's not every image. Maybe about 1-4% depending on the situation. Also, I've seen this happen on the Desktop app AND the mobile app for iOS on my iPad.What does Adobe do to protect the integrity of my uploads? Do you keep checksums of the file before upload to ensure it's the same one I download later? This is a real dealbreaker for the 1TB storage if I cannot trust the process!

LrSystemInfo.appWindowSize() returns incorrect values for height depending on Window > Screen Mode, making it impossible for plugins to know the maximum size of windows they can create. Since the SDK doesn't report the current screen mode, it's impossible for plugins to know the precise maximum size.The following tables show the heights returned by appWindowSize() for the combinations of operating system, the operating-system display scaling, and LR's Screen Mode.  "Useable window height" is the height of that part of the app window that SDK dialogs can occupy.  Erroneous return values are in red.Mac OS 10.14.3:Windows 10:A related bug is that Windows appWindowSize() and displayInfo() report units in physical pixels, rather than the scaled pixels used by LrView. (The Mac SDK doesn't have the bug.)  This makes it doubly hard for plugins to know the maximum size of windows they can create:https://feedback.photoshop.com/photoshop_family/topics/lightroom-lrsysteminfo-disp

It is not possible to copy nor synchronize Black & White Mix settings, as the option is missing from the dialog. (While creating new preset, Black & White Mix option is present.) Even if "Check All" button is pressed while copying or synchronizing settings, Black & White Mix is not copied/synchronized.Version: Lightroom Classic CC 7.3

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.