Bug Reports

Win10 / Lr Classic CC 8.0When using Synchronize Folder, Lr doesn't recognize HEIC files that need to be imported.If the only "new" file(s) are HEIC, Lr shows there are no files that need to be imported and therefore, no import is done.If the "new" files are a mix of recognized formats (jpg, cr2, etc.) and HEIC, Lr only counts the older recognized formats, but it does import all the files.To reproduce -  - In Lr, create a new folder. - In Windows Explorer, copy an HEIC file into the folder. - In Lr, right-click the folder and click Synchronize Folder.  The Synchronize dialog box shows 0 new photos to import, so you can't move on in the import process. - In Windows Explorer, copy a jpg file into the folder. - In Lr, right-click the folder and click Synchronize Folder.  The Synchronize dialog box shows 1 new photo to import, but Lr will import both the files.

LR CC Classic Version 8: When you use menu "Picture" - "Develop settings" - "Update to current process version" in library view on a photo, which has already the current process 5, it gives an unexpected error (maybee the menu's are labeled a bit different - i have the german verison installed), see picture below:The error does not occur, if the process is older.

So far I have only found this to affect Clarity and/or Dehaze alone. To reproduce:Start with an image that has no develop adjustments and is process version 4.Change Clarity or Dehaze, or both. The adjustment badge [+/-] shows on the film strip thumbnail.Update the image to process version 5 (Settings->Update to Current Process)The adjustment badge [+/-] disappears.In the Library module, if you filter Edits, the adjusted image doesn't show as I would expect if Lr doesn't consider it has any edits.If you change the process version to 5 in the Calibration panel, the problem doesn't occur.

Hello Adobe, could you please point out, that while using the new tether feature in Lightroom, it is essential, to follow the tether dialog box till the bottom. There you can choose "save copy to camera“. On a reason shoot i was tethering medium size jpg's because i want the process to be very fast. I was shooting like that many times before, so i overlooked the very tiny checkbox on the bottom of the page. The result was, that Lightroom forced the camera not only to "not" save the medium jpg's to my SD card, but also not save the raws to my CF card. At home i wanted to import the raw files to my computer, but there was nothing one on the cards. I've seen reports on the web, that other people have the same fatal loss of raw date because of that little checkbox, wich is new to Lightroom. Please try to make public, that your users have to take care of this. It would be sad, if more photographers loos more raw files, clients and money. Thank you.

There are a few other discussions where this issue is being reported but i believe they have other issues clouding the discussion   Since the update to .3 and subsequently 3.1 Lightroom Classic CC hangs after being idle for a time (i can;t be specific on time as it seem to change). It does not happen necessarily on sleeping from the computer or in one module or another or when changing windows or minimizing or maximizing   It hangs and i am forced to "end task" through Task Manager   I am on a completely up to date (drivers and software and Windows) Win 10 Pro 64 system with 128gb RAM and plenty of horsepower and disk space (NVME and SSD)   My system has no problems with any other programs   please fix this

[Note from John R Ellis: This was reported fixed in 2015.8, but there have been numerous reports of the symptoms coming back since then: See later posts in this topic.]It may sounds confusing, but when I select one collection or a published folder and go back to Folders and pick up one folder, Lightroom does not deselect that collection or published folder and I can not go back to that collection until I select another collection.A folder in Folders section is deselected when a collection or published folder is selected.I'm using LR CC 2015.1.1

After I create a new keyword set, alt+0 and alt+shift+0 do not toggle among my keyword sets.  If I close lightroom and come back in it works properly.I am running Lightroom Classic CC 7.5 on Windows 10.

I sometimes apply a filter combination of Flagged/Unflagged (so excluding rejected pics) and a red color label, using a custom color label set. When this filter was active on quitting Lightroom, the grid view stays empty when I start up Lightroom and only after doing some action (switching to a different folder and going back, changing the filter and undo the change) the photos show up like they should. If I also filter on the white color label (which isn't included in the custom color label set) the photos show up immediately on opening Lightroom.Library filter options: Lock Filters and Remember Each Source's Filter Separately are active. Lightroom version 7.3.1 on macOS High Sierra 10.13.4.

Lightroom 7.3 and osx 10.13.4First, I would like to note that this is not the same as RAW and non-RAW specific presets.  In this case the preset does work with both RAW and JPG files, just not consistently.   A preset in certain scenarios will work ALL the time with a RAW but only works SOME of the time with a JPGCreate a preset using the following methodSelect photo and do a RESET so no settings are appliedCreate a Preset called ZeroSaturation   (I think this can be any slider)Save the preset with ONLY Saturation selected DO THE FOLLOWING WITH BOTH  RAW AND JPG FILESSelect photoDo a RESETApply a Saturation that is not ZeroApply the ZeroSaturation Preset.   (The Preset works with BOTH JPG and RAW)Apply DehazeApply ClaritySelect DehazeApply the ZeroSaturation preset. (The Preset did NOT work the JPG)History on RAWAs you can see the preset works all the time on the RAW.  When you execute the preset on the Dehaze step the history is cleared above De

In LR 7.5, the array returned by LrLrApplication.developPresetFolders() includes buggy fake folder objects intended to represent separator rows in the user interface.  Invoking folder:getPath() on one of these bogus objects raises the internal error: ?:0: attempt to index field '_pathForFolder' (a nil value) This affects any plugin that attempts to access the develop preset folders. In particular, it broke a DxO plugin and my own Fix Presets plugin (which fixes many other preset bugs):https://forums.adobe.com/thread/2528220https://feedback.dxo.com/t/export-to-dxo-broken-after-update-to-lr-7-5/4514https://forums.adobe.com/thread/2527232http://www.johnrellis.com/lightroom/fixpresets.htmThe workaround is to detect such bogus objects by calling folder:getPath() and trapping any error with pcall().Details:Here are the results of calling folder:getName() on the array of preset folders:Note that the bogusly named folders correspond to the presence of separate rows in Develop's Prese

I have a very strange problem: I was on vacation in another timezone and I forgot to change the time on my DSLR. I imported part of the photos directly on my iPad LR app. Another part of the photos I imported into LR CC on my Mac after I got home.Since the capture time was off by 1h due to the wrong time on my DSLR, I corrected the capture time of all photos via LR CC on my mac.Here it is where it becomes strange: The time stamp on all photos is now correct in LR CC Mac but on the iPad or iPhone and also on the LR Webclient is still off by 1h for some of the photos. I first thought it to be a sync error that the changes did not get synced. But then I tried changing the time of 1 photo again to see if it would update. And it did update it just kept the 1h offsett (on my Mac the changed time was e.g. 16:15 and on my iPad it would show as 15:15).What I noticed was that this 1h offsett happens only and for all photos that have been imported via the iPad. On all photos t

Within the last several weeks, I have started to get errors when trying to sync from LR Classic.  Some problem images have been successfully synced for months, and others are new.  The problems seemed to begin when I removed some photos from All Photos in LR CC.  In the upper left corner, I see "Syncing 3 photos", though the number changes.  In Preferences, Sync Activity, the images have had the message "bad argument #1 to '?' (number expected, got nil)", and the Remove from All Synced Photos option doesn't seem to do anything.Is there some way I can reset the sync environment?  Would that be a solution? Thanks.

The Web module in CC 2015.7 / OS X 10.11.5 doesn't use the display's profile when showing photos. You can easily verify this:1. Install this display profile on your system. The profile swaps red for blue, green for red, and blue for green.2. In the Library module, view a photo and notice the colors have been garishly swapped, indicating that Library is using the display profile.3. In the Web module, use the default HTML gallery to view the same photo, and notice that the colors have not been swapped, indicating that the display profile is not being used.4. In the Web module, click Preview In Browser. If your browser is color-managed, the colors of the photo will be swapped. (You may have to completely restart your browser before doing this.)With a regular display profile, this bug can cause colors in the Web module to be more saturated.  See the original report from Bob Somrak here: https://forums.adobe.com/thread/2216419The problem doesn't occur with LR 5.7.1, and Bob t

my new Lightroom Classic does not work classic while exporting:In the export process (of course with the option "Add to this catalog") the exported files do not appear until the "work bar" has already disappeared long ago. So very, very slowly and sometimes not completely.If I redo the export process (with the identical settings) and the confirmed request to overwrite existing data, LR creates duplicates in the export folder. This is obviously a database error, because in the folder the exported data exist physically only once ...Have I described this complicated enough? :-))And yes, I have tried it with my existing (for LR Classic updated) catalog, as well as with a freshly produced new catalog. Always the same mistake.Thanks for any Help, Kai

Yesterday I "upgraded" to the Lightroom Classic CC version. I began trying to import some photos into my library and each and every time it crashes after a little while and doesn't actually import them.I thought I would start a new catalog, to see if there was something incompatible or wrong with my previous library, however that too crashes. I can import about 2-3,000 photos and then each and every time I go to import a new folder of images -- bam.  I've tried importing small batches, also crashes. Extremely disappointed!

Lightroom 7.x broke the ability to show placeholder_string in text input fields created by LrView.osFactory():edit_field and password_field.This is visible e.g. in Hard drive publish service description fields, first Lightroom Classic CC 7.3.1 and then Lightroom 5.7.1 (sadly I couldnt run 6.14 concurrently with latest release, all I got was error 1 on startup) LR 7.3.1:LR 5.7.1As you can see, the placeholder string "Untitled export" is not visible in Classic CC, and so are not any other placeholder_strings.  I think this used to work fine in 6.x, and I've used for example login/password fields in my plugins.  Now the users are pretty confused because all they see is empty text field.Tested on Lightroom 7.3.1, macOS 10.13.4.  Sorry, didn't try it on Windows.

Hi,This one, I can reproduce at will. Using a dual monitor configuration under Windows.1. Launch LR. Go to the Library module. Main screen in Loupe mode, secondary display in Grid mode.2. Select a smart collection.3. Select an image.4. Exit LR.5. Relaunch6. The main display shows again the lastly selected image. The secondary display says "No photos in selected smart collection".7. Now if you select another smart collection and go back to the previously selected one, all the images of the smart collection are shown on the secondary display.Sigh! Yet another bug introduced with version 7.3.

I am running LR 3.4.1 on OS X 10.6.8. The Library>Enable Filters command does not work properly when I have a Library Filter set up to filter on more than on criterion. For example, I have a Library Filter preset called "Needs Location Keywords" that selects all images for which don't have "Location" as one of their keywords and which are not flagged as Rejected. In other words, there are two filter criteria applied: 1) TEXT: Keywords "Don't Contain" "Location" 2) ATTRIBUTE: Flag = Flagged OR Flag = Unflagged Toggling the Filter State by choosing Library>Enable Filters works as desired when the Filter State is changed to OFF; all images in the selected folder are displayed. However, when Library>Enable Filters is selected a second time, changing the Filter State back to ON, only one of the original filter criteria is applied, namely: 1) TEXT: Keywords "Don't Contain" "Location" However, ATTRIBUTE Filtering is NOT re-enabled as one would expect. This is repeatable with differen

There appears to be a bug in Lightroom Classic CC 7.3 with regards to camera default settings: they're only partially applied on Import.For example, in my default settings, I apply a camera profile (Camera Neutral) - this works.I also use a fixed, custom white balance - this doesn't work. Lightroom always uses the "As Shot" white balance from the camera instead on import."Remove Chromatic Aberration" is on in my default settings (why does that default to off, anyway?), but it's off after importing.Only when I use "Reset" on a newly imported photo, ALL of my custom default settings are applied.I reverted to version 7.2, and my default settings are applied right on import, as expected.I'm using Windows 7 64bit.Thanks for looking into itAlexander.

[Update: The GPS Data Metadata browser column disappears when returning from Map to Library when there are more than four columns in the browser.  See this recipe from Louis Sherwin for reproducing the bug: https://feedback.photoshop.com/photoshop_family/topics/bug_report_filtering_for_metadata_gps_informa... Last tested in CC 2015.12 / OS X 10.12.6.  -- John R. Ellis]Hej,I think I found a bug in LR 5.2 which can be reproduced as follows (my LR is german, so the english translations might be a little off of the actual labels):- go to library (Bibliothek) module- under library filter (Bibliotheksfilter) select meta data (Metadatan)- go all the way to the right and select add column (Spalte hinzufügen)- click none (ohne) and select GPS data (GPS-Daten)- go to map module- got back to library module- the newly created column is gone now.If you can or can't reproduce this or know a workaround, please let me know.Thanks, Tobi

Step 1: In order to apply my standard changes by Camera and ISO to imported raw files I first set up one image carefully in the develop module and then hit Option+Update to Current Settings. (screen print)   Step2:   I then perform an import from that Camera and ISO however none of the changes that I established in step 1 are applied.  (this used to work in LR 6). Nothing happens to the imported raw files, no edits are applied.  I shut down LR, restart it and then I see the edits.  I reported this on another post but just discovered restarting LR allowed me to view the edits - none were applied on the initial import.  No idea why. Screen Print 

When clicking on Preview or Play I get the message "An internal error has occurred: ?:0: attempto index a nil value". Had no problems prior t0 latest update. Windows 10 Pro with latest updates 32GB ram

When you apply Auto Tone to a large batch of photos, LR does not consistently update all the photos, and subsequent batch changes to the photos’ develop settings can get lost.  This happens when using any of the mechanisms for batch changes: Photo > Develop Settings > Paste Settings, Auto Sync, Quick Develop > Saved Preset, or via the SDK.This problem has existed for many years (see all the reports merged below), at least since LR 5, and probably at least since LR 4.Apparently, when you apply Auto Tone to a batch of photos, internally LR just sets a flag on each photo, deferring the actual computation of the Auto Tone until later. It won’t actually compute the Auto Tone develop settings until the photo’s thumbnail becomes visible in Library or you edit the photo.  But any other develop settings you’ve applied to the photo in the meantime will get silently overwritten by the deferred Auto Tone.To reproduce the problem: 1. In Develop, define a develop preset “Test

After installing the Feb 2018 update yesterday, portrait movies imported from my iPhone (6S) are strangely rotated 90o to landscape orientation. Previously, no problem with such files.As part of my weekly collation of images from my phone, I export originals from Apple Photos, then import them into Lightroom. The specific files I am now having problems with, but didn't have before, are portrait movie files that are part of "live photos". The associated jpegs from live photos are all rotated correctly, and landscape "live photos" have no problem.I tested and this extends to all portrait movies, not just the .mov parts of "live photos". The problematic imported .mov files look fine in Quicktime and Finder.

Say I'm in Lightroom and I want to open 5 or 6 shots into PS CC, and while they're opening I want to jump over to Chrome and check my email. Is PS supposed to keep jumping to the front every time another file opens? It's pretty frustrating and I don't remember it happening in previous versions of PS.