Bug Reports

Lightroom 2015.4 now supports tethering for the Nikon D5500. My Nikon D5500 is not recognised when trying to tether !!! I received an email from Nikon today announcing a firmware update for my D5500, which i did. I’m not sure if the firmware update is preventing the camera from connecting.

I generated smart preview for a entire collection and I can see the "smart preview" and "original picture" below the histogram for all pictures. However it happened several times that when I remove the external disk on which raw files are stored, the smart preview disappear for the picture currently in development. I can check now that I have 16 pictures with smart previews missing, these are exactly the picture I modified in the development module. Is this a known bug ?

LR 6.4 Windows 7 64bit 24Gb mem no internet connection. All cloud usage disabled, all syncing etc turned off in LR and Creative cloud. Creative cloud itself is suppressed as too intrusive, too many sub tasks I have no use for. LR set with blank grid view and totally idle. Monitoring Task Manager LR is creating a Thread every 8 seconds with 100k mem working set used up. These threads persist. Left running over lunch had reached 530 threads and mem usage up by over 100Mb. If connect to internet thread count stabilises but existing threads do not die. Appears a background thread is created to access the internet which does not abort on failing to connect. Totally unacceptable behaviour, when idle LR should be doing nothing whatsoever and certainly should not be constantly accessing the internet. Certainly expect to be able to use LR with no internet connection.

After updating to Lightroom CC 2015.5.1 (win7, german) I can no longer use the keyboard shortcut shift+d to deselect the current photo. Using the menu still works. Any ideas? Please fix if this is a general bug.

1. Set some Transform slider, e.g. X offset +102. Turn off Transforms using the off button on the section header3. Draw something using adjustment brushExpected:Photo is no longer transformed, the brush should draw under cursorWhat actually happens:Photo is no longer transformed, but the reverse transform is still applied to draw events, so it is impossible to make any painting on the photo.

LrApplicationView.showView('reference') triggers an error that lists the accepted views--while the other develop-specific views are listed, reference is not.

In LR 2015.7 the "X" key is assigned to two functions in the library module: Reject photo (Foto/Ange flagga/Avvisad) Show info (Visa/Format för stödrastervisning/Visa information) Now, this is a total screw-up since the X (=Reject) function is SUPERIMPORTANT to every workflow. Unfortunately, when you press X the other function has priority. Luckily, Shift-X still works to reject a photo and jump to next.My guess is that this is only in the Swedish version (any maybe some other obscure languages) or you'd have a huge mob right outside 345 Park Avenue in San Jose.Come on Adobe! Just have an intern check the keyboard shortcuts before you release! Or even better, give us shortcut customization. Arrrgh... 😞

The context menu for a filmstrip thumbnail in Develop sometimes shows Metadata > Save Metadata To File rather than Save Metadata To Files when multiple photos are selected.To reproduce:1. In Develop, select multiple photos in the filmstrip.2. Right-click one of the selected photos and roll the mouse over Metadata.  Observe that Save Metadata To Files is shown.3. While the context menu is still showing, move the mouse over another selected photo.4. Right-click that photo and roll the mouse over Metadata. Observe that Save Metadata To File is shown, not Files. 5. Hit escape to close the context menu.6. Right-click the same photo as in step 4, and observe that Save Metadata To Files is now shown.See this screen recording: https://dl.dropboxusercontent.com/u/21811200/filmstrip-save-metadata-bug.2017.03.03.movSee this thread for the original report: https://forums.adobe.com/thread/2285258CC 2015.8, OS X 10.12.3

Lightroom Alpha Channel Rendering Issue With PNG File Format

hithere is a bug lightroom 6.8cc & 6.9cc in the slideshow moduleit doesn't keep the slideshow ,quality settingsi tried to create a preset with all settings and set it as defaultin short i start lightroom 6.8 and i have tried with 6.9 , change the slideshow quality to draft or highwhen i close lightroom v6.8cc and 6.9cc ,and I restard lightroom the preferences are restored to standardi tried to ask to the forum but nobody answered https://forums.adobe.com/thread/2288964 windows 10 pro 64bit , lightroom cc last update 2015.9 or 6.9cc (but the issue was present in 6.8 too)can somebody confirm it ? or is my system the problem?thanksbest regards

You can't use the smart collection Recently Modified to find photos whose rating, flag, caption, or title was changed in LR Mobile / Web.Specifically, when you change the rating, flag, caption, or title of a photo in LR Mobile / Web, the edit date in the desktop catalog doesn't change, and the smart collection Recently Modified (Edit Date is in the last 2 days) won't contain the modified photo.  But if you change the rating, flag, caption, or title in LR Desktop, or if you change develop settings in LR Mobile / Web, the edit date in the catalog does get updated, and the smart collection Recently Modified will contain the photo.To reproduce:1. In LR Desktop, sync a photo that hasn't been changed in several days with LR Web.2. Use the showdates script to examine the photo's edit date.3. In LR Web, change the rating of the photo and wait until it syncs to the desktop.4. In LR Desktop, notice that the photo hasn't appeared in the Recently Modified smart collection.  Note that "sh

I am experiencing a problem with the Map Module becoming non-functional. This issue is new with version 6.8.Reproduction steps are:1. Switch to Map module. Notice that everything works as usual - Selecting photos with GPS jumps to that location on the map. Dragging photos onto the map sets GPS coords. Right-clicking on map shows "Add GPS coordinates to Selected Photos" option.2. Click the Google logo in the bottom-left of the map. This used to open the current Google Maps view in the default browser. Now it opens the view in its own window.3. Notice that the map module no longer works as usual. Selecting photos does not cause the map to jump to their location. Dragging photos onto the map has no effect. There is no right-click menu. Changing to a different module and back does not help. Lightroom must be closed and re-opened to restore functionality.I wonder if anyone else is experiencing the same issue.As a side note, I much preferred it when Google Maps opened in the default browser,

This has happened a few times in a past, then went away in subsequent releases, now in last two Lightroom CC releases happened again.Basically I am sorting out my photos by capture time (older to more recent) - that works fine by itself. I also do a lot of file selection and panoramic stitching in Lightroom directly, which ends up creating panoramic raw files alongside the raw files. The created panorama raw files take the capture time from the last photo used and, when added to Lightroom, used to go after the last photo used for panoramic stitching. Not anymore - since last two Lightroom CC updates they annoyingly get inserted before the last photo in panoramic sequence which is quite annoying really especially when you order file groups by panoramic sequences. This makes it quite difficult to deal when processing the shoots with quite a few panoramic sequences.I am guessing it has something to do with secondary ordering when the timestamps of the capture are the same - that secondary

After the last update, when I click on the image to zoom in, it sometimes zooms out a little, then partially zooms in, finally zooming fully. It is slow, intermittent, and infuriating.What have Adobe done with this, as it was fine before?

I now get a warning about  zipping backup catalog files larger than 4GB Even though the catalog file is only 1.6GB.   I'm running MacOS 10.12.1

Hello,Since the upgrade to Lightroom CC 2015.8, I get an error with the backup of the catalog in Win10. Lightroom asks me to select another folder or even another drive. I’ve tried both, without success.When will a correction come out?I am unable to make backups of my catalogs.

The Delete key will sometimes delete a face region from a previously viewed photo, that is not currently selectedWhile working through recently added photos, if you tag a face on a photo, then move on to the next photo, and try to delete that photo, Lightroom will instead appear to do nothing but actually delete the face tag that you added to the previously viewed photo.Specifically, the steps to reproduce this are:View a single photo in the Library (Loupe view)Add a face region to the current photoGo to the next photo which does not have any face regions (Ctrl+Right)Attempt to delete that photo by pressing the Delete keyNothing appears to happen - the Confirm message doesn't appear and the photo isn't deletedHowever, if you go back to the previous photo with Ctrl+Left, you'll see that the face region that you just added has been deleted.  Lightroom shouldn't do that to a photo that is not visible or selected.(I'm using Lightroom CC 2015.7 on Windows 10)

I have just installed the 2015 CC edition of Light Room but am having problems publishing and exporting photographs. When either exporting to hard disk or publishing to FlickR, I'm getting 5 or 6 random, all white images.

I recently wrote a new plug-in for Lightroom and in doing so initially created a password_field that is taller than one line (height_in_lines = 3 in my case).On a Mac, that password_field behaves just as it should: the content is obscured by round dots, and it cannot be copied into the clipboard.On a Windows, though, to my horror a password_field with height_in_lines > 1 turns the field into a regular multi-line edit_field: the content is visible in plain sight, and it can be copied into the clipboard. This is a serious security flaw.Granted, most password_field boxes are only one line high so perhaps this is an innocent oops, but I was certainly surprised to discover the difference between Mac and Windows.Another minor nit is that the password_field on Mac can have a placeholder_string, but on Windows that placeholder_string is obscured as hashes. Duh!

When I see EXIF data for HDR images that Lightroom created, it's based on the darkest exposure of the source images. I think the middle exposure (or next-to-middle if an even number of bracketed shots) is a more appropriate reflection of the shutter speed/exposure time.

In the German help screen that pops up if you open the "reference view" ("Referenzansicht" in German) for the very first time, there are \n\n characters which presumably should mean that there should be a line feed, see screen shot below.

I am running OSX El Capitan and 50% of the time Print to File fails to export the file. Have to try a second attempt which is always successfull. I don't get any error message (also export progress bar is ok), it just does not save the file in the chosen location. I can also predict when it fails and when not, the "Save as" window in the Finder is slightly different. Am I the only one with this issue?

tethered shooting performance (download) is painfully slow, despite using usb 3.0 and fast computer with tons of memory, Capture One Pro is 5X faster. When is Adobe going to fix this issue? More and more portrait/headshot photographers such as me are shooting tethered and we shouldn't have to move to Capture One Pro in order to get decent performance. Nikon D800E, fast Windows computer (i7) with 24GB memory, Windows 10, USB 3.0

In the book module one can enter different fillings (whited border) for each side of the foto cell (left, right, up, down). However, when I later enter that cell again, Lightroom checks all the small boxes to connect each of the fillings. When I then uncheck any of the boxes, Lightroom resets all fillings to one of the values. Very annoying, please fix this.

Since updating to LR 2015.7 and Macs OS X Sierra, the badge numbers in the grid view are no longer visible no matter what view I choose (expanded, compact, etc.). For good measure I recalibrated my display and that doesn't make a difference. This is not a problem for 2015.7 using other machines running El Capitan and Yosemite.