Bug Reports

When I use Lightroom on Russian language export menu is cropped on the right side. I use the last version of Lightroom Classic on iMac 21.5 2017 and MacBook Pro 13 2017. 

In LR 5, the image in my second monitor renders blurry as if the photo is out of focus although the image is clear as a bell in the main editing screen. If I click off lens corrections, and then reactivate it, the second monitor window clears up and renders the photo clearly.

It has become painfully slow in Mac Mojave when I press “F” to view previews in Full screen. Takes about two secs to switch between pics, even if previews already exist. It goes instantly to switch between pics in Loupe mode. Tried turning graphic processor on and off, without significant difference. (On an 27" iMac 4 GHz Intel Core i7 24 GB)

I had upgraded to v10 of Lightroom Classic, and now this is extremely slow. On top of this, most time it crashes entirely, especially when I am starting Lightroom for a second time without restarting Windows (as in I close Lightroom, and restart some time later).   I have noticed that this issue is less frequent when my machine is on mains power, and wondered if this was also an issue with power profiles. The Better Performance profile is definitely less issue prone on v10, compared to the Better Battery profile which is the default.   I have tried downgrading to v9.4, but of course now my catalog files are not compatible with earlier versions, and I do not want to lose images I have imported since.   I would be grateful for help with this, as I am effectively stuck without my most used software at the moment.

Copy or sync crop and spot removal develop settings causes wrong results at portrait photos. The crop and spot removal settings are wrong by 90° after copy/paste or sync.   Here an example photo to reproduce. - Importing in Lightroom Classic 10 - Create a copy by edit in Photoshop  - Make a small edit, e.g. add text "Photoshop edit" and save. - Add a crop and spot removal e.g.   - Copy or sync the crop and spot removal develop settings to the same/original photo before the edit in Photoshop. But the result of the crop and spot removal is totally wrong:

Hello,   Since upgrading to Lightroom Classic v10.0, all UI-related functionality is painfully slow. All editing functions are working correctly and quickly but scrolling through the catalogue or even scrolling a side panel is taking many long seconds to refresh. Unreasonably long.   Disabling GPU Accellaration has no affect on my Lightroom's performance.   macOS Mojave 10.14.6 Mac Pro (Late 2013) 3 GHz 8-Core Intel Xeon E5 32 GB 1866 MHz DDR3 AMD FirePro D700 6 GB  

On macOS you can have the Secondary Display visible whilst you are cropping to you see a full screen view of the current crop boundaries.   As you adjust the crop bounds rect the secondary display should show a real time update of the crop.   This seems to only work up until the first pause point but then doesn't continue to live update.   1. Drag bounds 2. Pause, mouse still held down 3. Continue to drag bounds   You will see that there is a point where the second display stops responding to mouse drag events.

The boolean criterion "depthMap" for catalog:findPhotos() doesn't work. It always returns an empty array, for both "isTrue" and "isFalse".

When I try to import video files into my catalog it tells me "There is a problem with the video file (12)".  There is no issue with my video files.  I removed a video that had previously been imported to my catalog with no issue and tried reimporting as a test and it would not import.  I received the same message.  I created a new catalog to test and same message and video would not import.  This is a recent issue as i have been able to import videos with no problems.  The issue is occurring on both my Mac Book Pro and my Mac Pro.      

Please get dynamiclinkmediaserver under control. It hogs huge amounts of processor even when no Adobe apps are running. All I can do is to keep removing the dynamiclinkmediaserver folder from Application Support. But then it gets regenerated when I run Lightroom Classic CC

Hi, By simply launching the latest Lightroom Classic (9.3), it will set the shared media caches locations for Premiere Pro, After Effects, Audition and Media Encoder to the default Lightroom video cache location. /Users/{USERNAME}/Library/Caches/Adobe/Lightroom/Video Even though Lightroom's own media cache location might be custom set to something else.  Running the latest app versions available on MacOS Catalina 10.15.5 Does this also mean that the rather small cache size limitations usually set in lightroom now apply to the video editing apps shared cache too? Will Lightroom also delete cache files from Pr, Ae, Au, Me ? This bug has been reported for years. It's been marked as solved before by suggesting newer versions would not show this behaviour. Well its still here, I guess someone has to really look into this. @Adobe: Could you please provide a workaround, if there is one, for the time being until this gets eventually fixed? CheersAndi

Hi all,I'm facing the same issue since a couple of days.Followed instructions from above, deleted the pictures that was causing the issue, restarted LRC but now syncing is stuck on 10 remaining pictures with no apparent sync issues/ errors.As some people indicated in the past: I'd be glad to hear any tips from you guys, or better yet, some help. It's a complicated issue, and I'd be very happy to make peace with my ever-turning syncing symbol.Kind regards,DieterNote: This conversation was created from a reply on: Lightroom Desktop: 1 Syncing Photo Never Syncs.

Hey guys,I know that this has been written about 1000 times (most of them years old) in this and in other forums, but I cannot import video files into the catalog.Windows 10-64bit, LR 9.1 Build 201911291132I tried: uninstall, purge video cache (both from the settings an in lightroom), switched off all kinds of acceleration, setup a new catalog, uninstalled quicktime, reinstalled quicktime, uninstalled VLC, and everything else I found on the web - with zero impact.Any further ideas? Thanks for any helpful tips...Cheers,B.

LUT Color Profile Problem in Lightroom Classic

I updated to 9.3 this morning. Healing aspect of spot removal tool now has bleeding in many previously edited pictures which did not previously have bleeding -- what was before a clean background with spots removed now has ugly bleeding of color, and I can't use the healing tool properly in new edits either -- bleeds result.   What can I do to fix this -- I am pretty concerned, this has affected many photos.  Thanks.

Hi. I'm creating a new book in the book module. I have a previous collection with the relative saved book, now I have a new collection from where I'm gathering the pictures for the new book. The problem is that when I select the new collection, in the film strip I see also the pictures from the previous one! So if I let the new book auto fill I get the two collections' pics merged together. I found kind of a workaround by deleting the pages of the old pictures, but when I hit "create save book" it creates the new book with all the pictures (old+new) again! Please help! Thank you.

Hi there,   When using the «Tab» key to quickly navigate slider settings in the brush panel, Highlights are skipped over- the selection will jump from contrast down to shadows. I know this is only minor but it slows workflow. I have not noticed any other similar jumps yet.   I have also noticed since upgrading that the erasing brush stroke will sometimes not show unless I change to a new image and return to the image I am editing. It usually occurs when erasing straight lines (while holding the «Shift» key).

I have discovered , and others have confirmed, that if you sync a photo that has been edited in PS and saved as a PSD the syncing status will say the photos are not synced.  See photo below.  In fact they are synced but they remain in the un-synced status forever.  When you exit the program you get an error that there are un-synced photos.  Other photos edited in LR are not affected.  I believe the problem only occurs when you edit the photo a second time after it has been previously added to a synced collection.  The majority of my work flow involves editing raw in Lightroom Classic and then round-tripping to Photoshop resulting in a psd returned to Lightroom Classic. I frequently put the edited photos into a synced collection. If I re-edit the psd, the file appears to sync across platforms but Classic reports an endless sync in progress. When I remove the file from the collection, the sync status turns green almost immediately. When i put the edited file

[See here for a step-by-step bug recipe: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-imported-dngs-not-showing-bw-mix/6062739e86563b6ed6c2339e?commentId=6063b17b439e980adff71ff3]   Hi everyone,   Running the recent Lightroom Classic v10.2 update on my macOS Big Sur 11.2.2.   I imported some DNGs where the Treatment was set to Black & White and the Profile was Adobe Monochrome. By defult, these setting should trigger the B&W Mix panel to appear, but instead HSL/Color is showing.   Currently, I can fix this by switching the Treatment to Color and then back to Black & White to get the B&W Mix panel to appear with all the sliders shown with the correct settings, but this is tedious.   Thank you,Chrysta Giffen

I have a problem with version 10.0,the photo is of poor quality in the library and in the develop module. I use smart previews (the disk with the original photos is disconnected).smart previews in version 10.0 have poorer quality than in version 9.4When I install the older version (9.4), the same photo with the same preset is of better quality (also smart previews). It looks like there is a higher grain in the photoHere are photos exported from smart previews. Tested on: Mac pro 2013 (6core, 16gb ram, D500) Macbook Pro 2014 2,7 ghz 4 core, 16gb ram   10.0: 9.4: Photo exported after attaching a disk with the original photo:

Applying to a photo a preset that refers to a custom .dcp camera profile and then copying settings from that photo to a virtual copy produces incorrect results on the copy, and the Library thumbnails fail to update.  Tested on LR 10.1 / Mac OS 10.15.7.  Original report: https://community.adobe.com/t5/lightroom-classic/strange-bug-with-profile-and-white-balance/m-p/11735437    This misbehavior is different from the LR 10.0 bug fixed in 10.1: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-problem-when-using-copy-and-paste-or-sync-in-develop-module-with-wb-changed/5f94581872a09d5d5ced2f09    To reproduce:   1. Import the camera profile Canon EOS 5D Mark IV Kodak Portra 400 UC C.dcp and the preset C - Kodak Portra 400 UC.xmp from here: https://www.dropbox.com/s/gdaxo96wevbmqx6/white-balance-copy-bug.2021.01.07.zip?dl=0    2. Download and import the sample Canon EOS 5D Mark IV raw from here, with the option Build

In LR 10.1, photo:getRawMetadata ("stackPositionInFolder") returns a string, not a number, when the photo isn't a member of a folder stack, breaking my popular Any Filter plugin:   That string, "---0", has the pattern of strings used by 10.1 to record the custom-order positions of photos with collections and folders, so very likely this bug is fallout from the fix to custom-order position in 10.0 and 10.1: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-limit-of-52-reorderings-in-customordered-collections-and-folders/5f5f45b94b561a3d425c094f?commentId=5f91f13549d3ca75248dcdf2  https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-when-trying-to-add-files-to-collections-i-get-this-error-0-attempt-to-compare-two-nil-values/5f9091ea35f40c2520b9ecc4       

Hello I'm sorry for my bad englishthere is an error of french translationIGNORER and ANNULER is the same action in frenchIGNORE should be replaced by  SUPPRIMER  or EFFFACER ( DELETE)Have nice Day

After the Lightroom 7.3 update, .SRW files from Samsung NX cameras are filtered out when trying to import from an SD card. Only JPEG and other types are shown. The issue appears if the SD card is selected as the Source under the Devices section. The files show up normally if the SD card is selected under the Files section.Also. If the SD card is inserted after Lightroom is opened, then the .SRW files show up everywhere as well.It appears to be a bug with the .SRW extension, because you can take any RAW file that Lightroom would normally detect in the import dialogue and rename its extension to .SRW and then it won't be detected, unless I do the workarounds I mentioned.In LR versions 7.2 and before, the issue isn't apparent and the .SRW files are detected in all situations.

Possible issue with use of graphics processor: rendering in Develop Module of wide-gamut colours in error, LR6, problem goes away when "Use Graphics Processor" unchecked, problem didn't occur in LR5.x Graphic card: NVidia GeForce GTX 550 Ti, latest drivers (350.12 but also occured with 340.52). Win 7 Home Premium, 64-bit, LR6, CC version. Problem is this: with a wide-gamut monitor, in Develop Module, highly saturated blues are the wrong tone. They have to be VERY wide gamut: the problem occurs only with blues outside Adobe RGB gamut. These blues are rendered OK if "Use Graphics Processor" is unchecked. Obviously, in Library module this isn't a problem as colours are limited to Adobe RGB anyway. Also, even in Develop Module, colours are OK on the 2nd Lightroom monitor window, wrong only on the main Lightroom monitor. If I move the main window to the other monitor, then it's that monitor that's now wrong. In other words: it doesn't depend on the monitor (one's HP, one's Eizo) nor on the