Bug Reports

I am having a problem with lightroom and I just can't seem to find the answer. I am creating a proof book in the book module. I want the images to appear in order starting at the top left and go left to right, top to bottom. Ideally I would like to use a page layout with 4 to 6 images. I have discovered that depending on which template you use photo cells are "numbered" in a different order. Regardless if your images are in order in your filmstrip, when you choose auto layout, lightroom places them in an inconsistent pattern. For example, if you use a 2 photo layout the photos go left to right. But in 4 photos they go from top left to bottom then back to the top again. With 6 photos it goes top left to top right to top middle and then down to the bottom row (that one really doesn't make sense) you will see from my screen shots my photos are in order in the film strip and their file names are ordered. Is there a way around this? I am sure you are very busy but I really need help on this

Sometimes, I select photos in the "Modified Photos to Re-Publish" pane, and mark them as up-to-date, and they disappear for a moment, then come right back. If I do it again, it will usually take, although some straggling photos may take a third try... Triggers are not the default, namely: default = false, -- suppress default triggers in favor of explicit triggers title = true, caption = true, keywords = true, gps = true, dateCreated = true, And none of those things should have resulted in a re-triggering for re-publish... R

Lightroom's Slideshow module has a problem where the arrow keys always control the selection in the filmstrip. So if one is in a text field the arrow keys can't be used to navigate the field. Even worse, if one hits the "Export Video" button the arrow keys can't be used to navigate the name field. Thanks.

Lightroom V4 web module is extremely slow. I am using TTG CE2 components and compared with LR 3 which was not very swift, LR4 is painfully slow at building and exporting gallery and pages components.

I am running the latest version of light room. While in the import window, I cannot use teh left and right arrows to go between pictures, on the camera, while in loupe view. I have to keep going back to grid, select a pic and then go to loupe. I am convinced that the arrows are in fact moving between pics, because the "select for import" check box changes accordingly, but the pic does not load.

LR 3.4.1 or 3.5RC, Win7 64-Bit: When changing the color label (while a filter only showing images with an already existing color label is active), the change sometimes affects more than one image at a time. Steps to reproduce: Create new catalog, set AutoAdvance off   Import 6 images into the catalog   Go to AllPhotographs view   Select all 6 images using Ctrl-A   Click on label Red in the toolbar   Select Attribute Filter, only showing images labeled Red   Select first image only   Click on label Purple in the toolbar -> Image1 disappears, because Purple was assigned which does not match filter Red -> Selection is set to 2nd image automatically   Repeat for each of the 6 images -> sometimes (often), 2 images disappear because Red is removed from the first image worked on, and Purple is assigned to the next image automatically. This behaviour is sporadic, but often enouth it can be called reproducible.

Lightroom 5.7.1 Repro: - Navigate to Collection A - Navigate to Collection B - Select some photos in Collection B - Create new album with "Include selected photos" (view will switch to new album) - Navigate backwards (Window -> Go Back, or Cmd-Opt-Left on Mac) Expected: - View returns to Collection B Actual: - View returns to Collection A This applies to folders and catalog items in the left bar as well.

I don't know whether this bug is a fault of LR or PS, so I tagged this problem with both products. LR 3.4.1 and PS CS4, Windows XP 32 Bit SP3. Steps to reproduce: 1. Select a RAW in develop module of LR 2. Delete all local corrections and spot removals 3. Draw some adjustment brush strokes 4. *** save metadata (Ctrl-S) *** 5. Delete all brush strokes 6. Open as Smart Object in PS, or alternativley Open in PS, with PS doing the rendering in PS-ACR (the bug does *not* happen when LR is rendering the image!) Result: In PS, the deleted adjustment brush strokes reappear! The same happens a) for a virtual copy made after step 5, and b) even after modifying some other settings, e.g. contrast. And now for the funny thing: Adding a new different brush stroke will cause the image to be rendered *correclty* in a subsequent "open as smart object" or "edit in PS" (i.e. only the new, different brush stroke appears). *Deleting* all brush strokes will again make the old brush strokes reappear! Note: A

On OS X 10.10 (Yosemite), the map in Lightroom's Map module is very slow to load. It takes several minutes before the first part of the map appears, and some parts don't load at all, saying instead "Sorry, we have no imagery here", even though the part in question is on Google Maps. When zooming in or out, it's the same, it takes very long to update.

Hello! I imported a picture and then i horizontally mirrored the pic. When i choose the printmodule an activate my watermark and print it to a file the watermark is also mirrored in the exported file. But in LR the watermark is displayed in the right direction.

If an image or video is missing metadata date/time fields, then LR 3.4.1 uses the file's date-modified for filtering, sorting, and pre-populating the Metadata > Edit Capture Time dialog, but it uses the file's date-created to display in the grid view. It should use date-modified consistently for all of those. (When Windows copies or restores a file, the date-modified is preserved, but date-created is usually set to "now".) This problem trips up people managing scanned images and videos, since scanners typically don't add any metadata and LR doesn't understand much video metadata. See these threads for examples and details: http://forums.adobe.com/message/37343... http://forums.adobe.com/message/38293...

LrDialogs.presentModalDialog - actionVerb works fine, but actionBinding is ignored. for example, if I write: local args = {} args.actionVerb = "Test" args.actionBinding = 'test' accItems[#accItems + 1] = vf:push_button { title = str:fmt( "Doesntmatter" ), action = function( button ) LrDialogs.stopModalWithResult( button, 'whocares' ) end } end args.contents = vf:column( mainItems ) - main-items not relevant. args.accessoryView = vf:row( accItems ) args.save_frame = 'testPrompt' local answer = LrDialogs.presentModalDialog( args ) then click the 'Test' button, the value returned in answer will be 'ok' - I expect it to be 'test'. Is it broken? or am I using it incorrectly???

All user develop profiles were deleted when upgrading. I also notice that the LR presets are no longer in the folder. Settings are for presets to be stored with Catalog

On one of my catalogs, folder:getChildren() is returning 0 return values for a particular folder (that is, it is executing a "return;" statement, with no value): I've optimized the catalog to no effect. If I hide the root folder "/", then the method works correctly. This may be related to these topics (or it may not): http://feedback.photoshop.com/photosh... http://feedback.photoshop.com/photosh...

On one of my catalogs, folder:getChildren() is returning 0 return values for a particular folder (that is, it is executing a "return;" statement, with no value): I've optimized the catalog to no effect. If I hide the root folder "/", then the method works correctly. This may be related to these topics (or it may not): http://feedback.photoshop.com/photosh... http://feedback.photoshop.com/photosh...

I never know what to re-publish anymore. Most recently: I rebuilt standard previews then restarted Lightroom, now there are 9444 photos "modified" to republish (there were zero shortly before building standard previews). There are other times I go to publish new photos or honestly modified ones to find anywhere from 1 to thousands of photos in the modified to re-publish section, which hadn't been so modified. Also, marking them up-to-date is still problematic (takes multiple tries) - like in the beta. reminder: that was supposedly fixed in Lr5.2RC - it's not. Rob

Whenever I crop or straighten images in LR 5.5 my crop tool seems to jump into another "suggested" cropping. Then it jumps back to my cropping. This is very annoying and takes a lot of times when editing 1000+ images in a row ... I hope there is help. I have seen this problem in a lot of other forums aswell but there is not solution yet. I guess it's a bug that needs to be solved. Working on Mac OS X 10.9.3 (Server HD)

I have a new MacPro and upgraded to Lightroom 5 and CC Photoshop. I am having a lot of problems importing from CF cards via a Hoodman USB 3.0 card reader. I have tried different card readers and different ports. I have some movies on the CF cards (SandDisk 32GB Extreme). In the past, with LR 4 and my old Mac, I had no problem importing movies or images. Now, when I put a card in and pull up the Import dialogue, it takes forever for the previews to load and sometimes it just loads some of them and the rest are blank. I can import a few sometimes, or all sometimes, but LR ends up crashing or hanging if there are any movie files at all on my CF card. The same thing happens if I upload from my internal hard drive. In addition, if I load a previous LR catalog, it hangs and crashes everytime I open it and click on a folder with .mov in it. Through other forums, it was recommended that I try a card that has no .mov files on it and that seemed to work fine. Is there any solution to importing i

I'm having an issue with the crop tool in Lightroom 5.6. When I go to apply a crop, the picture will quickly zoom in, and then zoom back out on me for no reason. Happens consistently. It's very annoying, so if you could fix it, that would be fantastic. I'm running Mac OS 10.9.5 on a 2012 2.3 ghz i7 MacBook Pro w/ 16gb of ram.

Presently, there are many plugins that may access the catalog briefly to update it in background threads. If any other plugin tries to access it for writing at the same time there will be an error in the plugin making the denied attempt. I have solved this problem for myself, and published the solution in the SDK forum and at https://www.assembla.com/spaces/lrdev... (in a nutshell: parse error message to determine if error was in operation function or catalog accessibility, and if the latter, hold-off for a random time period between .1 and 1 second then try again, until succeed or give up...) however I'm sure not all plugin author's are accounting for this possibility, which may make them appear flaky (depending on the complement of other plugins installed), and the root of the problem being in a different plugin, makes it hard for the author of the seemingly flaky plugin to reproduce & fix... Perhaps an optional "wait-time" parameter to the with-do writing gates, and associated d

I’m creating my first Blurb book inside of Lightroom 4. There are some 175 images in my collection/filmstrip. I was about 80% complete with the book, when I selected an image to go into the Development Module for adjustments. When done I returned to the Book Module. But the book was gone! The filmstrip at the bottom of the page is there indicating images are in the book, but the book itself is empty with only a cover and two blank pages. If I add an already “used” image, the filmstrip counter goes from 1 to 2. Trying to fix this problem, I backed up and optimized my catalog. But upon restarting Lightroom no change... and no book! Any suggestions as how to get my book back? Or do I have to start over!

LR 3.5RC, Win7 64-Bit: If a preset name contains some (for windows filenames) invalid characters (i.e. "/", "< Test" "Test ? Test" Beat

In Smart Collections, the rule "Capture Date is in the last n hours" doesn't work. It appears to behave as "Capture Date is today". Here's a screenshot: Image is not available LR 3.4, Windows 7

LR4.3: "Remove Chromatic Aberrations" is turned off after disabling and reenabling the lens corrections panel for more images (auto sync on), even if it was on before and on by default. I consider this to be a bug. It isn't a big problem because it can be turned on manually but it can easily be forgotten.

Lightroom SDK: LrTasks.yield is extremely slow on Windows. (its over 100 times slower on Windows than Mac - something is really amiss...) I sure hope this gets fixed soon - any plugins calling it repeatedly in a loop run like molasses in winter (on Windows).