Bug Reports

When raw files are imported into light room with auto tone applied on import, when added to a collection and edited on light room mobile, the files have Full negative values in all adjustments .

I just left LR idle for a few hours and came back to find my 32GB machine 100% memory with 100% disk due to paging with Lightroom being the culprit.If I open up System Info from the Preferences->Performance->Camera RAW section, I can watch the "Real memory used by Lightroom" increasing continuously while LR is idle.Background:Just upgraded to standalone 6.8. Was previously using LR4 with no problems, but needed new camera RAW support. I built this machine myself and it has been rock solid and a great performer for 2 years. I use it for software development running linux in a virtual machine to do heavy multi-core compilation and to run compute intensive multi-threaded/multi-core applications for IC design. Never a problem.OS: Win7 ProCPU: Quad core i5-3570MB: Asus p8z77-v proDisk: 8TB configured as a 3T RAID5 array, 4T standalone and 256G SSDMemory: 16GB just upgraded to 32GB.

Collection name can enter string multiple lines. but, only first line appears on root collection set tree.This must be bug and fix it ether way.1. Inhibit multi-line collection name.2. Multi-line collection names are ok, appear it to collection trees.

mts and m2ts video plays in lightroom 4, but without sound/audio. is this a known bug?

When you Metadata->Export Keywords... from one catalog and then Metadata->Import Keywords... into another catalog the keywords in the new catalog that originally had all the export options unchecked now have the "Export Synonyms" and the "Export Containing Keywords" boxes checked in the new catalog. This means that potentially a lot of previously private information can be published without any warning. The only way you can accurately replicate you Keyword List to a second catalog is to export the whole master catalog and delete all the images from the exported copy.  

Movie files can't have their metadata saved to the file and normally you'd know that because the option to save the metadata is greyed out if you attempt it when a movie is selected. However, if you select 101 or greater movie files, the option becomes selectable. Which is frustrating because it makes you think that Lightroom will save the metadata to the files.

Hi, Not sure if this is the correct place to ask Lightroom questions if not I apologize.  Any way is this a BUG perhaps? Just noticed ......The filename template editor when editing would show an example of what the file options that were selected would look like. (it was right above the big white box near top) Its not there anymore! WHAT? WHERE did it go? I needed to make some changes to a newly imported set of images . in short wrong info was put on 3000+ images . basicly the original raw file #..did not stay with the new filename.some how got deleted when I added new info to filename EXAMPLE WAS NOT THERE.to VIEW how file would look like. I don't have original sd card to get Raw file #s from..... Much work was done to images before I noticed Thanks so much any help would be appreciated .

By default, Export Actions, such as shell scripts, are placed in $HOME//Library/Application Support/Adobe/Lightroom/Export Actions In LR2.7 these worked fine. After upgrading to LR3.4 they no longer work. I get the following error in the System Console: 15/05/11 12:06:44 PM [0x0-0xda0da].com.adobe.Lightroom3[3884] sh: /Users/andrewtj/Library/Application\ Support/Adobe/Lightroom/Export\ Actions/diveexiftool2.sh: No such file or directory After doing some testing, I have found that the spaces in the path are causing it to fail. If I put the shell script in a folder that has no spaces and instead use "Open in Other Application" which lets me choose a non-default location for the script, it all works. This needs to be fixed.

Lightroom:Auto advance:When editing I use the short cut keys when flagging an image (ctrl. + up or down arrow keys) auto advance is set to on, but no longer works.did this change in version 3.4? Auto advance works if I hit the "P" key or the "x " key. on its own. thanks

I'm working with LR 3.4 on a Mac with the latest camera raw and any current updates as required I've encountered the following problem. When I export a print collection it reverts to a standard collection with no layout information when imported back into a different catalogue. The physical files are retained but the print layout is lost and the interface icon for a print collection changes to show that it is no longer a print (layout) collection. Part of my workflow entails prepping my best (IMO) images for my portfolio gallery. The way I do this is to gather the images into a collection set, then create individual print collections with, say two or three images to a page, with borders etc. I then print to file as hires JPEGs, because we can't export from the print module, import into Photoshop to add a watermark via an action (I know this can be done in LR but I want only one watermark per image set not one per image) ready to upload to an online gallery. I prefer to use individual c

Ever since upgrading to 3.4 I have been unable to change brush parameters (ie brightness, contrast) by just hovering the mouse over the slider and pressing up/down keys.. It works for exposure but non of the other sliders.. This Is on Windows 7

I love LR, especially the UX and workflow, but I've been running into a very frustrating problem since upgrading to LR3. In version 3.3 on MacOSX 10.6.7, the "undo" operation often undoes the thing *before* the one it was supposed to undo. This happens when I perform multiple actions quickly (usually with keyboard shortcuts) and hit "undo" pretty soon after (within a few seconds). This happens to me pretty often (every 5-10 minutes). Examples: - I'll start in the Grid view and then change modules with "D" and drag a slider down, then hit "undo", and it takes me back to the Grid view but keeps the slider change (instead of keeping me in Develop and undoing the most recent change). - In some cases, I actually lose a complicated change, as when I make several changes with sliders, then make a change I don't like with another slider, hit undo, and it will undo one of the ones I *did* like (which I can't recover) and keep the one I didn't. - Another example is when I play with some slider,

I'm using the Lightroom Print Custom Package to do layout for my photos. Everything is fine until i have more than 6 pages, on the 7th one no matter what i do (delete cell, add photo) it affects the first 6 page. Has anyone seen this issue?

LR 3.4.1, Win7 64-Bit: Publish to Hard Drive in Format "Original" no longer creates XMP sidecar files along with the published originals. Steps to reproduce:   Create new Catalog   Automatically write Changes into XMP not checked   Import some .cr2 files   Export .cr2 images in format "Original" to an export folder   Create Published Collection, using format "Original" to a publish folder   Drag a couple of images into the Published Collection   Publish the collection   Actual Result:   Images exported as originals show up with .cr2 and XMP sidecar files in export folder   Images published as originals show up with only .cr2 files (no XMP sidecar files) in published folder   Expected Result:   Images published as originals should show up with .cr2 and XMP sidecar files in published folder   The same procedure in LR 3.3 produces Raw and XMP files in both export and published folders. As I don't have LR 3.4 install

Lightroom 3.4.1 64 bit has stopped working, running Win 7. It try to open a file and then crashes. I've deleted the preference file, reinstalled and even tryed to run the 32 bit version, but no luck. Any ideas. The 800 service is only available until 5PDT and when you can call before 7EDT and you have to wait, there is no support there after you get through level one support. I'm really not happy. Any ideas?

Filenames such as (for instance) photographer-place--year_month_day-filename.cr2 are exported by Lightroom 3.4.1's Develop module correctly, without change, into jpg versions. However, Lightroom's web module forces a conversion eliminating the dashes and replacing them by underscores, even converting two dashes into one underscore in the process. TTG Highslide Pro (which I use with LR) states on its website that this is built into the Lightroom web module, and recommends entering one's wishes in the "File Handling" tab within Lightroom Preferences. However, my own LR preferences include the standard File Name Generation option "Replace illegal file name characters with: Dashes (-)" so this would indicate that a dash is not regarded by Lightroom as illegal and therefore should be left alone, as is in fact the case on a normal export from a raw cr2 to jpg: no change in Lightroom and therefore no problem. But export via LR, via TTG oor via LR's own web templates, causes an unwanted conver

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