Bug Reports

When LR detects that itself and an external application both changed the metadata, it displays a warning badge on the tumbnail. When clicked, a dialog to resolve the conflict appears. => Dialog uses resource MetadataUpdateConflictExplanation (OK). => Tooltip of badge uses resouce MetadataUpdateUnknownError ("error writing metadata"). This seems to be wrong. => I would have expected resource SidecarConflict ("Sidecar file has conflict") for tooltip. Similar behaviour (warning badge, dialog when clicked) happens when an error occurs writing metadata to the file, but with other texts. In this case, I observed the following: => Dialog uses resource MetadataUpdateUnknownErrorExplanation (OK). => Tooltip of badge uses resouce SidecarConflict ("Sidecar file has conflict"). This seems to be wrong => I would have expected resource MetadataUpdateUnknownError ("error writing metadata") for tooltip. It seems that LR sets the wrong tooltip in both cases, i.e. the resource referenc

When one has a keyword hierarchy: In LR3, one could skip a level in selecting which keywords are exported. For example in the hierarchy A, B, C (where A is top parent) one could set A=Include on export, B=Do not include on Export + Export Containing, and C=Include on Export + Export Containing. In this way, on a photo with only keyword "C", on export we'd have A and C but not B. In LR4 all my LR3 keywords that had this pattern were changed during catalog conversion and I can no longer set this pattern. Turning off "Include on Export" now turns off "Export Containing" and "Export Synonyms" rather than leaving them alone as in LR3. This is a HUGE problem for me as I have my entire keyword hierarchy (over 3,000 KW's) designed to allow skipping levels. In addition, I have cases where the actual Keyword is for my workflow and convience but but the synonym is what I want exported (not the actual KW) which I can also no longer seem to do. See screen shots below

I have updated GPS coordinates using the new Map module but these are not output with the EXIF when I export JPEGs from originals of JPEGs & RAW files. I have ensured that Remove Location Info is unchecked regards JWW001

In the map module of Lightroom 4.2 RC, I am finding it impossible to navigate around the map using the small map panel on the left. If I drag the mouse right or down (east and/or south), the map moves itself right and upwards (west and north) and jumps quite large distances. It is better behaved scrolling north. The map very very quickly which makes it hard to be accurate. In one example I started here in New Zealand and ten seconds later was showing me Mongolia! Navigation on the map map works as it did in LR4.1 and does not have these problems. LR 4.2 RC (released 27th/28th August) on Windows 7 64-bit. Russell

When moving a stack consisting of a master photo and one or more virtual copies (should be a common case) from one folder to another (within LR), the stack becomes partially unstacked so that the master photo is no longer part of the stack (but the virtual copies are still grouped into a stack).It does not happen if the stacks are collapsed or the stack consists of master photos only (that are all moved together).Try the following to reproduce:1. Prepare a folder with 1 master photo2. Make two virtual copies. There are now 3 photos in one stack.3. Make sure that the stack is expanded4. Select the master photo or all 3 photos (does not seem to matter)5. Drag them to another, empty folder.6. Select the other folderExpected result: All 3 photos are still grouped into a stack.Actual result: The master photo is no longer in a stack, only the two virtual copies are.When only one virtual copy is used (1 master photo + 1 stacked virtual copy is moved), the stack disappears completely.The probl

I am using LR 4.1 and when I use a vertical perspective correction on a horizontal file and then go to a vertical image and try to use the previous button to apply the corrections the lens correction is applied to the horizontal correction and not the vertical.

Doing a second "Convert to DNG" on another batch of photo with different settings will affect the first task already in progress (it will inherit the settings of the second). Reproducable: Folder 1 with Raw photo's. Do "Convert to DNG...", start converting Folder 2 with Raw photo's. Do "Convert to DNG..." but with "lossy compression (new Lightroom 4 feature). As soon as Task 2 starts, it will affect Task 1 (already in progress): It will start doing "lossy compression" on the raw's that where not converted yet. I observed the difference in file size by accident. Luckily I had a backup.

404 broken link error when clicking on Help->Lightroom Online... in Lightroom 4.1

We have discovered that when updating process from 2010 to 2012 (by setting one then copying metadata settings across), brushes remain on the photo but the exposure setting for these has been unexpectedly set to zero. As a result, retouching (eg brightening faces) is lost until we go back to each brush and correct the exposure value.

Steps to reproduce: 1. Import a proprietary raw 2. set to black and white in develop (or make any other striking visual change) 3. show before/after view: before in color, after in b/w (ok) 4. Go to library, convert to DNG (I used 5.4 compatibility, no other options) 5. Go back to develop, show before/after view Expected: before in color, after in b/w (as before) Actual: The before version is in s/w too. It seems to have changed during DNG conversion. In the same way: 6. Correct before version using history: "Copy to before" of import step 7. show before/after view: before in color, after in b/w (ok again) 8. Choose "update dng preview and metadata" Expected: Nothing happens in LR (only the file is updated) Actual: The "before" version is suddenly in s/w again. It seems to change during "update dng preview and metadata", too. Also, a dubious "from metadata" history entry is created - what does that mean? LR 4.1 final 64 Bit, Win7.

The straighten tool can be used together with the Alt key to display a rotating grid. However, it is extremely slow then. The slowness does not seem to be caused by a slow update frequency, but by the strange behaviour that the grid seems to be recalculated for every position that the mouse cursor was on its way across the screen: The mouse positions seem to be "buffered" - when stopping mouse movement, the straighten tool "plays back" the last mouse movements for a few seconds. LR 4.1 64 Bit, Win 7, Logitech G500 mouse with no special driver installed (vanilla Win7 driver). Mouse sensitivity is set to medium, but the behaviour is the same for low and high. EDIT: I see the same behaviour with the "Wacom Bamboo Fun Small" tablet, also with no special driver installed. So it seems to be a general problem and not related to hardware or setup of my PC.

Many people have complained about spurious "Metadata file needs to be updated" icons appearing on thumbnails in Library mode. That has happened to me off and on for a year with LR 3. I now have a small 16-image catalog for which this happens repeatedly. No matter how many times I select all the thumbnails and do Metadata > Save Metadata To File, the needs-updating icons reappear very quickly, usually within seconds. The metadata is getting written to the files correctly -- it's just that LR doesn't think it has. The test catalog was created with LR 3.5RC on Windows 7 by exporting from my main catalog (also exhibiting the problem). Adobe, you can download the zipped folder containing the complete catalog and images from: http://dl.dropbox.com/u/21811200/bugg... (111 MB) Please let me know if you download it, so I can free up my Dropbox space.

In earlier versions of LR the latest used preset, when choosing Export was highlighted. Now it ́s not. It is choosed, but you can ́t be certain.

It came out in the finnish camera forum (http://www.digicamera.net/keskus/view...) that Lightroom will crash if 1x1 photos are imported to Lightroom 4.1. One person was able to reproduce the problem by importing 1x1 jpeg files created using MS Paint, and other person was able to reproduce the problem in Vista 32 bit.

A folder can not be renamed, if a video is selected. It is evident already reserved by the player. Only when you put your mark on a photo, the folder will be renamed. This is a bug. Ein Ordner kann nicht umbenannt werden, wenn ein Video markiert ist. Es wird offensichtlich schon vom Player reserviert. Erst wenn man die Markierung auf ein Foto legt, kann der Ordner umbenannt werden. Das ist ein Bug. Grüße aus Deutschland

I am using LR4 on a Mac with 8 gb ram, I7 processor and OSX. I have been using LR since LR1. LR4 is terribly slow. Trying to move photos from one folder to another takes about 20-30 seconds per folder on file sizes of about 6 to 12 mb. Is Adobe aware of this? If they are, I'll be patient. If not, it will force me to consider changing programs.

LR4 book module: Exporting book as PDF when book type is set to 'Blurb' (rather than PDF) does not use the 'Blurb' quality parameters (e.g. colour space, jpg compression) but instead uses values from previous adjustments when book type was set to PDF. example: 1. With Blurb selected I exported a PDF using the button on the left hand panel. 2. I changed from Blurb to PDF and dropped the jpg quality and ppi to low values. I exported another PDF and as expected, the file size and image quality where noticeably smaller / worse. 3. I then changed back to the Blurb option in the book settings panel and I exported a third PDF. I expected this to match the first PDF in terms of file size and quality, but in fact this PDF was still small and crappy like the PDF from step 2.

In the LIghtroom 4 Export menu, when exporting a video file, the extension in the File Naming Example doesn't get updated when the Video Format is changed. For photos, this happens immediately. For videos, it doesn't happen until the Export menu is closed (by clicking either Plug-in Manager, Cancel, or Export) and then re-opened. Lightroom Version 4.0 Mac OS X Version 10.6.8

I discovered a very strange performance problem in LR4 final (64 bit, Win7): 1. Load a RAW file into develop module, e.g. from a Canon 40D 2. Reset to adobe defaults 3. Set "Highlights" to a different value than zero, use e.g. -40 4. Change the exposure value. Refresh rate should be relatively fast. 5. Now turn *off* the entire "Detail" section. 6. Change the exposure value. Refresh rate drops dramatically! The strange things are: a) The refresh rate does *not* drop if sharpening, luminance and color noise red. are all set to zero instead of turning of "Details". b) The refresh rate does *only* drop if the "highlights" or "shadows" sliders are set to something different than zero ("whites" and "blacks" do not matter!). The effect seems to happen in all zoom stages, and seems to affect all other settings, too, e.g. clarity and saturation (and even "highlights" or "shadows" themselves). Edit: There seems to be no similar effect in PV 2010 - using recovery and fill light while "Detail" is

Sometimes I go to add a new brush adjustment, but after setting everything up, when I go to apply the first stroke, it immediately aborts/brush is suddenly deselected. Does not happen often. Lr 3.4.1, win 7/64.

using new email photo feature...photos send, but they are not the currently selected photos...they are photos from a prior selection of photos that were emailed...even after shutting down LR and restarting, somehow that cache or selection does not clear. From the composed email preview, it looks like the correct photos are being sent...but when I open it up on the receiving side, they are clearly the wrong photos.. BTW, I am running 4.1 RC, but this also happened with 4.0...running Win7 64bit.

Lightroom 3 will import RAW+JPEG images from my Canon S90 fine. The new release of Lightroom 4 only imports the JPEG images and there seems to be no way to access the RAW (CR2) files to process them.

LR4 (trial) import hangs during import of files if extension has been changed from uppercase to lowercase on Win7 x64 machine. For example: I imported several files named P1000830.RW2, P1000831.RW2, .... Afterwords the file extension was changed to lowercase outside of LR. When reimporting the files (*.rw2) while the old files (*.RW2) were still in the LR Library, the import hangs.

The rendering of a photo in develop is sometimes less saturated than it is in library. To reproduce: Select a CR2 file in library with loupe view on a second monitor. Switch to develop, the saturation decreases slightly. Switch to library and the saturation increases slightly. Switch back to develop and the saturation remains the same Move the contrast to 10 and then back to 0 and the saturation decreases. A sequence of screen shots shows the effect.

Not at all unusual for me to have wonky conversions due to over-strong clarity in locals. Adobe: Please halfen values for local clarity, just like you're doing for global clarity, upon conversion - thanks. I'm not sure if this was an oversight or on purpose, but it's present behavior is often problematic for me - I often use clarity locally instead of or along with globally - they're like a team... (I know you go through the locals to convert brightness to exposure..., maybe do clarity too for next release?). Rob