Lightroom Classic 8.4 has been released today. The engineering team has spent this release cycle focusing on performance improvements, including some foundational work that you can’t see, as well as the usual bug fixes and new camera/lens support. The entire Lightroom cloud ecosystem has also been updated.
Update – A couple of days on, the release is looking very stable. There’s a couple of bugs being reported:
- Lower specification GPU’s can no longer enable any GPU acceleration, although it worked in 8.3 and earlier.
Simon Chen (engineer) has this to say: If your OS, GPU card and driver version does not support the DirectX 12/Metal, then the OpenGL based GPU acceleration fallback is no longer available in the latest LrClassic 8.4 release (also applies to ACR 11.4, LrCC 2.4). Although this is recognized as a bug, but the team has planned to drop OpenGL support in the next release. The reason is that some OS vendors have make it public that they will deprecate the OpenGL API soon. Practically, this typically means the bug will show up if you have a Windows 7 OS and/or older version of GPU card or driver. There is currently no known workaround for the bug. The team is investigating possible temporary relief. For the long term, customers are strongly recommended to consider updating your machine to the latest Windows and macOS and GPU drivers to take advantage of the possible GPU performance gain. - There’s an issue with HDR/Pano merges on macOS 10.14.6 with earlier LR versions as well as 8.4. This appears to be due to an operating system change, and is being investigated urgently.
Advanced GPU Improvements
Since version 6.0, Lightroom’s been able to use the GPU for display visualization – in other words, to improve how quickly pixels are drawn on the screen, especially on high resolution monitors. In this release, Lightroom can also use higher-specification GPUs to speed up image calculations in the Develop module, so when you move a slider, it’s much faster to update.
To benefit from these latest enhancements, the minimum graphics card requirements are slightly higher than the basic system requirements. On Windows, you’ll need Windows 10, a graphics card with DirectX 12 support, at least 2GB of VRAM and a driver released in the last few months. If you own a Mac, you’ll need macOS 10.14 or later (ideally 10.14.5+), and a graphics card with Metal support and at least 2GB of VRAM. The photos also need to be set to Process Version 5 to benefit from these performance enhancements.
Because there are many possible combinations of GPUs, drivers and driver settings, there are some new preference settings. Auto is the default, Off is useful if you get crashes or strange artifacts, and Custom allows you to pick which GPU enhancements to use.
Batch HDR/Panorama Merges
By popular demand, you can now select multiple collapsed stacks and merge them to HDR or Panorama in one go, rather than having to start each merge individually. Real estate photographers rejoice! Combined with Auto Stack by Capture Time, this will be a real timesaver. If there’s more than one stack selected, it bypasses the dialog and uses the last-used settings, just like the existing headless shortcut. It’s also smart enough to skip any loose photos in the selection.
Book Auto-Create Cell
Dragging a photo from the Filmstrip onto an empty space on a page now automatically creates a cell for the photo.
Export as PNG
After many years of feature requests, PNG format has been added to the export options! PNG is primarily used on the web, particularly for graphics or images with transparency.
Color Labels for Collections
In Lightroom 7.4, we gained the ability to add color labels to folders, and in 8.4, they can now be added to collections, smart collections and collection sets too. They’re useful for marking workflow progress and highlighting the most important folders.
The folder/collection color labels can now be given different names to the image labels, so red labels on images might mean they’re HDR images, but a blue collection may mean it needs editing.
Filmstrip Index Numbers
The Grid view thumbnails have displayed an index number since the earliest Lightroom releases, but they’re now visible in the Filmstrip too.
New camera support:
- Canon PowerShot G5 X Mark II
- Canon PowerShot G7 X Mark III
- Hasselblad X1D II 50C
- Leica V-Lux 5
- Panasonic LUMIX DC-GX880
- Click to view the full list of supported cameras
Tethering for new cameras:
- No new tethering in this release
- Click to view the full list of cameras supported for tethering
New lens profiles:
- Canon RF
- Canon RF 24-240mm F4-6.3 IS USM
- Canon RF 28-70mm F2 L USM
- Canon RF 35mm F1.8 MACRO IS STM
- Canon RF 50mm F1.2 L USM
- Canon RF 85mm F1.2 L USM
- TAMRON SP 35mm F1.4 Di USD F045
- TAMRON 35-150mm F2.8-4.0 Di VC OSD A043
- Zeiss Otus 1.4/100 ZE
- Nikon F
- Nikon NIKKOR 28mm f/2.8 AIS
- TAMRON SP 35mm F1.4 Di USD F045N
- TAMRON 35-150mm F2.8-4.0 Di VC OSD A043N
- Zeiss Otus 1.4/100 ZF.2
- Sony FE
- SIGMA 35mm F1.2 DG DN A019
- SIGMA 45mm F2.8 DG DN C019
- Sony FE 200-600mm F5.6-6.3 G OSS
- Sony FE 200-600mm F5.6-6.3 G OSS + 1.4X Teleconverter
- Sony FE 200-600mm F5.6-6.3 G OSS + 2X Teleconverter
- Sony FE 600mm F4 GM OSS
- Sony FE 600mm F4 GM OSS + 1.4X Teleconverter
- Sony FE 600mm F4 GM OSS + 2X Teleconverter
- Tokina FíRIN 100mm F2.8 FE AF MACRO
- Click here for the full list of available Adobe Lens Profiles
Bug fixes:
There are loads of bug fixes, but Adobe only publishes the ones that were reported by users:
- Cosmetic glitch when using right-click on the filter bar
- Library filter panel stops showing number of images in each category
- Zooming not working in the map module, using the two-finger up/down or scroll wheel
- Moving pages in Book module
- Different treatment of XMP sidecar when using “import” vs “add to this catalog during export”
- Incomplete and out-of-date documentation for Preferences > Lightroom Sync
- Stripping timezone information from the “Date Created” field
- HEIC photos import with Metadata Status: Changed On Disk
- Library collection panel scrolls unexpectedly when you duplicate/rename/delete a collection set
- “Waiting for Connection” after Sleep
- Book Module: Page Text feature not working when pasting Page Layout
- Constrain Crop not saving in preset
- German translation of “Aktualisierungen” inconsistent
- Aperture import not working – stuck on “Checking Aperture Library”
- Export to DVD Missing XMP Files
- Cannot merge panorama in 10.14.6
If you find another bug, click here to learn how to report it to Adobe.
How do I update?
To update, go to Help menu > Updates or click the Update button in the CC app. The update servers take a while to push the updates around the world, to avoid overloading the servers. You can also open the Creative Cloud app, click the … icon (top right) and select Check for Updates to give it a nudge.
Is the book updated?
The eBooks for Adobe Lightroom Classic – The Missing FAQ are already updated for these changes, and can be downloaded immediately after purchasing. If you’re already a Lightroom Classic Premium Member, the updated eBooks are available for download in your Members Area.
Dear Victoria
Nikon Z6 and latest Lightroom release
I’m seeking your guidance on the following matter …
After using my Nikon Z6 camera for a while and importing raw (not JPEG) image files into Lightroom (Lr) for processing I noticed the Lr default preferences/settings were being overridden by the Z6 picture control setting I used to shoot an image (e.g. Standard, Vivid, Monochrome).
I thought I had subsequently fixed this issue through research and support from Adobe for import default to Lr Adobe settings, I assumed for colour and monochrome. All seemed to be working well. Recently, I did an Lr update and I currently use Lightroom Classic version 8.4.
Yesterday, I shot in monochrome and have just noticed that my files have been imported as Nikon Camera Monochrome V2, overriding Lr default settings again. So, I just did a Lr full preferences reset and tested the import again by taking some colour and monochrome images then importing into Lr – the Nikon settings are now overriding Lr settings.
It seems that the recent Adobe update has not maintained prior settings …. I contacted Adobe this evening and asked for advice on how to permanently ensure (regardless of updates, etc) that Nikon Z6 settings don’t override Lr settings on import (whether in colour or monochrome, whatever Nikon Z6 setting).
Adobe advised me that the Nikon Z – Lightroom import issue is on-going, and its engineering team is currently working on it. In the meantime, I was provided with an Adobe workaround:
https://helpx.adobe.com/camera-raw/kb/white-balance-issue-color-cast-with-nikon-z-6-raw-file.html
but was told if I still face the issue, downgrade Lightroom into 2.3.1. I advised that it’s not a white balance problem I’m dealing with; it’s an import problem. Adobe said it’s the same issue with the white balance and expects the problem will be resolved soon, but it does not have the exact date. Adobe said I “… can reach … back after the next update so that we can share the information”. Not exactly sure what this means …
Essentially, I’m looking for a permanent ‘fix’ to ensure Adobe Lr preferences are maintained. So, I’m wondering if you can provide guidance on (1) if it’s wise to try the colour balance work-around, (2) if you have an understand of the issue and have clearer advice than what Adobe provided, or (3) other suggestions?
Hope this makes sense … thanks in advance …
Regards
Kelvin
The Z6 and Z7 are the exceptions to the general rules. Nikon are saving LR-compatible XMP data, which overrides the LR defaults. The solution, if you’re using Classic, is to apply a Develop preset in the import dialog with your preferred details. That’s applied after the xmp is read, so it should retain your chosen settings.
That Z6 issue you linked to was fixed, but there is still an unrelated open issue for Z7, which may apply to WB problems. https://feedback.photoshop.com/photoshop_family/topics/lightroom-camera-raw-nikon-z7-raw-processing-and-white-balance
I am on Windows 10 Pro version 1809 and after updating to Lightroom Classic 8.4 the Batch HDR/Pano merge did not work for me after updating. What is worse is that you can’t use the headless shortcut mode. So I had to revert back to version 8.3.
Here are some things I tried to fix it. Tried all possible selections (Auto, Custom & Off) under the performance tab regarding use of the graphics processor. My video card: DirectX: NVIDIA GeForce GTX 1070 (26.21.14.3170) I made sure the latest Video Driver was installed. Nvidia Studio Driver version:431.70 release date: 2019/07/29
That would be worth reporting Ron. Here’s instructions on how to report it to Adobe: https://www.lightroomqueen.com/send-bug-report-feature-request-adobe/ There are some reports of merge not working, but all on macOS 10.14.6.
So I was excited to see what improvements I’d get if I checked Use GPU for image processing, but it’s grayed out on my Windows 10 system. I believe I have checked all the requirements and updated some things and am now fully compliant (and rebooted), but no progress. Are other folks having this problem too? Any ideas on how to go forward figuring this out?
Thanks.
What’s your graphics card and driver version Phil?
It’s an NVIDIA GeForce GTX 1050 Ti. The version claims to be 2.1 NVIDIA Build_224, which doesn’t look anything like the required numbers I’ve seen online. But I’ve already updated to the latest drivers. And updated the Directx and the GL to satisfy the requirement.
David Franzen (engineer) posted the driver number he’d tested on this thread: https://forums.adobe.com/thread/2646121
And if that doesn’t do the trick, you might try the clean driver install here: https://helpx.adobe.com/lightroom-classic/kb/lightroom-gpu-faq.html
Wow, Victoria, I installed the 431.70 driver that David Franzen links to and now I’m all set! Thanks so much.
Phil
I’m wondering if I have found a bug.
Today I needed to export some processed RAW files as jpeg with sRGB profile with a file size of 2MB. I have successfully done this previously but now I am now the file size is much smaller than 2MB (less than 1MB) after I have exported. I have even tried setting the export size as 4 and 5MB and the file size is still well below 2MB.
[Corrrected grammar]
I’m wondering if I have found a bug.
Today I needed to export some processed RAW files as jpeg with sRGB profile with a file size of 2MB. I have successfully done this previously but now the exported file size is much smaller than 2MB (less than 1MB) after I have exported. I have even tried setting the export size as 4 and 5MB and the file size is still well below 2MB.
That sounds quite normal. Some photos compress more than others, and some have fewer pixels because they’ve been cropped. Set the quality to 100 and uncheck the resize checkbox, and you’ll get the biggest JPEG you can out of that raw file.
I used to be able to export a RAW file to jpeg and specify the file size and usually it did end up being around the file size I had specified. I leave the resize checkbox unticked as typically it is downsizing the original image.
Only since the update I am no longer able to achieve the file size that I want.
I have been asked to provide 2MB jpeg files for publishing in a newspaper. I know that it is best to set the file size in pixels but at the moment the paper are insisting on 2MB files which is why I am now struggling.
What camera shot the photos, what pixel dimensions is the original, and have you cropped them?
I am very happy to report that Library and Develop performance has very much improved on my Late 2014 27″ iMac 5k with i7 and 24GB RAM.
Up until this v.8.4 update Lightroom Classic was becoming almost impossible to use for editing when using lots of local adjustments.
I have set the GPU to be used for Display and Image Processing in Performance preferences.
For me the v.8.4 performance updates were long needed. Maybe it is not so noticeable when using a non-4k display.
That’s great to hear Trevor!
I only wish they would add stacking to the mobile version. I use the mobile app because my phone is more powerful than our home computer. But they added so much lately, so hopefully stacking will be there soon.
I’ve used Photoshop Elements for a long time. I would like to change to Lightroom. What is best way to learn Lightroom?
Barbara Dalderis
Start with my free Quick Start ebooks, available to all free members of this site. Click Register at the top of the page to sign up, click the confirmation link in your email, then you’ll find them on the Downloads page. That’ll give you enough basics to keep you out of trouble, and you can go from there.
Thanks again for a great “What’s New” summary and updates to eBooks.
Since downloading the update today my Lightroom Classic won’t open now …… the program just hangs and doesn’t respond and I have to force quit.
I’m using a MAC ….. please help !!!!! It was working just fine before the update.
I’d try uninstalling, rebooting then reinstalling, in case you have a corrupted install.
Peter, did you try the proposed solution, and if so, did it work? I’m facing the same terminal spinning beach ball….
I’d like to evaluate what performance improvements might be provided in my environment by the addition of GPU-accelerated editing in the desktop version of Lightroom 8.4. Is there some way to install a new rev of LR without overwriting the old one? (I’m running MacOS 10.14.6, in case that’s relevant.)
Hi Chris
No, 8.4 overwrites previous Classic versions. Set to auto I’ve found it works well. This version just gives more manual control over GPU usage if you desire it.
Since I posted my query earlier today, I’ve figured out one somewhat awkward and laborious way to do a comparison: clone the boot drive; boot from the cloned drive; install the new rev on the cloned drive; finally, boot from the original drive to test the performance with the earlier rev and from the cloned drive to test the performance of the new one.
I’m not sure I’m quite that curious, though.
I just skip back and forth by uninstalling/reinstalling through the CC app. As long as you have fast internet, it doesn’t take that long.