Bug Reports

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

LR 4.1 RC refuses to create 16 bit tiff files for Edit In function. I tried both Preferences - External Editing and set bit depth to 16 in the additional external editor section. When I reopen Preferences it has reverted to 8 bit. If I select 16 bit from the "Edit Photo with" dialog after selecting Edit In, it still creates an 8 bit tiff file for the external editor. The external editor I am using is Topaz Labs.

Note: Not to be confused with http://feedback.photoshop.com/photosh...! Steps to reproduce: 1. Enter adjustment brush 2. Draw a brush stroke 3. Click on "A", set size, feather and flow of brush "A" all to 10, automask off 4. Click on "B", set size, feather and flow of brush "B" all to 20, automask on 5. Click on "Erase", set size, feather and flow of brush "A" all to 30, automask off 6. While in Erase mode, press the shortcut key for A/B-change (english: "/") twice. Expected results - one of: a) Nothing happens. There is no A/B in erase mode b) Brush changes from erase mode to A, B, ... etc. Actual result: Erase mode persists, but size, feather, flow and automask change to that of brush A, and on second key press to that of B, etc. The original settings for the erase brush are lost. If the settings are changed again, they are again lost when pressing the shortcut key (the original settings for A and B are not changed by that). Tested in LR 3.6 and 4.1 RC 64 Bit, Windows 7, with german

One of the 4 photos page templates for Blurb 10x8 (standard landscape) is misaligned. The top left photo is a little off in the template called "page_44". The fix is easy: open "Adobe Photoshop Lightroom 4\Templates\Layout Templates\10x8-blurb\basics10x8\templatePages.lua" and search for "page_44". The photo with photoIndex=3 has a width that is wrong and should be changed to 284, like the width set for the other photos in this template. (This is also the file you can modify to add your own templates, to design pages that are otherwise impossible to create!)

When painting with a self created brush preset it always changes the title of the brush from whatever you have called it to Custom after you have made the first stroke, even though no sliders have been moved to change or alter the brush.This in its self doesn't alter the ability of the brush to do what it is being asked but can leave you wondering if you have been painting with the brush you first selected or whether it has changed.This doesn't seem to happen with the presets that come with LR. A friend has confirmed that his self created presets are doing the same.

Lightroom 4.1 64 bits Windows - French When editing the altitude (Elévation) in the GPS section of the Library (Bilbiothèque) panel, a message box appears saying "L'altitude doit être indiquée en mètres ou en pieds, ou rester vide". This modal message box is in a infinite loop (clicking OK relaunches the same message box) and this requires killing the Lightroom process using task manager.

Using Lightroom 4.1 on Mac.I usually tag pictures, which show people with the names of the people.For this I manually set up a hierarchy like "People/John Doe". Now I select a picture, press cmd+k to enter the "add keyword" mode. Now I enter the person's name. In this case John. While entering it the autocompletion shows the matching name, i.e. John Doe. I press enter.Lightroom now applies to _separate_ tags called "John" and "Doe" on top level. It should have applied what it suggested, i.e. a single tag "John Doe" which is defined in the hierarchy under People.This bug makes tagging quite difficult because I have to use the mouse for every single picture.

When I geotag photos in Map module the program fills the name of the place: Country, Province, City and sometimes even Sublocation. So far so good.However, when I switch to Library module the location fields in Metadata's IPTC are still blank. Or sometimes they even have data from a different photo!It only happens when only IPTC option is chosen in Metadata panel. If I choose "EXIF and IPTC" the problem is gone.I think this is a bug.I use LR 4.1 on Mac.

I created a track on my cell phone for several photo sessions in California. Upon returning to North Carolina I loaded the photos and tracks into LR, but when trying to Autotag received the message "No Matching Photos." I tried to set a time offset, but when I selected the menu item nothing happened. I did notice that when I tried to autotag the photos LR started an "operation" (in the upper left corner) but nothing ever happened - that notification stayed up there - never completing - until I closed the program. Upon examination I noticed that the tracklog had a time offset already built in. When I removed this the tracklog worked as expected in LR. I can supply the logs if you need them

This sure feels like a bug: Steps: Create a stack Select it Choose Split Stack Result: All photos bar top are removed from catalog. Huh?...Help says: Note: The Split Stack command is not available if you only select the top photo in a stack. That's the behaviour I would expect. Is this a known bug?

LR 4.2 final 64 Bit on Win7. Steps to reproduce: 1. Select a folder containing about a dozen photos, all *not* part of a stack 2. Group photos so that three or four stacks are created and all photos are in a stack 3. Expand all stacks 4. Select all photos 5. Group into stack (now a single stack containing all photos of folder is there) 6. UNDO Expected result at step 6: Stacking goes back to the previous three or four stacks Actual result: Apparently only one of the stacks is restored, and all other photos are now contained in "single-photo-stack" displaying the "photo is part of the stack" badge with the number zero [!] in it. Expaning/collapsing those "stacks" seems to hide/show the previously existing stacks, but they are definitely gone. The "unstack" command is not available to "break up" the "single-photo-stacks". A restart of LR does not help. However, there seems to be a workaround: When selecting the "single-photo-stacks" together with a "normal stack", the "unstack" command w

LR 4.2 64bit Win7 SP1 64bit During catalog backup any mouse wheel movement brings this dialog [Window Title] Confirm [Main Instruction] Lightroom was unable to back up the catalog named “LR catalog”. [Content] Please check your folder permissions, and make sure that you have available space on your backup drive and main catalog's drive. [Try Again] [Choose Different Backup Folder...] [Exit]

On regular basis I get a crash in Lightroom when load a GPS track in the map module. This usually happen when I load more than one per session. When this happens restarting Lightroom and loading the GPS track again works. The GPS track in in .gpx, generated by HoudahGPS This problem exists since the initial beta of Lightroom 4. Still happen in the 4.3RC. This is on Mac. I have systematically sent the crash report to Adobe (check with my email address if you have access to them) The only reason I report it here is because I was told the crash reporting is not useful.

Cannot delete missing photos in LR4.3 Please try this: 1. Find missing photographs 2. Select All 3. Pick "delete photos" from the menu. 4. Nothing will happen! We had a discussion here: http://forums.adobe.com/message/49182... This is probably newly formed LR 4.3 bug.

I note RW2 Files from the Panasonic GH3 and imported as DNG in LightRoom do not show GPS location in EXIF data even though it is present in the original file and the DNG file. I'd like to report this as a bug. (LR4.3/Win 7 64bit)