Bug Reports

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

Lightroom 4 does not show any pictures in folders with >N pictures! In my case, N is about 400. No matter if I try to view exisiting folders, or if I import new pictures. Lightroom tells the right number of pictures in the folder, but reports "no pictures" when trying to view the folder contents. Folders with <N pictures work fine. Catalog has been imported and converted from Lightroom 3.6. I am not able to use Lightroom 4 now. The problem is already known, see http://forums.adobe.com/message/42743... This is very annoying. Please let me know when we can expect a solution. Is there any place where a customer who has bought Lightroom can contact Adobe directly on this subject? Thanks.

Lightroom 4 doesn't show effects preview of presets at Navigator tab on mouse roll-over over presets. It's only when working with second monitor (F11)! When the second display turned off, the feature works as it should. And, when working with the second display, primary display usually doesn't even show correct preview in Navigator (Develop Module)

When converting from a LR3 catalog, as well as when switching back manually to PV 2010, the new noise sliders ("Details" for luminance and color, as well as "Contrast" for luminance) are not active and cannot be changed. I have no idea if just the sliders are disabled or the associated development settings vanished, too (as it is the case for the tone curve). LR4.0 64 Bit, Win7, tested with a RAW file from Canon 40D.

After upgrading to LR4 many of my previews don't show in some of my overlaying folders. It only says that there's no photos in marked folder (don't know the english translation exactly since my version is in swedish). From the beginning I couldn't see the previews in som folders at all but after imprting them they showed up. In some of my overlaying folders (containing folders within folders) I can see all photos but in others not. It's especially annoying in the All photos folder since I can't make an overall search. The same phenomenon occurs when searching on some keywords. Sometimes it says in the metadata-tab in under keyword that ther's no photos but they show up anyway, though in the keywordlist it says the number of photos in the folder. Sometimes no photos at all show up. I have about 65 000 photos in this particular catalogue.

Why has Adobe not proactively told users upgrading to V.4 of the damage to their back catalogues because of the loss of tone curve data? Adobe are actively allowing people upgrading to cause significant damage to thousands of images through the loss of tone curve data. I can only imagine in the hope that not many upgraders notice their images being damaged. That is a truly reprehensible way to treat a loyal client base, and Adobe risk serious damage to their reputation as this issue become a real headache for more & more users. Anyone senior from Adobe care to comment on this?

I'm using Lightroom 3.4.1, 64bit on Windows 7 I really want to be able to enter CR/LF when entering photo metadata caption text. This works and displays fine in Lightroom when entered using Ctrl/Enter, and is recorded correctly in the photo file or xmp sidecar as " & # x A ; ". The problem is that if this data is ever re-read from the xmp sidecar or embedded data, Lightroom no longer displays the CR/LF, so for example: Line1 Line2 gets displayed as: Line1Line2 The " & # x A ; " must still be in the data, it is just ignored. In fact, if a CL/LF is again entered, it displays in Lightroom's Caption box, but gets doubled in the data files. So "Line1 & # x A ; Line2" gets re-written as "Line1 & # x A ; & # x A ; Line2" in the sidecar. I've got thousands of files like this, so this is a real big problem for me in Lightroom. It would be nice if CR/LF in captions would be displayed in other Lightroom features like slideshows, but that would be more a feature. The improper d

Lightroom 3.6: Identity Plate in Web Module -- custom plate is not working. When creating a web gallery and trying to use a custom graphic as an ID plate, LR creates the ID plate by converting the graphic to a PNG file. For some reason, the converted PNG is blank for some original graphic files. It does not matter whether the original is JPG, BMP or PNG. I have posted this issue on the LR forum at adobe.com, but so far no one has come up with a solution. One of the other users has confirmed the same bug in LR 4 beta. For a full description of the problem along with sample files, please see http://forums.adobe.com/message/42359... Maybe someone here can shed some light on the problem. Thank you. John

Hi, In LR, I have an intermittent problem where for Folders published to Hard Disk, the folder name sometimes is not visible, only the number of items in the folders. See the 2 attachments. I have to quit LR and restart the application to resolve the problem, until it happens again a few days later. My system is in french. Is this a known bug? Thanks,

There's a bug between the Grid (2nd monitor) and Navigator. If I hover the thumbnails in the grid, Navigator will show the last image I hovered and not the current one that is selected. Also, it won't show preset preview if I select the image by the grid. So basically, hovering, selecting and picking the images in the Grid messes the view in Navigator. Filmstrip is working fine. It was already mentioned and documented during the beta phase but wasn't fixed: http://forums.adobe.com/thread/948447

Steps to reproduce: 1. Load a RAW file with known lens into develop module 2. Klick "Set Default..." and "Restore Adobe Default Settings" 3. Reset (the photo has now Adobe default settings, profile correction is not active) 4. Activate profile corrections 5. Set profile corrections setup type to "Default" (should already be set upon activation) 6. Klick "Set Default..." and "Update to Current Settings" 7. Reset 8. Also reset (or import) some other photos taken with the same camera 9. Look at the camera's Default_nnnnn.xmp file in Adobe\CameraRaw\Defaults Expected results: - After the second reset, the profile corrections setup type *remains* at "Default" - Other photos are reset to / imported with profile corrections setup type "Default" - Default_nnnnn.xmp contains crs:LensProfileSetup="LensDefaults" Actual results: - After the second reset, the profile corrections setup type *changes* to "Custom" - Other photos are reset to / imported with profile corrections setup type "Custom" - De

Lightroom 3.5RC says "Can't update this collection: An internal error has occurred: assertion failed!" when I try to Publish a Hard Drive service that has modified photos. I use it regularly and have had no problems prior to 3.5RC.

Peculiar. I am losing the ability to use the right click functionality of my mouse within LR. Of note - Windows 7 64bit - on the rest of my computer i have no such issues (anywhere). - it seems to happen after i have had the program open for extended periods +30-40min. - only seems to have started with 3.4 (for me at least) - re-staring Lr solves the issue for another 40 min Seems to have been reported before http://forums.adobe.com/message/3321022 http://www.flickr.com/groups/adobe_li...