Bug Reports

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

The title letters in Cyrillic fonts (e.g. Russian) don't print correctly on the spine of the cover. Normally, they should be turned 90 degrees to the right. What I see is that they keep standing.

I'm using LR4 on 2 screens; with the grid module on one screen, develop module on the other. When I select a photo from the grid on screen 1, then move to the develop module on screen 2, as the pointer moves across the grid module the last photo that is touched from the various thumbnails on the "grid" is the picture that gets displayed as the develop module "navigator" picture in the upper left corner. The picture I selected remains in the main screen of the develop module, but the upper navigator picture is whatever the mouse pointer touched last on the grid screen. Zooming and scrolling in the "navigator" window will move the develop module main window to the equivalent point location though the pictures are different. Thanks, hopefully I have described the bug sufficiently.

This is in LR4. I have a smart collection that matches photos whose keywords are empty. I select the collection, go to loupe view, hit Control-K to focus on the keyword input field, and start tagging photos one at a time by entering a comma-separated list of keywords. When I hit Enter, the current photo is removed from the smart collection (since it now has a nonempty keywords field) and LR switches to the next one with the keyword input field still active. This works great for photos; I can plow through them pretty quickly entering keywords as if I'm inserting lines in a text editor. But when I hit Enter after tagging a photo and the next item in the smart collection is a video, the keyword field loses focus and I have to hit Control-K again. I very often fail to notice the loss of focus and start entering my first keyword, which causes all sorts of havoc as LR interprets the letters in the keyword as keyboard commands. Occasionally the problem happens with the opposite transition (fi

In LR 3, the field "durationInSeconds" returned by photo:getRawMetadata() is a number. But in LR 4, it's a userdata that tostring() shows as "RatioTime( 1847/6 )". Some tedious experimentation (absent documentation) shows that the method toNumber() will convert it to a number. Was it intentional to return this field as a built-in object? I suspect that this is a bug, that the intention was to convert the RatioTime to a number before returning it to the client caller. All other SDK objects have names that start with "Lr".

After updating from LR3, LR4 has reset my tone curves. I use custom tone curves on almost every picture, and all my contrast treatments this way seem to have gone. Initially the previews were still the old ones, so I only noticed after opening several pictures in the develop module, just to see my meticulous tone curve adjustments be removed. Is anyone else seeing this?

Note: Not to be confused with http://feedback.photoshop.com/photosh...! While in adjustment brush, the keyboard shortcut for A/B change malfunctions after any development slider is changed and the mouse cursor still hovers over the changed slider. The malfunction depends on the language: If the A/B-change shortcut has another meaning, that is executed. If not, nothing happens and the shortcut works when pressing it another time. Example: In English GUI, A/B-change is the "/" key, but it has also the meaning "deselect active photo". So, to reproduce in english: 1. Enter adjustment brush 2. Draw some brush strokes 3. Change some slider (e.g. exposure of the brush itself), don't move mouse away from slider! 4. Press / Expected result: Brush changes from A to B or vice versa Actual result: Edited photo is deselected and "no photo selected" is displayed. Lightroom 4.1 RC 64 Bit, Windows 7. In Lightroom 3.6, the bug does not appear. P.S. Same as the other bug: Of course only a minor one, but

Several of the fonts Lightroom will let me choose come up with an error saying they aren't available. And then the selected font seems to be the last one I picked (preview shows the font I selected, but the font name doesn't update consistently).

As Dorin Nicolaescu-Musteață pointed out here: http://feedback.photoshop.com/photosh..., a side effect of the bug described there is that "dummy" history entries are created for the photos that are not affected by the change (history entries that did never really happen). And that this also happens with Auto-Sync. But that is in fact a whole new different bug. ==> When Auto-Sync is active in develop, and mixed PV2010/PV2012 photos are selected, all changes on PV2010-only-Parameters (e.g. fill light) will appear in the histories of all selected PV2012-photos, although no change was applied to these photos. And vice versa: All changes on PV2012-only-Parameters (e.g. highlights) will appear in the histories of all selected PV2010-photos. This includes the changed basic controls, the old/new clarity, as well as editing the point curve (note that the PV2012 RGB point curve does *not* auto-synch to the PV2010 point curve, and vice versa). Edit/P.S.: The same happens for PV2010 vs. PV2003:

Select some photos in grid view, partly with PV2010 and partly with PV2012. The quick develop controls display for PV2012, but are disabled, which is logical because of the mixed PVs. Everything is OK so far. However, the clarity controls are still enabled, and they apparently change only the photos with PV2012 (including resetting clarity by clicking on the label). In this situation with mixed PVs selected, the clarity controls should be disabled, too.

A snapshot *created* in PV2010 does not store a point tone curve. 1. Switch to PV2010 2. Edit the point curve somhow 3. Create a snapshot 4. Edit the point curve again 5. Recall the snapshot Expected: Point curve reverts back to the edit in step 2 Actual: Point curve reverts back to "middle contrast" Shapshots that are *updated* rather than *created* behave correctly! LR 4.0 64 Bit, Win7. Note: This problem is probably related to (but not the same as) http://feedback.photoshop.com/photosh... and http://feedback.photoshop.com/photosh...

1. Use the file renaming in library, enter the file name editor and accidentally select one of the "Shoot Name..." presets (that do not work there - as expected, i.e. no shoot name is inserted). 2. Open import dialog, select Copy or Move, go to "File Renaming", activate it and select the same "Shoot Name..." preset. Expected result: The "Shoot name" input field is enabled (and appears in the "fewer options" mode) so one can enter the shoot name. Actual result: The "Shoot name" input field is disabled (and does *not* appear in the "fewer options" mode). One must restart LR in order to get it functional again. Further observed effects in that state: - When editing the file naming template (from within import dialog) and choosing the affected "Shoot Name..." preset, the shoot name place holder is not inserted, however it can be inserted using the Shoot Name button. - The *other* "Shoot Name..." preset still works! - An import preset containing the affected "Shoot Name..." preset still wor

After I enter an e-mail address and subject, I hit send, which immediately returns "Unable to Export: An Internal Error has occurred: AgExportRendition: can not import a photo exported to a temporary location." I found a report of this bug for the Beta, and tried the solution there of deleting the "For Email" preference file. Did this and restarted LR, but it made no difference. I am running with Administrator privileges on Vista 64bit, using MS Outlook 2003. I upgraded from LR 3.6 to LR 4, and am in a catalog that was converted from LR 3.6 to LR 4. LR 3.6 and a 2.x version are still installed on the same computer.

While exporting photos via the Facebook Publish Service in Lightroom 4, I receiver error message "An Internal error has occured. expected string argument to JSON.decode()" and "Can't update this collection. An internal error has occurred: expected string argument to JSON.decode()" I also received the second error while importing photos. OSX 10.7.2, Macbook Pro, LR 4.0