Bug Reports

Sometimes (seems to be random) after unlocking and locking the crop perspective in one picture and then moving on to the next image, the crop perspective is unlocked again when cropping the next image (despite having relocked the perspective in the previous image). Is there anyway to keep the crop perspective lock the same when moving to another image?

New bug in V10 of Lightroom Classic. Setting a star rating on a photo in Grid view is not carried into Compare view.   Mac Catalina 10.15.7 Lightroom Classic 10.0

Just update the last version of lightroom classic 10 and i have an error message "Agnegativestyle manager_new exception thrown: Agerrorid>dngfil_error_file_not_found The picture dies'nt show except on top leftplus, when i want to export to the new update of photoshop 2021, it open photoshop, and immediatly close just after i can do anything..Si I can not use both of them...     I've already try to desinstall and re install both and nothing change...   Im on windows 10, last update 1909 nvidia last update driver too  There is my pc set up config, not old at all and good enough.   there is my spec via lightroom:   Version Lightroom Classic: 10.0 [ 202010011851-ef6045e0 ]Licence: Creative CloudParamètre de langue: frSystème d'exploitation : Windows 10Version : 10.0.18363Architecture de l'application : x64Architecture du système : x64Nombre de processeurs logiques: 8Vitesse du processeur : 4,2 GhzVersion SQLite: 3.30.1Mémoire intégrée : 32725,1 MoMémoire réelle dis

My current setup is a MacBook Pro 15 Mid 2012 with Catalina 10.15.2 and LR Classic 9.1. The LR catalog is on the local disk (SSD). The images itself are on a Synology NAS connected via SMB. When I try to import photos from my iPhone 6s Plus, LR lets me select the pictures and correctly detects duplicates in the catalog (which are then grayed out). When I start the actual import though, LR just hangs forever. Cancelling the import works and then I get the message that there was either a read or write error.Strangely the following works reliably:- Importing from the same iPhone to a local folder (so it cannot be an iPhone problem)- Importing from a local folder to the shared folder on the NAS (so it cannot be a NAS problem)What is NOT working is the combination of importing from an iPhone directly to a NAS folder. 

I am running Lightroom Classic 10.0 on a MacBook Pro (macOS Catalina version 10.15.7) and Lightroom keeps crashing when importing or exporting images. I’ve made sure I am running the latest software and updates, I’ve tried restarting my computer multiple times, I’ve reset my LR preferences and the catalog I’m using was optimized today. This issue started happening when I was still running LR 9.4 and then I updated to 10.0 and nothing changed. What can I do? I’ve never had this happen before today.

When sort order is set to date order, it then changes to custom order each and every time an image is edited in Photoshop

Hello, I believe this is a bug..When using edit in Photoshop from Lightroom with TIFF format set, none of the compression settings work. Because when the file is saved in Photoshop (ctrl+s) and comes back to Lightroom it's always an uncompressed TIFF. Every other setting works.Unfortunately I can't tell whether the fault is on Lightroom or Photoshop side..Tested on Win 7 - 64bit with LR 3.6 - 64bit and PS CS5.1 - 64bit, also on Win XP - 32bit LR 3.5, PS CS5. (In both cases camera raw version match) Lightroom 4 behaves the same.I would appreciate your replies, Thank you

They used to be sorted alphabetically. In version 7.3 the order is random

When launching Lightroom 6.7 on Windows 7, it can take a little while to initiate and do it's thing (even loading from a fast SSD). Normally that'd be fine as I just bring other programs to the foreground and continue with other tasks while it loads in the background. However, I count 3 times where Lightroom steals priority from whatever other program I have just to show me the next step in its loading process. Please make it stop or only do it at the very final step?

When enlarging and exporting a file with a transparent background as a PNG file from Lightroom this happens  

Hi Guys, I have a problem with the RAW file of an in-camera double exposure that has changed colour dramatically and I'd appreciate any advice. Image 1. - this is the base image for the double exposure. This is image 2 of the double exposure: This is image 3: - the in-camera merged double exposure.  The image below is SOOC and exported directly from Lightroom last week and these are the colours I would like to keep.  This image is a low res jpg and is all I have left of the original colours as the RAW version in Lr has changed to nuclear Yellow. This is the RAW file showing now as funky, nuclear yellow.  Despite resetting all the settings and even reimporting the files I am stuck with the yellow and can't  get the original colouring back.  I can get it to revert to green by using Auto WB in Lr but it's not the same as the original. There has been a long discussion in The Adobe Support Community and the thread for that can be read here: https://community.ado

Many Nikon DSLR's have an overlay function which combines (overlays) two NEF images to produce a third NEF image in-camera. The source images don't have to be different, so an image can be combined with itself, which is what I did for this example.I have noticed that for such combined images, the WB for As Shot has Temp: 2880 and Tint: -119, regardless of the WB camera setting of the original images. In this example, I shot an image with my D750's WB set to Daylight. Importing the original image into Lr Classic 8.0 gives the As Shot WB as Temp: 5300 Tint: +7, which is always the value for this WB setting. See the screen-shot below:If I change the WB from As Shot to Daylight, the values change slightly to Temp: 5500 Tint: +10, as shown:Combining this image with itself using 0.5 for the contribution of both source images to make a new overlayed NEF and importing into Lr, in develop I see this:White balance for the image looks fine, but the settings aren't right for the WB camera setting.

If two selected photos have different entries in a particular field, LrC displays <mixed> in that field. In version 9.4 (and earlier), after synchronizing metadata, LrC would update the display of the field with previously different data and display the field showing the now identical data. In LrC 10.0.0, the field is not updated to display the data. It still shows <mixed>. After deselecting the selected images and then reselecting the images, the field correctly displays the updated (identical) contents.   Steps to reproduce problem: In the Library, select two images for which a given metadata field (e.g., Title) are DIFFERENT. In the Metadata panel, the field will display <mixed> Click the Sync Metadata button at the bottom of the right side panel.  Be sure that the field in question (e.g., Title) has its checkbox checked in the Synchronize Metadata dialog box that appears. After clicking the Synchronize button, the field (e.g., Title) will still sho

I have noticed the Splash Screen being displayed two or three times during startup of Lr Classic 8.3 along with (not responding). My OS is Windows 10. The problem seems to be easier to replicate when launching Lr in the Library showing the grid view. In Preferences, the "Show splash screen during startup" option needs to be enabled. Here are my steps to reproduce the problem: Launch Lr Classic 8.3 and when the splash screen goes off, click on the interface - I've been clicking on a blank area of the menu bar. The splash screen briefly shows again and Lr shows (not responding) while the splash screen is visible. After a few more seconds, the splash screen is displayed for the third time and Lr shows (not responding) again. Waiting for a further short while, the splash screen goes off again and Lr resumes initialising itself.

After upgrade to LR CC2015.8, short cut X to reject an image in Library module is out of order.Shif+X is OK ?

In the Library module, I select a group of photos and use "compare" mode. Up until I upgraded to 9.4, I could use the arrow keys on the keyboard to move between the pictures in the group. That's broken now. It's not my keyboard (keys work fine). The graphical arrows on the Lightroom interface still work with the mouse.

[Here's a test plugin to run in LR 9.4 and 10.0, showing the bug in 10.0. -JRE https://feedback.photoshop.com/conversations/lightroom-classic/bug-lightroom-classic-10-applying-preset-in-plugin-all-panels-turned-off/5f9439bcbd2550489fc11865?commentId=5f960b4649d3ca123123eeff]   When retrieving an existing preset with for example Exposure 0.5, along with this setting all the panels are turned off.   Example preset:    xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/"   crs:PresetType="Normal"   crs:Cluster=""   crs:UUID="41AE3A89A1C9A8429C7CE3F3B1A21FCD"   crs:SupportsAmount="False"   crs:SupportsColor="True"   crs:SupportsMonochrome="True"   crs:SupportsHighDynamicRange="True"   crs:SupportsNormalDynamicRange="True"   crs:SupportsSceneReferred="True"   crs:SupportsOutputReferred="True"   crs:CameraModelRestriction=""   crs:Copyright="" 

I'm using LR Classic 8.2.1 with LR CC Mobile for Android 4.2.2 to upload smart previews to Cloud storage and then download them to LR Mobile for Android on my Samsung Note Pro tablet. I've also installed LR Mobile Desktop to get my custom camera profiles uploaded, but no editing in LR Mobile Desktop has been performed. I can review pictures in my LR Classic synced albums in LR CC Mobile for Android, LR CC Web and LR CC Desktop. However, if I try to review the pictures on my Samsung tablet with WiFi disconnected I get a message on some image files 'Failed to load Development version.' So it appears only some of the LR Classic synced smart previews are being downloaded onto the Samsung internal storage. I'm certain this was working properly at one time, but not any longer. I've uninstalled LR Mobile on my Samsung tablet including deleting all application data and cache and reinstalling with no change in behavior. I've also created a new synced collection in LR Classic and it exhibits the

Summary If you have a large catalog and use Filter folders, then next time you use Import (or Synchronize or Drag&Drop, ...) it will take a lot more time than usual or essentially freeze Lightroom. Catalogs with 10.000s of photos -> LR freezing for seconds or tens of seconds. Catalogs with 100.000s of photos -> LR freezing for minutes or hours. Windows 10, Intel i7 6700K. No plugins were active, not even the standard ones like Flickr or Adobe Stock. I have made a lot of tests and this is what happens: Step by step reproduction 1) Open LR 2) Just for comparison: Import 10 or more files files - this takes seconds 3) Remove those files from the catalog 4) Use Filter folders in the left panel: Write "aaa" there, Enter, then clear the text by clicking on the cross. Filter folders should therefore be no longer be active 5) Import those same files again - if you have large catalog, this now takes much more with LR possibly freezing after about 6-8 photos imported. How much time it t

I using Jesse Friedl's jfFlickr and jfZenfolio publishing plugin (latest release) with Lightroom 5.5 I've been using the jfFlickr one for years, all my photos there were published and up to date I started using jfZenfolio, published some pictures. I then notices that the photos I published in jfZenfolio now show up as "Modified Photos to Re-Publish" under jfFlickr In fact you can see them showing up under jfFlickr as "Modified" one at a time as they get published to Zenfolio

Calling  applyDevelopPreset on a preset created within the plugin causes all "Corrections" (Local adjustment Brushes, Radial Filters and Graduated Filters) to be removed from the image in LRC 9.3. All other image settings remain unchanged as expected. Is there a way to prevent this from happening? This is how the preset is administered on a photo in the plugin. local preset = LrApplication.addDevelopPresetForPlugin(_PLUGIN, editText, edits)photo:applyDevelopPreset(preset, _PLUGIN) This is the generated preset. s = { id = "35819D5A-5461-4BDA-802C-0A2AF7D3E4AC", internalName = "Exposure +0.3 1.8", title = "Exposure +0.3 1.8", type = "Develop", value = { Exposure2012 = 1.8, }, version = 0,} Applying this preset changes the intended value of exposure, but also removes any Corrections (Local Adjustment brushes, Radial and Graduated Filters) on an image. All other settings remain unaffected. Currently, as a workaround I'm having to do this to keep

Auto-Stack By Capture Time is extremely slow in my LR 9.3 but is nearly instantaneous in LR 8.2.1. Details:  In LR 9.3 / Mac OS 10.15.5, I selected 1185 photos and did Photo > Stacking > Auto-Stack By Capture Time. I got the spinning beach ball for over two minutes and LR was unresponsive before the dialog finally showed how many photos would be stacked: In LR 8.2.1, I selected mostly the same photos (1170), and Auto-Stack instantaneously showed me how many photos would be stacked, with no spinning beach ball. Something broke since LR 8.2.1. Auto-Stack should be just a simple sort and linear scan of the capture times of the selected photos, so the behavior in LR 9.3 is clearly a bug. See here for the original report by another user on Windows: https://community.adobe.com/t5/lightroom-classic/auto-stack-by-capture-time-causes-lightroom-classic-to-become-unresponsive/td-p/11348704?page=1

When you delete a folder or collection from the catalog, LR doesn't remove references to the folder or collection from the favorites of the film strip's source menu.  It's impossible to delete the dangling references to collections from the favorites. To reproduce: 1. Make a new catalog and import one photo into it. 2. Make a collection containing the photo. 3. Select the folder containing the photo, click the film strip's source menu in the top left of the strip, and do Add To Favorites.  Select the collection and do Add To Favorites. 4. Delete the collection and remove the folder from the catalog. 5. The source menu still shows the folder as a favorite. The menu now shows "Collection: Collection" as a favorite, rather than the original name of the collection. 6. Restart LR. 7. The favorite for the folder is now gone, but "Collection: Collection" still appears, and there is no way to get rid of it.  Tested on: LR 9.4 / Mac OS 10.15.5 and Windows 10. Updated to correct t

Hi, first time poster here but long time users.  Major issue with my work flow today.  I normally use the x/y compare view in lightroom to do close compares of my images and to remove the ones I don't want.  Up until now this has worked well by just right clicking on the image in the compare view I want to remove and selecting the remove option.  However, on using this today I became aware that it was removing the opposite image.  I have been through a long support call, including resetting all my preferences only to find that the support analyst had the same issue on his machine.  He refused to escalate the issue and told me to post it here and ask for it on the wish list.  However, as this is something that was working and is now broken and I imagine is part of others work flow I think this should be looked at urgently. Fortunately I spotted this in time to restore the incorrectly removed images from backup, but others might not be so lucky. 

I had an issue with lots of repeated files and in order to fix it I wrote my own script to calculate a hash on all files and then check which are the same. This worked very well and with it I found that I have the same exact file imported into different folders... In my setup all the files enter those folders through an import on Lightroom. When I digged further I found out that: 1) the files have the same MD5 hash 2) they are exactly the same 3) they have the same EXIF data and it matches reality (CREATED DATE) 4) They have a different date on the filesystem 5) The file was imported to the date the file has on the filesystem I am very surprised with this. When we move files around the file date changes but it seems that Lightroom is importing based on that and not on the METADATA inside the file. This is happening for .JPG  Is this normal behaviour? I have the latest release of LR Classic 9.2