Bug Reports

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

Following on from our twitter conversation yesterday, regarding LR v9.4 support for Z5 with FTZ and the Nikkor 16mm f2.8 lens. Please see the video for the issue. Regards Mark ps I say in the video Z7, which is wrong it's the Z5  

LR doesn't import GPS coordinates stored in QuickTime:GPSCoordinates in MP4 videos (.mp4), though it does for Quicktime videos (.mov). To reproduce:   1. Import the .mp4 and .mov files in this folder: https://www.dropbox.com/s/6hga1ka2tm61v0o/mp4-gps-bug.2021.02.25.zip?dl=0   2. Observe that the .mov shows GPS coordinates in the Metadata panel, while the .mp4 does not.   3. Use Exiftool to see that the files have identical QuickTime:GPSCoordinates:   $ exiftool -quicktime:gpscoordinates mp4-gps-bug.MP4  GPS Coordinates                 : 34 deg 0' 0.00" N, 38 deg 0' 0.00" W, 0 m Above Sea Level $ exiftool -quicktime:gpscoordinates mp4-gps-bug.mov  GPS Coordinates                 : 34 deg 0' 0.00" N, 38 deg 0' 0.00" W, 0 m Above Sea Level   Tested on LR 10.1.1 / Mac OS 10.15.7.

Hi, have been struggling to find an answer to my problem:If i draw a face region or if a photo has already the data of the face region and i rotate it 90° and i remove the photo from lightroom and re-import, it won't recognize the facetags despite that the information is in the XMP.*As long as the photo is horizontal (that is normal orientation), there is no problem, i can delete the photo from Lightroom and re-import and it wil recognize the face region with the person's name.i have tried to edit xmp metadata in all sorts of ways with exiftool to see if that would fix the problem but havent' had any luck.I would appreciate any help to fix this issue.-UPDATE: I posted this issue in Adobe Forums https://forums.adobe.com/thread/2626690 and we got to the conclusion that it is A BUG, so if this is correct please this has to be solved.Thanks.

The bug that I reported here has not been squashed in the latest Lightroom.The problem is hysteresis in the response of points on the tone curve control when following mouse movements.If you drag a point (say, the white point) in the Tone Curve and move it back and forth, after a few drags you will not be able to put the point back in the upper right corner of the response panel.The underlying cause is that (a) the point does not move directly with the cursor (LR hides the cursor so you can't see this, but when you let go of the mouse button you will see that the cursor does not align with the point, (b) as you drag, the relationship between the cursor position and the point changes, when the point hits the right edge of the box and the cursor continues to the right, then when you move the cursor back to the left it does not "pick up" the point at the same location that it "left" the point, and (c) the (invisible) cursor is limited by Mac OS to stay on the screen.The work-around (

Ever since the V10 update my email out of LR Classic has quit working, but instead returns the above error message.  I have reset the preferences, deleted and readded my email client to no avail.  Still does not work and from the forum, it looks like there are lots of nil value errors happening. System specs: OS Name Microsoft Windows 10 HomeVersion 10.0.19041 Build 19041Other OS Description  Not AvailableOS Manufacturer Microsoft CorporationSystem Name JOESALIENPCSystem Manufacturer AlienwareSystem Model Alienware Aurora R7System Type x64-based PCSystem SKU 0858Processor Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)BIOS Version/Date Alienware 1.0.22, 6/9/2020SMBIOS Version 3.1Embedded Controller Version 255.255BIOS Mode UEFIBaseBoard Manufacturer AlienwareBaseBoard Product 0VDT73BaseBoard Version A00Platform Role DesktopSecure Boot State OnPCR7 Configuration Elevation Required to ViewWindows Directory C:\WINDOWSSystem Directory C:

Technical Information: Lightroom Classic Version 8.4.1Operating on an Apple MacBook Pro 2016, 2.6 GHz Quad-Core Intel Core i7, 16 GB 2133 MHz LPDDR3 With macOS Catalina 10.15Description: Normally exporting jpeg's as I do, and it crashes for no reason. I have to foce quit the application and hard restart the computer for me to be able to boot Lightroom again. Very strange issue. My friend is having the same issue on his older MacBook. This is incredibly frustrating as I need to export many photos....

In Lightroom CC Classic v8.2 I have an image that I flipped horizontally.Then I 'open in Photoshop'  (version 20.0.3) and it is upside down.If I rorate 180 degrees, then it shows correctly.It is not clear if the fault is with LR or PS.Windows 10AMD

Since the last Update to V10.1.1 i cant't "Light out" the second screen. It only works on first screen. Is It a bug or can I fix this problem? Thank you.

I have folders marked as favorite and I cannot unmark them. When I open the context menu, I can mark it as favorite (even though it already is) and then unmark it, but the star next to the folder icon stays.   Since I updated to the latest version, I can mark and unmark new folders at first without any problems, but later not anymore.   I think the only thing I did was filtering on the favorite folders only followed by trying to unmark a folder while the filter is active. Afterwards its not working for any folder anymore.

Since v10 'include subfolders' on import screen always resets to not showing subfolders, in v9 if you clicked 'show subfolders' it persisted until the checkbox was changed. Can we restore this behaviour to v9 version.

Shift+T should toggle between brush and edit mode. However, it does the same as T, it shows/hides the toolbar.

LIGHTROOM 4 I migrated from LR3. I never installed the beta because I didnt want to deal with BETA ISSUES. I wanted a product that worked as it should immediately out of the box. [Does ADOBE understand that???] I BOUGHT LR4, installed it on my computer, updated the library, and then opened an image I had been working on but not completed in LR3. I clicked to update it to the newer processing and IMMEDIATELY there was torrential lag. My CPU Usage meter showed maxed out. I decided to reset the image and start from scratch. This worked for a very short time. As soon as I began using the adjustment brush the lag started building - the more I used it, the worse it got. I then decided to open an image that had never been opened in LR3. Same issue. As soon as I started using the adjustment brush or the spot removal there was lag. and it got worse and worse the more I used it. Again my CPU meter showed maxed out. My RAM never jumped about 50% utilized though.... I am running: Intel® CoreTM i7-

Since I have updated to LR Classic, I have an issue with my keyword list. I have hierarchical keywords. Some on the top level are numbered and some of the top level have no child keywords. Since the update the keywords on the top level and the second level hierarchy are no longer in alphabetical order. Some keywords seem to be ordered correctly, but several others are not. The keywords which are not ordered alphabetically seem to get ordered by a change/creation date or so.I do not use LR CC and have not done any keyword changes on my mobile devices.Has anybody an idea, what I could do about it? Is there I setting, I have missed?