Bug Reports

LR 6: Cannot enter negative values e.g. for lighting in Development (e.g., -1,0); sets always to zero. Works if I just move the slider; positive values ("+1", "1") work also. (MacOS 10.10.3)

With the final release of LR 4.1, using the + and - keys within the Develop module to adjust exposure no longer work. They appear to work, in that the app throws the expected dialog ("increase exposure +.10" or similar) and this action is recorded in the history panel, but the exposure slider on the right does nothing, and the expected result (up or down exposure) on the image never happens. With the + and - keys, you can send the exposure up or down 4 stops, per the history and the onscreen pop-up, but the adjustment actually never happens. Only when you use the mouse and drag the exposure slider up or down, does exposure actually adjust. This is a tremendous workflow hit when you have thousands of images you want to make minor exposure adjustments to, and have to keep reverting to the mouse. Everything worked fine (in this regard) in 4.1RC, and every version prior. 2010 Mac Pro 24G memory Lion 10.7.4

I've found a solution to a problem many others seem to have reported - but it does involve a work-around, suggesting the Adobe Photoshop Lightroom team need to fix a bug. When a large number of Develop Presets are loaded into Lightroom (in my case, over 500), the Library Module, and strangely, to a lesser degree, the Develop Module run very slow. Having performed some troubleshooting, I discovered the reason for the slowness was a CPU spike. On my iMac 3.4GHz with 32Gb RAM, NVIDIA GeForce GTX 680MX with 2GB, and 1TB Fusion Drive, the CPU would go over 100%, while the disk and memory allocations were low. I run Mavericks 10.9.2, so it's not a matter of an out of date OS. This occurred whether I had 10 images or 10,000 images in the catalog (I tested various scenarios). I read on a forum that the number of Develop Presets could affect performance, so deleted the majority of them (backing them up first) to see if it would make a difference. I reduced the number of presets to less than abo

Using the new 2012 process in Lightroom 4, the auto tone adjustment function does not work properly. Most images come out strongly over or underexposed.

LR 4.4, OS X 10.8.4 After the infamous facebook Tuesday night update the Facebook publish plugin no longer works. LR will not display a fb album list, cannot create albums or publish new photos to existing albums. Editing Collection settings will no longer authorise and returns error "Can't save changes: Authorizing" Sometimes states error "Cannot retrieve facebook album list", plugin also fails and needs reloading, diagnostics file contains : Plug-in error log for plug-in at: /Other App Links/Imaging/Adobe Apps/Adobe Photoshop Lightroom 4.app/Contents/PlugIns/Facebook.lrplugin **** Error 1 An error occurred while attempting to load this plug-in’s portion of the Export dialog. ?:0: attempt to index upvalue '?' (a nil value) I have reloaded an earlier backup of the plugin to make sure it was not corrupted. Several users have posted about this error on the Adobe community forum http://forums.adobe.com/community/lig... Removing authorisation and plugin from fb does and reauthorising does

Just installed Lightroom 5 final. Output Sharpening and Noise Reduction does not work. Whole story here: http://forums.adobe.com/thread/1229132

Full Screen Preview (F) works incorrectly with selections when invoked from Grid view (G), though it does work correctly when invoked from Loupe view (E). Full Screen Preview should work just like Loupe view (and it does, when invoked from Loupe view). To reproduce: 1. Go to Grid view. Let’s call three consecutive pics A, B, and C. 2. Select A and B, with A most selected. 3. Go to Full Screen Preview; the most selected (A) is displayed. 4. Click right-arrow. Pic C is displayed, even though it wasn’t selected. 5. Go back to Grid view and notice the original selection has been lost; just C is selected. With Loupe view, right- and left-arrow cycle among the selected photos, and the original selection is not changed (only the most selected). Full Screen Preview should work the same way. And if in the recipe above, after selecting A and B, if you first enter Loupe view and then Full Screen Preview, left- and right-arrow work correctly, cycling among the selected pics A and B. See here for a

Hi, during the last days I created about 50 HDR/dng files (Canon 5D3, 3 images merged) using the new LR CC HDR Merge function. Now, after the merge, when I edit the dng file (22 MPixel, 85 MB) LR slows down extremely. The main performance issue is not changing the sliders but waiting until the image is rerendered! After a development change it takes often 10-20 (!) seconds until the image is rendered. In library module, mostly I have to wait 20 to 40 seconds until a preview is rendered. Often I wait forever and the preview is NOT rendered. Then I have to restart LR and then again have to wait 20-40 seconds until the image is rendered. During rendering about 50% of a i7-3770 CPU (i.e. 2 cores are fully loaded!) are used. Sometimes the CPU load goes up to 100% (i.e. 4 cores are used!) during rendering the image. Below is an example of the load while rendering a preview for more than 2 minutes. The worst case is using the compare mode in library module. When comparing 2 HDR/dng files, I h

Works ok if played from slideshow module, but not impromptu.. win7/64 More info here: http://forums.adobe.com/message/6037135 I'm sure this problem was introduced long before Lr5.4, but Lr5.4 is the first revision with a slideshow feature worth using (due to color/tone bug - thanks to Adobe for fixing) so... Is there any way to manually advance a slide without a trip to the slideshow module?

LR 5.0 on a Mac (tried both Mac Mini, MacBook Pro and MacBook Air - all running 10.8.4). When I run a slideshow and pause it, the arrows keys to go backward/forward are not working. Created a "testuser" account (so no LR prefs that have been inherited) and copied over a test catalog. Same issue. Also installed it on work laptop where I've never used LR. So no old "cruft" on account or inherited. Same issue. I use the slideshow module to pick/rate/flag and therefore have paused and gone back and forth while the slideshow was paused (e.g. to change rating on previous photo), then resume. Bug? Workaround available?

Still broken in Lightroom 5.4 on Mac/Mavericks. When running a slideshow, the left/right arrow keys do not work to go back and forth in the slideshow. Though I am glad to see you finally fixed the color profile problem on slideshows.

i have the option to automatically save XMP data into the images activated. so all keywords and metadata changes are not only saved to the catalog but also into my DNG and TIFF images. now this works fine for everything except the new face recognition data. i mean the areas (rectangles) where the faces are. i guess the problem is that the images already contain the keywords (names) of the persons in the images. what i did was using the rectangles to identify the persons in the images. drawing rectangles around their faces and name them. this info about the rectangle positions is NOT automatically stored in the image files. not after hours of letting LR run idle. this info is only stored when i manually save (CTRL+S) the images or do something other to the metadata (like adding NEW keywords to it). so in short: just adding the face region data (the rectangles) will not trigger the automatic XMP save function when the name keyword was already asigned as keyword to the image. that ́s very

Hello, some problems with NR not applied if image size < 1/3 of original were apparently solved in 5.2, but in some cases NR is still not applied. Please have a look at attached images, they are both exported with exactly same settings, the only difference is, that there is a crop applied on cropped.jpg version. Please notice the difference in overall noise. Please solve this problem as soon as possible, this has a big impact on image quality if higher ISO is used. Please contact me, if original NEF or XMP is needed. I can reproduce the problem. It seems, that it appears only if some specific crops are used. Thank you. cropped.jpg: not_cropped.jpg:

A smart collection uisng the criteria Collection and Publish Collection doesn't always update its results properly in LR 4.4 and LR 5 Beta (Windows 7 64-bit). Here's how to reproduce: 1. Create a Flickr publish collection named "test 1" with 1 photo. Create a collection named "test 2" with 2 different photos. 2. Define a smart collection named "Collection test" defined as "Match all", "Publish Collection contains test". Observe that it properly selects the 1 photo in the Flick publish collection "test 1". 3. Edit the smart collection to instead use the criterion "Collection contains test". Observe that it continues to select just the 1 photo in the publish collection "test 1", not the 2 photos in the collection "test 2". Here's a screen shot:

'Contains Words' has a data sensitive bug that causes it to behave seemingly flaky. Details are findable on the forum if the forum search ever gets fixed. I remember it by the keyword: "Big Mallard Ducks". Try searching for a photo with this keyword using 'Contains Words' and the various contained words and you'll see the problem - somebody already identified detailed cause - see somewhere on the Photoshop Lightroom forum. I never use keywords with spaces anymore, so this bug means nothing to me personally. This one falls in the category of "should be fixed next rev" in my opinion - it has persisted for a long time now.

LR 5.2 breaks Red Eye corrections that were applied in LR 4 in Process Version 2012. In LR 4, a Darken value of +100 darkens the adjustment, but in LR 5.2, it lightens it. As a result, photos with red-eye applied in LR 4 can look significantly different in LR 5.2. This bug was corrected in ACR 8.1, but the fix did not get into LR 5.2? http://blogs.adobe.com/lightroomjourn... It would be great if the LR team could quickly acknowledge that this is a bug that will be fixed in the future, so we can plan temporary workarounds accordingly. The image below shows how LR 4 interprets Darken = -100 (left eye) and +100 (right eye): And this one shows how LR 5 interprets the same values:

On the left is Camera Standard. On the right is Adobe Standard. See the hard edges and the weird colors in the gradient of the Camera Standard version? What’s up with that? I get that using any of the camera-specific profiles for my Nikon Df.

Lightroom 5 bug in reordering images manually - Mac OS Only. Symptoms: In grid view if you drag a photo to change position and try to swap with the image on immediate left the image you're dragging moves to the last place. Step to reproduce: 1-Open lightroom 2-select a folder 3-click on one image 4-drag over the immediate left image 5-release click 6-the image moves to the end of the grid versions affected: 5.0 -> 5.7 OS: Mac OS X only (10.9.x - possibly other versions too) screen recording: https://dl.dropboxusercontent.com/u/2...

I encountered a bug in the Lightroom 5.2 spot removal tool. When the tool is active (after hitting Q), perform a left-click with the mouse and hold it. Then move a little so it starts painting a white surface. Still keep the mouse button pressed and hit the Delete key to remove the spot being created. Instead of deleting only this spot, ALL spots disappear. After this toggling spot removal mode does not work anymore. Restart of Lightroom is required. I use Windows 8 Pro.

When more than one photo is selected, and more than one copy name is passed, I mean, in Windows anyway, maybe Mac too. First off, I realize the SDK v5 has not been released, so if this bug report is premature, just ignore it. That said, I wanted to report ASAP in the hopes that it will be fixed before SDK 5 is released, if applicable. Problem is, plugin has no official way of assuring Lr is in grid mode. So createVirtualCopies needs to be fixed, or we need a way to force grid view, or both. Again, my apologies in advance: I acknowledge this is an undocumented function. Rob

I am using Lightroom 5.2 (tested with MAC OSX 10.8.5; 10.9 and WIN 7/64) All images are stored on an external drive an all smart previews are built. If the external drive is unmounted and I try to email photos I get the error: Can't send email because some selected photos are missing. Exporting the photos to my local hard drive is working so the photos are not really missing.

Found a bug in Lightroom 5.5 for Windows: "Can't move folders into their own subfolders"I have a folder named, "2010". I created another folder in the same level as "2010-2019". Attempting to move "2010" into the new "2010-2019" folder results in the below error. Rename to "a2010-2019", then moving 2010 into the new "a2010-2019" folder works. After that, I renamed "a2010-2019" back to "2010-2019" Error: "Can't move folders into their own subfolders"

LR 3 / W7 - conflict - Ctrl+Alt+A = Polish letter ą. When I try to type polish name in edit field with letter ą, the beginning of this name is deleted, because of in LR clr+alt+a is a shortcut to "select flagged photos" command.

At a Lightroom workshop at the weekend we were running through the book module and noticed that only those with Lightroom 4 could type in the spines on their dust cover. All font sizes etc were checked and correct.

The Problem: A client uses a MacBook Pro, an Epson 77c projector, and Lightroom to show slideshows using the slideshow module of Lightroom. In Lightroom 5.0, the reds and oranges of the slides when shown on the projector are over-saturated - but *only* when using the Slideshow module. This is a new problem since upgrading to Lightroom 5.0. Additional details: * I have created a calibrated display profile for the projector (using a Spyder 4 Elite) and made sure that the Mac is set to use the proper calibration for the projector in the Displays pane of System Preferences. * Even if I select a different (incorrect) calibration for the projector, such as the generic sRGB one provided by Mac OS X, the problem persists (although of course the colors in the photos look worse in general, too). * As I said, this is a new problem with Lightroom 5. With the exact same setup and photos in Lightroom 4, I do not see the problem. * The oversaturation only happens with the slideshow module displayed o