Bug Reports

It started out of nowhere today. I restarted the program, I checked for updates and updated the software. I have only one photo selected, but when I click P on my keyboard to flag an image, it flags the image that is immediately after the one I have selected, in addition to the selected image.

A couple of versions ago, after the update, I realised that the develop sliders had shrunk. I thought it was a GUI design change until I switched to English. It was a surprise to discover that in my language the sliders are a lot smaller. I'd get it if it was because of a long caption that needed more space (as it is in Temperature) but as you can see in the screenshots provided, there's a huge amount of free space that is not needed for the caption. No need to say I haven't touched the panels width.I was waiting till the next update hoping this was fixed but in this last release it's not done yet.Spanish version.English version.

When you create a metadata preset using Save Current Settings As New Preset, LR incorrectly rounds the coordinates of the selected photo to the nearest second before saving them in the preset.   When the preset is applied to another photo, it will get the rounded coordinates, rather than the original.    On average, this can result in the second photo being about 17m / 55' away from where it should be.Tested in LR CC 2015.10 / OS X 10.12.3.To reproduce:1. In the Map module, select a photo A in the filmstrip.2. Paste these coordinates into the Metadata > Location > GPS field:37.899630, -119.221138(which is 37° 53' 58.668" N, 119° 13' 16.0968" W).3. In the Preset dropdown, select Edit Presets.4. Do Check None and then check the box to the right of GPS.5. Save the preset as "Test GPS".6. In the filmstrip, select another photo B and apply the metadata preset Test GPS.7. Zoom in the map all the way and observe that photo B is about 12m from photo A.8. Open the file "Tes

Hi, Lightroom 4 beta seems great so far (I'm an LR3 user), but the maps feature (which I'm most excited about) exhibits perplexing behaviour when searching for a specific lat/long in non-urban areas. Repro steps:   Paste the following lat/long (-27.033813,153.465791) into the maps.google.com UI and search. Google maps places 2 markers on the map: a green arrow showing the actual position (a helipad on Moreton Island, Australia)   a red blob showing the nearest house (in a resort on the same island but 18 kilometres away).   Paste the same lat/long into the Lightroom 4 beta "maps" module search and note that LR4beta is treating the nearest house as the result, not the actual lat/long (i.e. the helipad).   Note that repeating these steps for an urban lat/long (e.g. the position of your house) produces very accurate results. This may be a limitation with the google maps API, but it is an unexpected (and unwanted behaviour). Entering a lat/long should take you to th

Only noticed this since last update to 2015.10 - when in Develop module, press F for full-screen view of current image.Press F to toggle back to Develop, then arrow to next or previous image - Loupe Info at top left doesn't display Info 1 or Info 2 details, only filename. Pressing I to toggle the Loupe Info display cycles through again. Have restarted LR & system - can reproduce issue.

I am using Lightroom CC 2015.10 and Mac OS 10.12.4, but I think that this behavior has been present forever in Lightroom for Macintosh.Lightroom "closes" the text box for all metadata when the focus is changed from Lightroom. This is different behavior than almost all other applications on Macintosh, which close the text box when an enter or carriage return (or mouse click) moves the focus out of the box. This makes it very difficult to copy and paste metadata from other programs into Lightroom.My major problem is that I use a 3d party clipboard manager (Keyboard Maestro). I load up a number of text strings into different "clipboards" and I want to paste from them into Lightroom. But the moment I choose a clipboard to paste from, Lightroom loses focus, and closes the text box, so that the paste fails. I have to go back to LR, click on the text box, paste using the Lightroom internal command-V. This is different than every other program I own, and a big frustration.But here is a frustra

I'm on the latest Lightroom CC and OS Sierra and I have found that Lightroom is not automatically detecting my CF card when inserted. I have the auto detect box ticked etc and my card reader is a Lexar USB 3, any ideas?

When using the new face detection functionality in LR CC, "Named People" are represented in People view as a thumbnail, which, along with the name iyself, includes the total number of images associated with that person. However, once the number of images exceeds 100, the thumbnail display truncates the number so that the last digit isn't shown, e.g. 254 becomes 25... If you hover your cursor over the thumbnail then the full value (e.g. 254) is displayed. This is on Windows 7. Looks like a definite bug to me.

List of Lightroom 4.2 export presets column in the export dialog pop up window is way too narrow. It should be wider. Either user controlled via dragging or otherwise. Currently it cuts off after about 22 characters. This is more than annoying if you have a list of presets with meaningful names. The only way to see the full name of the preset is to go to the renaming option. Not good if you want to manage many presets. I can't understand the "why" either since the total window is not large and being able to resize column widths is commonplace in even the simplest applications. Is there any way to configure this? If it cant be solved right away this should be a feature request.

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