In my last post I cautioned about updating to Version 7.3 of Lightroom Classic CC (released in early April), as many people were experiencing problems. Yesterday Adobe released an update (v. 7.3.1) to address those issues. Here’s a link to the release notes.
From what I can gather so far, this latest update seems to be working, and people are reporting that most of the problems have been fixed. That means presets are now ordered and sorted correctly, and, for the most part, profiles are no longer being inadvertently changed when applying presets. (Profiles are still sometimes getting changed when I apply a B&W Mix preset to an image. This may not be a bug, however, but an inherent problem with the new implementation of profiles.) And most of the crashes and other performance issues people experienced should be fixed.
However, there is still no option to turn off the full-screen previews when scrolling over the names of presets. Many people have reported that these previews greatly slow down their computers. Adobe is apparently working on this.
To install this latest update, go to your Creative Cloud app, click on the Apps tab near the top, scroll down the list of apps, and click on the big blue Update button next to Lightroom Classic CC. If you don’t see the Update option, click on the tiny menu in the upper-right corner of the Creative Cloud app and select Check for App Updates.
Now that these problems have been mostly addressed, we can start talking about the biggest additional feature in this update: the new profiles browser, with many more options for choosing profiles. I’ll have more to say about that soon.
— Michael Frye
Related Posts: Caution Required with the Latest Lightroom Update; Big Lightroom News
Michael Frye is a professional photographer specializing in landscapes and nature. He is the author or principal photographer of The Photographer’s Guide to Yosemite, Yosemite Meditations, Yosemite Meditations for Women, Yosemite Meditations for Adventurers, and Digital Landscape Photography: In the Footsteps of Ansel Adams and the Great Masters. He has also written three eBooks: Light & Land: Landscapes in the Digital Darkroom, Exposure for Outdoor Photography, and Landscapes in Lightroom: The Essential Step-by-Step Guide. Michael has written numerous magazine articles on the art and technique of photography, and his images have been published in over thirty countries around the world. Michael has lived either in or near Yosemite National Park since 1983, currently residing just outside the park in Mariposa, California.
Thanks, Michael, for this update. I was just getting ready to reply to your previous post about LR. When I received it, I had already installed 7.3 and I had a problem with it losing a folder I had uploaded and worked on––just disappeared. I was getting ready to revert back to 7.2 when this post came, so I’ve updated and hopefully things will work fine. I appreciate this information and, as always, thank you for your fantastic blog and all you do for landscape photography. By-the-way, I loved your blog about Death Valley and the stunning images you posted.
Hmm. I have my doubts that installing the latest update (7.3.1) or reverting to 7.2 would fix this. It’s hard to know what happened from your description, but it sounds like when you updated perhaps Lightroom 7.3 used some previous version of your catalog, rather than the latest version, and that earlier version didn’t include the folder you describe. You might try opening the latest backup catalog made before you updated to 7.3 to see whether that includes the missing folder. If not, you can re-import the missing folder, but how well that works depends on whether you had the option to “Automatically write changes into XMP” checked in your catalog settings. If you did, then whatever work you did to those missing images will still be there, and the images will look as they did when you last worked on them. The images won’t have any Develop History, and won’t be in collections anymore, but at least you won’t have to re-process them. If you weren’t saving changed to XMP then you would have to re-process them all.
Thanks, so much, Michael. I did have “Automatically write changes into XMP” checked so when I re-imported the folder my changes were still there. I did a lot of work on a few of them so at least I have that. Much appreciated! By-the-way, I watch a video of the flooding in Yosemite a couple weeks ago; it was really substantial! I hope there wasn’t too much damage. —Bob