Monday, February 19, 2018

Lightroom Classic CC 7.2

Priya Alexander:

We are pleased to announce the latest update of Lightroom Classic. We have made some significant performance enhancements and added a few key features that will help optimize your photography workflow. When customers talk about performance enhancements, there are generally two categories of improvements requested: Interactive (how quickly the interface responds to your actions) and batch processing (how efficient Lightroom is at utilizing system resources and completing batch tasks). This update is focused on batch processing improvements and we’ll continue to focus on both Interactive and Batch Processing improvements going forward.

We have made significant strides with our partners at Intel to optimize CPU and memory usage so that performance will scale better across multiple cores on computers with at least 12 GB of RAM.

DL Cade:

Our own tests also showed a noticeable speed boost when it came to exporting files, and a massive increase in performance on import.


Adobe was adamant that this update is just the beginning. The company is “pleased with these performance improvements” and believes Lightroom Classic users will be please as well, but Adobe also told us it is “far from done.” The company promises continued performance optimizations and improvements in future releases of Lightroom Classic CC.

It does feel quite a bit faster to me. Additionally, the database schema has changed—at least compared with the 6.x version that I was using—and that shrunk my 2 GB catalog by about 500 MB. There are also some new features.

See also: Why Lightroom CC Is a Big Step Up from Apple’s Photos.

Previously: New Lightroom CC and Lightroom Classic CC.

2 Comments RSS · Twitter

Unfortunately, even though it is supported in Lightroom CC and Photoshop CC, Lightroom Classic CC 7.2 still doesn't support the HEIF format.
And according to it doesn't look like it is very high in their priority list…

Good to see Lightroom Classic still getting updates, even it it's not complete feature parity.

Leave a Comment