Bug Reports

In Lightroom, the Export command won't let me choose an export directory, even when I choose "Specific Folder" in the "Export To:" field. My choices is limited to my desktop. I cannot even choose an other hard drive.

I rename my photos in Lightroom 3 at the time of import with Camera Make + Filename. This works great to distinguish the photos between my Nikon D3s and Nikon D3x. Unfortunately, video taken with the D3s does not have the Camera Make field in the .AVI file and when you import the pictures, Lightroom "hangs up" looking for the Camera Make. A popup window that allowed you to create your own name or a way to fill in the information manually would be helpful. At least, it should import the avi file and notify you that it could not rename the file properly. Thanks

Normally, the before/after display does not include differences in crop/straighten, i.e. the "before" version always shows the *current* crop/straighten settings (not mentioned in the manual btw). However, when you go directly from the before/after display (completely zoomed out - "fit") to the crop/straighten tool, change the crop, leave the crop/straighten tool and then directly go back to the same (!) before/after display, the "before" version shows the *old* crop/straighten settings. Screenshot: Image is not available Some actions, such es selecting a different before/after view or zooming, will refresh the display so that "before" ist shown correctly in the current crop/straighten settings again. Windows XP 32 bit SP3. P.S. This is definitely only a minor bug. P.S. II. Why does LR beep when using the keyboard shortcut Alt+Y for before/after-top/bottom? Is is because normally Alt-* is used to access the application's menu, but there is no main menu with shortcut 'Y', so is this a

When I import a foto applying a *user* develop preset, the foto is wrongly imported with process version 2003. The develop preset does *not* contain the process version (verified by applying the preset to an already imported foto in process version 2010, which does not change), and LR has been reset to the Adobe standard default settings for the camera type before, so I think it is not a user error. This only happens for user presets, and not for Lightroom's build-in presets. If I recall correctly, a similar problem was fixed a while ago for the build-in presets, but now it seems to occur for user presents? The strange thing about it: It seems nobody has reported this problem before (at least I did not found it), so perhaps it is a problem local to my machine? Perhaps some components from older LR versions were not correctly de-installed? How can I check that? Edit: Additional information: The user preset was freshly created in LR 3.4.1, so it cannot be a backwards-compatibility issue

Bug: When a photo is cropped, the RGB values shown in the before/after mode are wrong for the before version (first numbers of the three RR/GG/BB pairs). The RGB values shown for the before version is not from where the mouse cursor hovers over the photo, but from somewhere else, depending on the cropping used. Steps to reproduce: 1. Create a simple black and white image in square format, the upper half black and the lower half white and import it into LR. 2. Go to crop mode (R) and crop away the upper quarter of the photo. 3. Leave crop mode and enter before/after left/right mode 4. Be sure that the current crop shows on the before version (see possibly related bug http://feedback.photoshop.com/photosh...) 5. Move mouse cursor slowly from bottom to top of the before or after version(which one does not matter) 6. You will see that the RGB values of the before version (first number in the three pairs) drops to zero (black) *before* you actually reach the black area in the upper half. In

I have Adobe Lightroom 3.4.1 and I just imported two separate catalogs into one new one. I had a smart collection that would sort out shots that were landscape aspect ratio and it is now empty, as Lightroom thinks that EVERY shot is now portrait aspect ratio. If I change ANY crop settings in the Develop Module, then Lightroom instantly and correctly identifies photos that are in landscape vs. portrait aspect ratio. Is there a way to fix this WITHOUT me having to touch each photo's crop settings to fix it??? THANKS... Lee Hawkins Cleveland, OH

Something I've not encountered before (using LR 3.4.1). Processed one image and changed it from landscape to a square crop. Selected other images, one at a time, and used 'Previous' to apply all of the Develop Settings. Could have used Sync, but I needed to adjust the crop window slightly for each image. I found that I could move the image (or crop window) around on the secondary images, and that I could resize it using the top/bottom or side handles, but as soon as I attempted to move any of the corner handles it automatically altered to the original (landscape) orientation even though the crop icon was locked. When I went back and selected the 1x1 crop, it set it to the full frame size (vertical, anyway). Mike.

Filtering a smart collection by "Capture Date" and Months sometimes doesn't work. I have a smart collection filtering by "captured in the last 5 months but not in the last 4 months" and I get almost all of the pictures in my catalogue in the collection. I'm using LR3.4.1

I think I have localized one of the problems I am having with cataloging my photos with Lightroom: even if you click "automatically write changes into xmp", Lightroom will quit without warning you that changes were not written. For instance, I took a keyword that had about 1,000 images associated with it and renamed it, then I quit. The sidecar associated with some of the files did not have a recent modification date, indicating that changes were not saved to the file. Restarting Lightroom and hitting save for these photos did save the changes (with a progress bar indicating that the save was taking a while). I have been going through my own private nightmare where I changed the name of some folders high up in the directory of keywords (names of folders of folders of keywords), and then imported all my photos into a new catalog. What I found is that the photos have come in with the old and new hierarchies, which has been a mess to figure out. I assume that this is because Lightroom did

Lightroom 3.4.1: On Win7 systems both the 'Edit Keyword Tag' and 'Rename' context menu items (when right-clicking on a keyword in the Keyword List) both produce the same result, specifically the Edit Keyword Tag dialog box. The 'rename in place' capability of LR2 seems to have been lost. A minor issue, as the Edit Keyword Tag also allows renaming, but mentioned for complete accuracy.

Another language error in Swedish version of Lightroom: In the develop module, adjustment brush you can choose effect. In the drop down list to the right in the screen shoot the text is "Jämna till skal". I suppose you mean "Soften skin", but "skal" in Swedish means skin on a potato for example. Skin in english also means the skin of a human, but in Swedish that kind of skin is "hud". My suggestion is to change this till "Jämna ut hud" eller "Hudutjämning" meaning to soften the skin of a human.Note: This conversation was created from a reply on: Lightroom: Swedish - Translation Issue: "Jämna till skal" should be Jämna ut hud"....

Lightroom 3.4.1 - Swedish Translation Issue---> In the Swedish language mode I suggest a change in translation in the following place: Arkiv/Exportera med förinställning/Efterbelys fullstora JPEG-bilder (File/Export with Preset/Burn as full-size JPEG:s). I suggest you change the word "Efterbelys" to "Bränn" in this case since it does ́t make any sense today. "Efterbelys" means "Burn" as in Dodge and Burn in Photoshop. In English you use the same word for this and Burn as in burn a DVD or burn the house down. In this case, in Lightroom, I suggest you change the Swedish word "Efterbelys" to "Bränn", which would give us the Swedish sentence "Bränn fullstora JPEG-bilder". However in Photoshop, when the meaning of burn goes along with dodge, the Swedish word should be "Efterbelys", which I suppose is the case today (I have an English version of Photoshop so I don ́t know the translation there)

To begin with, I am not sure whether this is RC-specific or a general 3.x problem, so I post it as a separate problem and not in the "3.5 RC bugs" thread. 1. Open adjustment brush. 2. Draw some strokes, set "A" brush to size 20 and "erase" brush to size 2 3. Reset adjustment brush (or alternatively, click on "new" to deselect current pin and create new brush stroke) 4. Position cursor over image 5. Hold down ALT key, note that brush shape does NOT change to (-) because there is no active pin 6. Draw something while still holding down the ALT key.... 7. The brush shape immediately changes to the erase brush (-) 8. Observe what is drawn: ... the initial "blob" is drawn correctly using the "A" settings (size 20) ... the continuing brush stroke is drawn using the "erase" settings (size 2) 9. After releasing the mouse button, the brush operates correctly again. WinXP 32 Bit. Edit: Here is an example how it looks after drawing the brush stroke as described: For this example, I set flow to 90

I'm using the new Lightroom 3.5. When I add a Mask and want to change the Exposure, if I click Shift and the arrow key, it moves the slider all the way to either -4.00 or +4.00, not in .10 increments as expected. I use a Macbook Pro with Lion. Thanks.

Considering scanned images, with existing, but different, values for DateTimeOriginal and DateTimeDigitized... A. In LR version 3.3 (& possible prior versions): XMP:CreateDate appears to have been mapped to an existing value for DateTimeOriginal. I believe it should have been mapped to the existing DateTimeDigitized, as noted by the MWG. This issue may be one cause for the incorrect digitized dates noted by users of 3.4 & 3.5RC. B. In LR version 3.5RC: Recommend retaining the XMP:DateTimeDigitized tag. Currently, this tag is deleted by 3.5RC (and perhaps 3.4), which prevents corrective action due to the problem noted above for LR3.3 (i.e. autosave metadata or ctrl-s deletes the date digitized information from original file). Per the MWG, 3.5RC is using the CreateDate as the digitized date, but that value is no longer correct as created by LR3.3. Due to the possible loss of the DateTimeDigitized data by 3.5RC, I'll need to revert back to LR3.3. Though the CreateDate appears to b

Hi, I've noted an inconsitent behavoir of LR when it is started in "non-standard" conditions. This is not critical, but upsetting as I get finally exactly the opposite of what I was expecting. (I've always encoutered this bug (since 2.6) on both vista & W7) All my pictures and catalogs are on external disk: for each "picture library" the files, the catalog & the technical data (preview, cache) are in a unique Windows directory on an eSata external drive with this approach: - I can make full backup very easily - I've a very safe confidentiality of the pictures (when the drive is off...) - I can use my professional laptop for "personnal use" And by the way the perf are very good with a 2Terabyte 7200RPM external disk (25 000 pictures of 19 & 50 MP). The issue is that with this approach, I start from time to time LR without a library on-line and: - LR asks me if I want start with the default lib or exit. - I choose "exit" - LR exits - I connect my disk - I relaunch LR - and LR

In Lightroom 3.6, the import option "Don't import suspected duplicates" does not work with old files (year 2000). Here you find test-data: http://www.thavis.com/downloads/2012-... http://www.thavis.com/downloads/2012-... http://www.thavis.com/downloads/2012-... Regards Peter

Here is way to reproduce it: I'm experiencing it on Adobe Lightroom 4 on Lion OSX Go to the Develop module. Select a picture and create a virtual copy of it. Select the virtual copy you just created. Play a bit, for example, with the tone curve many times so you create 5 or 6 elements of history. Click (for example) in the middle of your History to select a particular ''action'' as for example "Point Curve: Custom" Now right click and from the menu' choose the action Create snapshot... Enter a name for the snapshot RESULT: No snapshot has been created at all FURTHER TESTS: Click now on the + sign in the pane and name a snapshot RESULT: The snapshot is created. Thanks & Regards, Marco

Using LR4 64bit- have been able to reproduce crash multiple times. Happens when using the adjustment brush. Click on the adjustment brush then click on one of the numbers for any of the adjustments- without clicking anything else (i.e. off highlighting the adjustment #) re-size brush using mouse wheel- crashes every time.

1. I search for a place, say "London" 2. I then zoom, pan, scroll the map to the exact location I want. 3. I click on a photo in the filmstrip so I can geotag it The map then re-centres itself on my search field, losing my location I just found. To get around this, I have to remember to clear the search field first - it would be great if I didn't have to do this 🙂

Unable to Update DNG Previews & Metadata to more than 100 DNG files at a time in LR4..

After Updating LR4 from LR3.6, the Spot Removal Tool freezes (shows hand) after each movement for 5 to 60 seconds. This happens only when I'm using the Wacom Intuous 4 tablet. The Tool work fine when used with the USB-Mouse! I'm working with Win 7/64 with a Dual Core E6850, GT440, 4Gb, Wacom Intuos 4, LR 4, PS 5, DW 5.5... All drivers are up to date, PC is running without any problems. Any ideas what to do? Or just wait for the next LR4 update... Greetings from Frankfurt/Germany

When exporting a book for Blurb, I see an offset with an image overlapping the two page sides. First I noticed this on Blurb's book review page. Then I tried to do an "Export Book to PDF..." and I can see the same offset. Please have a look at the offending page at http://leu.org/issue_blurb.png This is with the official Lr4 release on a Mac OS X 10.7.3. Thanks for your help! – Daniel

In previous versions of Lightroom, selecting one of the tools in the Development Module, such as the Adjustment Brush, automatically displayed the settings panel directly below the tools, in what appears to be a dropdown. Selecting a tool in LR4, on Windows 7, no longer makes the panel automatically visible, no matter where you are scrolled in the Develop panel; you have to scroll back up to the top of the panel in order to see the settings. Not critical, but certainly annoying behavior. I looked for other reports of this but found nothing, so I apologize if this has already been addressed.

Bug appears when several photos are printed to files (not to the printer). LR is generating file names suffixed with ",jpg" (comma) and not ".jpg" (dot). Most probably somebody is using a library for Brazilian Portuguese where the decimal point is a comma in the wrong place