Lightroom Classic

When you are in B&W mode and have custom settings in the B&W Mix panel and then convert the image to colour and then back to black and white the B&W Mix panel sliders are all reset to zero.This is changed from the previous version of Lightroom Classic where the settings were retained. This is an issue because if you switch back to colour (maybe to find the colour of what you are changing so you can grab the right slider) and back (to adjust that slider) all your previous settings are lost.I'm assuming this is a bug that someone can fix for the next version.

After applying one of the new B/W presets, and then zooming in, the app crashes.  Re-opening and zooming agin on same image, usually no problem, but if applying a new preset to same image or a new preset to another image and zooming in, it crashes again.  Happens consistently with B/W, seems to be OK with color presets, but have  only tried a few.

With the release of CC 2015.8 / 6.8, it's no longer possible to modify TranslatedStrings.txt for English users on Mac. LR ignores the file:/Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Resources/en.lproj/TranslatedStrings_Lr_en_US.txtWhereas on Windows, LR does read:C:\Program Files\Adobe\Adobe Lightroom\Resources\en\TranslatedStrings_Lr_en_US.txtI confirmed this using "dtruss" on Mac and Process Monitor on Windows.This affects a large number of users who had relied on editing TranslatedStrings.txt:- To provide keyboard shortcuts for commands that don't have them and that don't appear in the menus (e.g. Toggle5Shortcut for assigning the purple label).- To change keyboard shortcuts for commands that don't appear in the menus, e.g. BrushDecreaseKey. Some users report using keyboards for other languages (e.g. German) that they use with LR running in English, and the English shortcuts don't always map well to non-English keyboards.- The Keyboard Tamer plugin relies o

My Lightroom Classic is crashing constantly.  I'm working on a Mac.  Any help would be great right now.

Updated to Classic.  It crashes each  time I close, whether asking to test integrity and optimize and save when exiting, or even when asking to 'skip' these steps and close.  Confidence is low that changes won't be lost, so can't really use this upgrade until this is fixed.  Crash reports sent each time.  Win7Pro SP1, 64bit, GPU acc is off.  No problems with the last 2015.12 release.  I need the latest (Classic) to support a new camera. Thanks.

Beginning with at least the iPhone 4S, and continuing with the 5 and 5s, I see that videos shot with those devices show a capture time that seems to relate to GMT, when it was actually shot at GMT -5. The videos show a correct creation time in Finder prior to import, but this odd shift occurs upon import. I know that the capture time can be edited in Lightroom, but I'd rather see the correct time on import. This happens in Lightroom 5.3, but also occurred all the way back into 4.

I have quite a few Lightroom external editing presets. These were always displayed in alphabetical order in the "Edit In" dialogue box but I noticed that, post upgrade to Mac OS High Sierra, the order seems to have become random. I tried deleting and re-creating but the issue persists. Not the most serious problem in the world but a workflow nuisance. I have reverted to the previous OS with the hope that a later release from either Abobe or Apple will address the issue.

Preferences > File Handling incorrectly says:"During import or when reading metadata Lightroom can recognize dot, forward slash, and backslash separated keywords as keyword hierarchies instead of flat keywords."But backslash is not interpreted as a hierarchical separator.  To reproduce in CC 2015.10 / OS X 10.12.3:1. Start with a photo p1.jpg not in the catalog, with no keywords assigned to its metadata.2. Use Exiftool to assign a keyword containing a backslash: exiftool "-xmp:subject=ZZZ\AAA" p1.jpg 3. In Preferences > File Handling, select these two options: - Treat '.' as a keyword separator- Treat '/' as a keyword separator 4. Import the photo into the catalog. 5. Observe in the Keyword List panel that the flat keyword "ZZZ\AAA" has been imported at the top level. 6. Remove p1.jpg from the catalog, and repeat steps 2 - 5 but using "ZZZ/AAA".  Observe that the hierarchical keyword ZZZ > AAA has been assigned to the photo.

Since updating to LR Classic (7.0.1) the info overlay disappears as I move between modules (Library and Develop typically) and sometimes even when I move between collections and folders. To get the overlay back, I go to the View Menu > View Options > uncheck the box beside "Show info overlay", and then check the box again. There is a delay with the spinning circle and then the overlay appears again.Using Lightroom Classic 7.0.1 on iMac with mac OS High Sierra (10.13.1).

[A number of people are now reporting this for 2015.8 -- see below.  -- John Ellis]Hi, In Lightroom 5 and 5.2, when using the X key, then Delete Rejected Photos, the central display box no longer displays an image. If I switch back to Library mode an image will appear but if I go back to the Develop module, again it's blank where an image should appear! Is this a known issue? ThanksJohn

When in Map Mode I try to move a thumb nail for a photo to correct GPS location. LR Classic CC freezes then System Dumps and I can not capture any data and have to reboot.  I get the LR Dump Dialog but system is frozen and cant do anything. ANyone got a suggestion?  I am windows 10 32GB memory  Using Graphic processor OFF. Current LR class version intalled

Noise reduction effect not displayed in Develop mode when image is smaller than 1:1. Enlarged is ok, but when I set FIT or FILL, image displayed without noise reduction settings applied (I think so).

When I import video files from my iPhone 7, LR fails to import the GPS co-ordinates for many of them.  It does import the co-ordinates for *some* of them.  A simple ExifTool command easily extracts the co-ordinates for all the files, regardless of whether LR failed or succeeded.  There does not seem to be any obvious difference between the files that succeeded and the ones that failed.  I am using LR 6.10.1 on Mac Sierra 10.12.5 and my iPhone is running 10.3.2.

I have just under 100,000 family photos (divided into different folders - family member's name) on an external hard drive. With all the photos I have collected, it is difficult to organize and to find pictures.  Plus it takes extreme lengths of time sorting through the photos.I want to import all photos into Lightroom Classic on my Windows 10 64bit computer.  I need help designing a foundation that works with Lightroom and for me.  Ultimately, I guess I want a Collection/Smart Collection for each family member so I can find particular photos, and be able to continue to add new photos in the future.I have 25 different family member (each has their own folder on the external hard drive).  I do have some videos in some of the family member's folders.Any other suggestions that I might need to add to setting up my Lightroom are greatly appreciated.Thank you in advance for your help in my request.

In LR 7.0.1, re-reading metadata from a photo can create a zombie keyword that can't be deleted from the Keyword List.  This behavior does not happen in LR CC 2015.12.To reproduce:1. Create a new catalog.2. Import a photo that previously had the keyword A assigned to it and saved to its metadata.3. Observe in the Keywording and Keyword List panels that A is assigned to the photo.4. With the photo selected, select A in the Keyword List panel and click the "-" button to delete it. Observe that the keyword disappears, as expected.5. Do Metadata > Read Metadata From File, and observe that A comes back to the Keywording and Keyword List panels again, as expected.6. Select A in the Keyword List panel and click the "-" button to delete it a second time. Observe that A does not get deleted from the Keyword List.  I haven't found any way to get rid of these zombie keywords -- restarting LR, assigning them to new photos, exporting as a new catalog, deleting preferences, etc. do

Lightroom Classic CC (7.1 release).I have the left-most column of the library module (the Navigator, Catalog, Folders, Collections and Publish Services) set to "Solo Mode" so only one section is open at a time. Often (not every time) when I start Lightroom Classic CC and open the "Folders" dropdown it only opens a few pixels - enough to show a list of maybe five, five-and-a-half folders in all. There is no scroll bar so I cannot access the rest of the list. If I close then re-open the "Folders" section using the dropdown, it works properly.Bug needs to be fixed. 

In Lightroom 5 sometimes the Navigator preview pane display gets stuck on a different photo than what I'm working on in the develop module. I haven't managed to figure out when in happens specifically, but I notice it once every few working sessions. Thanks, David

I've just tried to migrate my LR Classic catalogue to Lightroom CC. After updating metadata, finding missing photos and clearing sufficient disk space, I finally got it running. 24 hours later, at 89% complete and 'Im porting albums' I got a message that said;  'Migration was not successful. Mo one is more unhappy about this than us. Except you probably. Please contact our support team.   No log file, no explanation. My photos all seem to be imported, but if it didn't finish, I don't trust that all my photos are imported correctly.   How do I even start troubleshooting this? And how do I delete my cloud photos to start again?   Thanks a lot, Dean

Hello!Looks like I and other users have stumbled upon a new problem. Today I just opened my PC just to find out that I get this error mentioned in the title while both Photoshop and Lightroom Classic CC are launching. I only get to click on "close this program" or look for a solution".Others on the other Adobe forums are encountering the same problem, please look here for more details from more users: https://forums.adobe.com/thread/2414345I am running Windows 7 Ultimate 64bit and I have not done any Windows updates last night or anytime soon. I have an Nvidia GTX 1060 6GB and i have an i7 Haswell 2.7Ghz with 16GB of DDR3 1600Mhz. I have the Nvidia drivers - vers. 388.43.

When exporting images with 'Add to Stack' checked only one (1) image file can be stacked with the original. When a second export file is created using the same original file it is stacked with the original, but the first export file is removed from the stack. The first export file is then moved to the end at the bottom of the Grid view (last image). Changing Sort Order to Capture Time or File Name or A>Z, Z>A has no effect. The file remains at the bottom position of Grid View as the last picture. I also reset the LR Classic Preferences file with no change in behavior.If you right-click on the original file and select 'Unstack' all of the files appear together as expected using Capture Time sort in the Grid view. I checked LR CC 2015.12 using the same image file in the same folder structure and it behaves as expected with all files stacked below the original.Both Windows and Mac OS X platforms exhibit this issue with LR Classic 7.0 and 7.0.1. Please see this post for more details:

The count for people in Lightroom CC only shows 3 digits unless you scroll over the count in which case is shows four digits. For example, I have over 1152 photos on my wife, but it shows only 115 unless I put the mouse cursor over the number.

When dragging photos to geotag them in the map module, it will work for a photo or two then nothing visible happens for subsequent photos. The map also does not respond to zooming, panning nor direct input of a place in the location filter/search box. However, the overview map top-left does respond. Further, if a photo is dragged to the main map, it does get geotagged, evidently based on what the main map window should be showing, based on the location shown in the overview.This bug existed in the previous version as well - very dismayed that it is persisting in 7.0.

Since the last LR update, images have been "stuck" in the Develop module. It happens regularly, but so far I've been unable to identify a triggering event. For example, I was editing an image in Develop this morning. Then went to the Library module and selected a different image. When I clicked back to Develop, the original image I'd been working on was still displayed. Clicking any other module displayed the new image I wanted to work on, but the Develop module continued to display the original image. (Note: I don't necessarily have to select an image in Library to make this happen - sometimes just selecting a new image while still in Develop will yield a stuck image.) If I try to make edits to the image, it is the new image that gets the changes, not the stuck image, so it's only an issue with the previewed image. The only current fix for this is to close and reopen LR. When I do, the image that I wanted to work on is now displayed.I understand from Victoria Brampton that you ma

The last backup date in the general tab in catalog settings is not updated correctly.https://forums.adobe.com/thread/2256634

I found a small bug in the program I think. When I start building smart previews for a wedding, everything looks okay. In the progress bar to the upper left, it shows the current photo it's working on (like 107 out of 3000) or whatever. However, if I go to smaller folder and begin a second round smart previews at the same time, then both tasks show the same total amount of photos. So the wedding album will start looking weird like "1000 out of 600" as if it's working on 400 extra photos that don't exist hehe. I've attached a screenshot of the issue.