Bug Reports

I've tried the dust cover in my latest draft, and the only way I manage to edit it to include left (at beginning) and right (at end) inside covers is by trial and error with front and back covers.   That is, there should be FOUR parts to edit - cover, back, AND left and right inside dust cover.   Plus I can't move anything around on the dust cover.   I have to go back to develop and change/crop size.  Am I not seeing something?   Or should that code be updated to work for the 4 images of the dust cover?

This post needs a body  

I use a laptop when travelling.  I have exported the keyword list from my desktop to the laptop.I added a new photo onto the laptop with the keywords"barkblur' and 'persontest".  They show on the laptop keyword list.  'barkblur' is an exisiting keyword and shows in the folder structure. Whilst 'persontest' a new keyword shows outside the folder structure.I then selected the folder and chose export as catalog and ticked export negative file and include available previews. and saved it to an external hard drive as TEST. Then copied the TEST exported catalog folder to my desktop computer.On the desktop the only one of the keywords show on the photo - 'persontest' only and not 'barkblur'. Person test is a new keyword and bark blur is an exisiting keyword. Image is not available  IN the keyword list the 'barkblur' numbers have not increased and the 'persontest" which is the new keyword does show. Image is not available I hope someone can help with this. Thank you

When deleting files in a folder LR often will not delete one file, even though it is not being locked by another program.  This behavior, at least in Windows, has been present for more than 8 years.  Please, please fix this.If you select multiple images in the loupe view thumbnails you can only change metadata on the first selected image.  You must change to grid view to change them all.  However, other actions, like remove or delete work on all selected images while in loupe view.  This inconsistent behavior is confusing.  Please enable selections for all activities in loupe view.

I was using LR 8.2 today and tried to use the Enhance Details. An error came up saying I needed to update Windows 10 for it to work. I updated Windows 10 and ever since Lightroom Classic CC and CC for Desktop crash upon startup.I have uninstalled Classic CC and gone back to 8.1 and I am able to work. This is very frustrating.

Since I upgraded to V8.3 of Lightroom Classic I can no longer export my files to our Synology Network System, I get the following error message "The specified folder in not writable" After contacting support they were not able to resolve my issue, they maintained that it is a network issue on my side. I could not find any answers here or anywhere on the internet and decided to report this issue.Because I share my processed photos with the rest of the office, my only solution was to un-install V8.3 and go back to V8.2.1, by doing that it resolved my problem.So yes Adobe you have network issues in V8.3 as version 8.2.1 works perfectly when saving files to a network drive.

Hi,I'm noticing an issue in Lightroom Classic CC, in the Library module, when navigating between Collections. This is with the 8.2 release on Windows 10 1803, although the issue was present with 8.1 as well.If I am viewing a collection that is synced with Lightroom CC, and then select a published collection, the grid view in the published collection does not show the groups by publish status (Published Photos/Modified Photos to Re-publish/New Photos to Publish), and hitting the Publish button does not publish any new photos in the collection (e.g. export and upload to Flickr).I can work around this by first going to a non-synced collection, or a folder in the file system view, in which case the published collections work as expected.It is not a work-stopping issue, but it is annoying, especially as I make more and more use of Lightroom CC syncing.Would you be able to help?Thanks!

Several people experience Titles and Captions are removed from images when browsing through synced images in CC mobile for Android. Data is removed in CC classic main catalog as found on main computer with catalog as well. Disappeared for ever.

The documentation lists  photo:quickDevelopSetWhiteBalacne( value ) And that, indeed, is the correct call to set white balance, misspelling and all.So the documentation is correct, and I've had to code it that way in my plugin. Are you planning to fix this by including another properly-spelled function that accomplishes the same thing? Unfortunately, you'll probably have to leave the misspelled version in to avoid breaking current code.

Currently using LR version 8.0 build 1193777I have spent hours designing a book in the book module. Now I am finding many bugs in the program. Some examples:I saved the book, intending to come back to it later for further work. The saved book is essentially not editable.* Try to change a page layout, such as from two photos to three -- the change at first shows but then does not stick; it reverts to the old version.* I decided to change the layout from 10x8 to 13x11. This cannot be done. After as dialog warning of possible unexpected changes -- the thumbnails do not change. Go off to another collection and return to the saved book -- all the page settings show the old size, etc.* After saving the book, there is no longer a "Create Saved Book" button to save changes. I can find no way to get the "save" button back.Searching online I find many complaints of similar problems. Nothing works to fix the problems. The common recommendation is to revert to version 7.5. This works for some peop

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!