Bug Reports

Develop displays histograms for identical images with small but noticeable differences, and these differences depend on the order in which you edit the files.  By itself, this probably doesn't have any impact on users, but it may indicate a worrisome underlying bug in how Develop caches computations.See this screen recording, and follow these steps precisely:1. Download this sample raw into a folder and make a copy of the raw in the same folder. Rename the two raws A and B.2. In LR, do Preferences > Performance > Camera Raw Cache Settings > Purge Cache. 3. Restart LR.4. Import A and B.5. In Library, select A and make a virtual copy.6. In Library, select A and Cmd-click B (order is important).7. Go to Develop, and use the cursor keys to switch between A and B.  The histograms appear identical.8. Go to Library.9. Without changing the selection, go to Develop, and use the cursor keys to switch between A and B.  The histograms now have small but noticeable

In Lr Classic 8.4 open the Preferences dialog and on the General tab uncheck the "Automatically check for updates" option. Close the Preferences, then close Lr. Relaunch Lr, open the Preferences and look and the "Automatically check for updates" option. I find that it is always checked.I edited the Preferences file and found thatnoAutomaticallyCheckUpdates = true/falseis always set correctly on closing Lr according to whether I have unchecked/checked the "Automatically check for updates" option in the Preferences dialog. The problem is when Lr is launched again, it seems that although the Preferences file option is being loaded, it is not being used to initialise the "Automatically check for updates" check box state.I think it is an initialisation problem because unchecking the option, closing the Preferences dialog and then opening it again shows it unchecked. However, closing Lr when the option is unchecked and relaunching always shows the option as checked, even if internally the op

Hello as a keen birder, I have a multitude of pictures of birds which I classify by Bird family(as title), bird name(as caption) ,date of picture taken and eventually sequence.I used to use the EXPORT function and do a rename of the DNG picture into a new Jpeg file name.As Title I had the format like as example 23.100, which would mean bird#100 out of family #43.So my resulting new Jpeg file name would be 23.100-birdname,date-sequence.Jpeg.However with version 9.1 this does not work anymore. ! ( Not sure when the change occurred as I went recently from 6.4 standalone- which is OK , to classic 9.1)The title with such a numerical format is ignored when I edit the Rename Preset like {title}-{caption},{date}-{sequence}.When I leave out title in the previous string, the rename works ( obviously with just caption,date and sequence).If I leave it in the string, just the first numerical digits before the dot , in the example 23, are shown, without caption, date,sequence !If I change the title

The Presence subpanel of Develop's Basic panel doesn't display properly when the process version is 2:Tested on LR 9.0 / Windows 10. It occurs with someone else using different graphics hardware and an up-to-date driver, so almost certainly not a driver issue:https://community.adobe.com/t5/Lightroom-Classic/v9-0-for-Windows-not-displaying-Texture-or-Dehaze-Sliders/m-p/10726166#M162655

When a raw that's been rotated 270 degrees CW in the camera and flipped horizontal in LR is opened in Photoshop from LR, it opens upside down. To reproduce:1. Turn off the option Catalog Settings > Metadata > Automatically Write Changes Into XMP.2. Import a raw that's been rotated in the camera 270 degrees CW (90 degrees CCW). Make sure no .xmp file for the raw is present before you import. (The raw should have EXIF:Orientation = Rotate 270 CW.)3. Do Photo > Flip Horizontal.4. Do Photo > Edit In > Edit In Adobe Photoshop 2020. 5. Observe the photo is upside down in Photoshop.Tested in LR 9.2 / PS 21.1 / Mac OS 10.14.6.

When using a lens with a max. aperture below 1.0 (e.g. 0.95), the exif data seems to be recognized, but it's not usable in the Library Filters, in the text-bar below the histogram and also not in Smart Collections.It seems as if the code simply doesn't support values below 1.0.Please contact me for further details if needed.

LR's use of "|", "<", and ">" as hierarchical keyword separators is not documented.In the User Guide section Add Keywords To Photos, it should say:"Type keywords in the field labeled Click Here To Add Keywords in the Keywords area of the Keywording panel. Separate keywords using commas. Use vertical bar |, <, or > to indicate hierarchical keywords, such as animal|dog, animal > dog or dog < animal."(Text to be added in italics.)In Preferences > File Handling, it currently says:That should be modified to:"The vertical bar |, <, and > are automatically recognized as hierarchy separators."

Camera specific profiles missing once updating from Lightroom Classic 9.1 to 9.2https://community.adobe.com/t5/lightroom-classic/missing-camera-profile-since-9-2-with-z6/m-p/10929699?page=1#M177187

If do you clic on GOOLE word in map modul, Google Map is open in external browser, this is OK, but if do you presse on shift + clic, Google map is opened in the LR windows and no possibility to close that, I do closed the LR windows !!!LR 9.0 on macOS 10.15.3

I'm breaking up my master catalog into individual years so they're smaller and run faster. I created a new catalog (say 2019) then choose "import from another catalog", which I choose my master. It takes a while, then compiles a list of files to import (they are originally all checked boxes). I uncheck all the boxes, then select only files from 2019...this works really well...until I get to a file that has a large number of images (say around 8000 or higher). It refuses to allow a checked box on these large files (even though they were originally checked). Seems to be a bug, I've tried everything to work around this. Any suggestions?

after moving the original files to another directory and want to create HDR or Panorama, these functions do not work! I have to restart Lightroom to use these functions !!

There is an issue (buck with the slideshow exportation:If you sync edits of a big amount of pictures, or read metadata from file, LR does generates a slideshow (video) WITHOUT taking the edits into account, UNLESS being charged before.By charged before, I mean being displayed and thus rendered, OR 1:1 preview generated.This is quite a big bug, imho.

When importing photos and videos to Lightroom from disk (copy, add) from a particular directory, the import of the .mov files would fail with a message indicating that the connection was lost with the dynamicmediaserver.exe process.  Once the dynamicmediaserver.exe process hung, I had to kill the process to get Lightroom import working properly again.  However, every time I tried to import .mov files from the particular directory, it would hang again.  The problem appeared to be a very small .mov file with only a single video frame.  When I removed this file the dymanicmediaserver.exe process would not hang, and the import proceeded normally.

The color filter squares in the filter bar above the bottom thumbnail bar do not have color on a 4k monitor. They show as the background color with a little white dot in each square. Floating over each little square pops up a dialog with the color I'm hovering over, but that is not an efficient UI.The color picking squares in the upper filter bar above the gallery view do show the colors. Can we get color added back to the lower color selection squares?

If you open Lightroom Publishing Manager, the Video Format in Video section is not updated correctly when you switch between publish services.See the video   1. Change the video format setting to H.264 in the Hard Drive publish service.2. Switch to Flickr publish service while saving the previous change.3. The video format setting is originial in case of Flickr.4. Switch back to Hard Drive.Actual result:the video format setting changed to original in Hard Drive publish serviceExpected result:the video format setting stays H.264 as it was set previously

If someone has already reported this I apologize. I did try to search for it but couldn't find anything with the keywords I was using.If I enter a misspelled keyword accidentally it continues to show up in "Autocomplete" even though I delete it from the Keyword List.I've never had this happen before. I recently upgraded to the 9.0 release.My specific example of this behavior is when I go through to keyword basketball photos one of my keywords is Dribble. In the past I could type in dri and hit enter and it would autocomplete Dribble. I accidentally entered dri9 (the 9 is above the right side of the I key) and when I hit RightArrow to move to the next photo it entered dri9 into the keyword list. On the next dribbling photo when I typed dri it showed dri9 as the top option in autocomplete. I went into the keyword list and deleted the dri9 keyword. That removed it from the photo and from the keyword list but it still shows up in autocomplete. I tried to see if I could remove it by enterin

I have issues with LR Classic CC Library crashing (Message: "LR not responding") after adding larger quantities of metadata in the DNG. The above problem started when I decided to add older pre-digital era photos. These photos have no exif or date/time/place embedded since they are negatives or slides. As a result I have to add the above metadata manually. This was with my "old" Win10 PC a HP Z620 with Xeon processor and ample storage on a internal HDD (E:) the catalog was on the same drive. I was advised by Adobe support to move the Catalog to the C: drive and purge the cache. Give the LRcache extra Gb's (15 Gb) and leave the photos (approx: 10000.) on the E:drive. This seemed to be working. After working some time with the data the problems re-appeared. (LR not responding) It looks like LR is locked in some kind of "loop". To get out of this loop I have to end LR forcefully by Ctrl-Alt-Del and stop LR Classic. The result is that a larger part of the metadata is lost and not added to

A bug seems to be introduced with version 9.0 of Lightroom that when a plugin designer sets exports settings using the "updateExportSettings" of the Lightroom SDK all these settings are ignored and default settings are sent for the export job.When the following code is used, the files are NOT renamed on export. The exported file have the same name as the original files.updateExportSettings = function( settings )    settings.LR_collisionHandling = "rename"    -- Rename settings    settings.LR_renamingTokensOn = true    settings.LR_tokenCustomString = ""    settings.LR_tokens = "{ {naming_sequenceNumber_5Digits}}"endI do not know if this is the best place to put this, Adobe seems to have deleted the Lightroom SDK forum.

Changing the color profile in Lightroom and set it to any profile, including (and most visibly on) camera type profiles, will make (especially) the skin tones very/only yellow.This issue occurs only on Sony A6600 RAW files.Please note that the issue is NOT related (or influenced by/triggered by/associated with):- monitors (3 type of monitors, various brands, tested)- PC specs (2 pc, low & high specs)- other cameras (have been tested and the issue does not occur on the following: Canon EOS 1D (2002 model), Sony A6000, A7, A7s, A7iii)- software (Lightroom is at it's latest version, with auto-updates configured and it is an official license, mobthly subscription)- camera settings (regardlless of WB, WB Shift or any other settings, profiles, the issue occurs)- lens/lens attachments (regardless of the lens/lens attachments, the issue occurs)- time/location (the issue occurs regardless of the photo being taken outdoors/indoors, day/night/artifical light)Also, please note that further inv

Hi,Since a few days, LR 9.2.1 tells me upon startup that a new version is available. Of course, this is wrong. Using the Help | Updates menu has no effect. Adobe CC Desktop says : up to date.It's the new joke in town.

Just discovered this as a new problem in LR Classic 8.4, this isn't present in 8.2.In LR if you hover over a preset in the preset browser a preview of the effect is displayed in navigator and main screen. In 8.4 however if image is in portrait orientation and the preset contains either brush or radial actions these will be incorrectly displayed in the preview - they appear squashed. When you actually apply the preset however they apply correctly. Preview:Applied: Preview:Applied:

I've got allot of pictures in my Lightroom Classic catalogue without keywords, when I try and add keywords through the dialogue box Lightroom crashes and I have to sign into my iMac again from the welcome screen, it's happened around 8 times now and it's really frustrating. Does anyone know what could cause this to happen?

Lightroom Classic adds the green border to HEIC files from iPhone. See the original photo and a screenshot. If I edit this image in Photoshop (after applying the Lightroom corrections), I can see and edit the green border there as well.P.S. The files are modified because of this stupid limitations:Sorry! We were unable to upload your image because it was over 2MB in size. Please try uploading a smaller version of the image.Sorry! We were unable to upload your image because it is not a PNG, JPG, or GIF file. Please ensure your image is one of these formats and try again.

Keywords with national characters (Norwegian, ØÆÅ), are not sortedalphabetic.Keywords are all written i Norwegian.I'm running windows 10 Home, Version 1903 and Lightroom Classic 9.2

After I imported raw photos taken with HTC U12+, it shows incorrect temperatures and tint, as it's showed in the following picture:Every raw photo, no matter what temperature I've adjusted before I took it with U12+, showed the temperature at 50,000k, which is not supposed to happen.Also, the Tint shows rather high digits compared to the normal ones.It doesn't happen in other softwares that are able to edit raw files, such as Snapseed, which shows the correct temperature (4900k)Such an issue has been recognized by HTC, and they're working on it, but I was told to report the bugs here as well since it's not clear whose fault it is. Please fix this bug. Thank you.