Category Archives: Enhanced GPU Support

Camera Raw 14.3 – GPU Support for Open and Save

 If there is one thing that Adobe Photoshop and Lightroom users tend to fixate on, it’s performance, particularly how each leverages the CPU and GPU. So, I find it surprising that more hasn’t been written about the recent GPU enhancements for opening and saving files that was introduced in Camera Raw 14.3. More details of what Adobe have to say about this can be found in the release notes 

I suspect the reason that little has been made of the enhanced GPU support is that Camera Raw isn’t particularly easy to use when working with multiple images, which may explain why relatively few users using the multi-image workflow. On the other hand, Lightroom Classic, which doesn’t currently benefit from GPU acceleration while saving files (exporting) is ideal for this type of workflow. Hopefully, we’ll see this addressed in the future.

Having drawn attention to the enhanced GPU support I expect readers will be keen to know how much improvement can be expected and whether their particular  computer + GPU configuration will benefit.  Again, Adobe have provided updated information on system requirements, which can be found here.

The improvements in ‘Open’ and ‘Save’ described are based on a combination of both CPU and GPU rather than just the GPU. This is important because simply transferring the workload from the CPU to the GPU would leave the former idle for the duration of the ‘Save’ process, which may not be the best use of very powerful resources.

While there’s lots of other helpful information in the documents linked above, the most important part, in terms of GPU support for ‘Open’ and ‘Save’, is shown below.

Notice that the memory requirements are actually a lot more onerous than the minimum requirements, and particularly so when the GPU is sharing memory with the CPU, etc.  Does this mean that users with less memory than specified above will miss out? Possibly! However, to check whether your particular configuration can benefit requires a bit of tweaking to Camera Raws Performance > GPU Preference as shown in below screenshot.

Camera Raw – Performance Preferences

Camera Raw checks the GPU capabilities during launch, and if it meets the requirements for full GPU acceleration will set the preference to ‘Auto’. If the test fails, the preference will be set to Off, and while we can manually override the preference and maybe even be able to turn on full acceleration, it’s likely that only very limited improvement will be seen in save times. By way of example, I have a late 2019 MacBook Pro i9 with an AMD Radeon Pro 5500m GPU with 4GB of dedicated VRAM. The GPU fails the initial test because it doesn’t have sufficient dedicated VRAM.

So, now that we know how to establish whether a particular GPU will provide full acceleration it’s time to check the degree of improvement. For this, I’ve used three Mac M1 based systems and the Intel i9 MacBook Pro mentioned above. The three Macs are:

  • Mac mini 8-core M1 with 8-core GPU, 1TB internal SSD and 16GB of unified memory;
  • 16-inch MacBook Pro 10-core M1 Pro with 16-core GPU, 2 TB internal SSD and 32GB of unified memory;
  • Mac Studio 20-core M1 Ultra with 48-core GPU, 1TB internal SSD and 64GB of unified memory; and
  • 16-inch MacBook Pro 8-core i9 with AMD Radeon Pro 5500m 4GB VRAM, 1TB internal SSD and 16GB ram.

I loaded 100* Canon EOS R5 files into Photoshop hosted Camera Raw 14.3, applied lens corrections, Auto Settings in the Basic panel and default sharpening. The Camera Raw ‘Save’ panel was configured for full size, Quality ’12’ JPEG. A 2TB Samsung T5 USB-C SSD was used for the original and saved files. Using the T5 meant that the likelihood of the faster SSDs in the M1 Pro and Ultra helping the  SSD read / write times would not occur.

The averaged results from 4 tests on each computer are shown graphically below.

Camera Raw 14.3 – Comparison with GPU Acceleration Off / Auto

Taking the  Intel based i9 first, notice that enabling full GPU acceleration on the system has only marginally improved the time to save the files. Furthermore, the CPU and GPU were never even close to being maxed out. However, when GPU acceleration was disabled, the CPU was maxed out for the duration of the test. Therefore, in this instance, manually setting the GPU to full acceleration is of little benefit because the necessary VRAM is not available.

We can also see from above graph that the time to ‘save’ the 100 files as JPEGs on each of the M1 based systems is substantially better than the Intel i9 based based system. I suspect, had the Intel based system had the minimum requirement of 8GB of VRAM, then it would have performed much better. Would it have beaten the the Mac mini M1? I doubt it.

If we now consider how the Mac mini M1 performed we can see that it just manages to meet the minimum memory requirements for full GPU acceleration. Therefore, it doesn’t benefit to the same extent as the M1 Pro or Ultra from enabling full GPU acceleration. Even so, it’s 2.5 times faster at saving the files than the Intel i9 MacBook Pro.

The comparison between the M1 Pro and Ultra are where things get more interesting. The M1 Ultra has three times the number of GPU cores and double the number of CPU cores as the M1 Pro, yet the results are probably closer than the core count would suggest. Is the less than expected difference due to throttling or poor utilisation of the GPU? Not that I could see! In fact, during the GPU enabled tests, the GPU and CPU cores on each ranged between 80% and 100% throughout.  There was no sign of the M1 Pro maxing out the CPU or GPU for prolonged periods nor was there any indication that that the M1 Ultra was cruising along just enough to look busy. Based on what I was seeing throughout the tests, my guess is that there is scope for further optimisation, but not to the extent that would allow for the M1 Ultra being 3 times faster than the M1 Pro.

In closing, I think it important to note that the purpose of this blog post was to highlight the new enhanced GPU support in Camera Raw 14.3 and how each of the M1 based Macs used in the tests benefit from same. Hopefully, I’ve done enough to demonstrate that Adobe have at least started to optimise the performance of applications of interest to photographers using M1 Macs rather than simply port them from Intel x86 to Apple ARM 64 code. I’m also hopeful that we’ll see further improvements over the coming months, especially those of us who prefer Lightroom Classic to Camera Raw.

Update 22 April 2022

(*) I’ve also ran tests with 1000 EOS R5 files and found the same pattern of results to those for the lesser number of files. The important takeaway from the extended tests is that even after 30 minutes of near maximum CPU/GPU use, none of the systems throttled.

In below screenshot, I’ve shown Activity Monitor graphs for the M1 Ultra CPU and GPU at approximately 1/3 way through exporting 1000 EOS R5 files. The graphs demonstrate that both the CPU and GPU are well loaded during the export process.

Camera Raw, Lightroom Classic & Desktop | April 2022

  The latest updates to Lightroom Classic (11.3), Lightroom Desktop (5.3) and Camera Raw (14.3) have been released to customers. These updates include new camera and lens support plus bug fixes. There are also some feature and performance enhancements to Lightroom Classic.

Masking – Updates (Lightroom Classic)

ou can deselect a selected mask or component using the keyboard shortcut Cmd  / Ctrl + Click on the Masking panel. You can also use Option /Alt +directions keys to navigate the Masking panel list and loop around the last or the first mask.

Metadata – Performance Improvement (Lightroom Classic)

Adobe have worked on optimising the population of data in the Metadata panel. To achieve this, Lightroom Classic  will perform a one time optimisation task when the application is in idle idle mode. When optimisation is complete, you should see performance improvement in metadata population when a large number of images are selected (i.e.10’s of thousdands).

Map – Updates (Lightroom Classic)

There are changes to how Map module is initialised, which should improve map response time.

Preferences – Updates (Lightroom Classic)

Adobe have added an option in the Preference dialog ‘General’ tab to reset Preferences and relaunch Lightroom Classic. The button is only visible when you hold down the Option / Alt key.

Note that in addition to changing View Options back to default, resetting Preferences may also impact the Presets and Plugins settings, and thus require that they are reinstalled.

Print Module – Updates (Lightroom Classic)

The Print module on macOS has been updated to leverage OS native capabilities for drawing/rendering of Images. This change should also fix the issue of image being undersaturated when the Zoom to Fill option is selected.

Wacom Tablet – Updates (Lightroom Classic)

Some bug fixes and improvements related to Wacom tablet have been implemented in 11.3. These include:

  • Inverting stylus not erasing brush stroke has been fixed.
  • Pressure sensitivity enhancements (avoids the blotchy spots while drawing brush strokes).
  • Single brush stroke/dots which were previously not registered are now added to images.
  • Click and hold eye icon (to show/hide effect of a mask/colour grading) now works.
  • Stutter/delay in slider scrubbing – performance has been improved.
  • Delays/sluggishness in cropping the image has now been resolved.
  • Checking Windows ink used to make overall Wacom performance a little sluggish. Performance has now been improved.

Camera Raw Filter, Open and Save – Performance Improvement (Camera Raw)

GPU acceleration now speeds up save, open, and the Camera Raw filter. For supported GPUs, see the recommended GPU specifications for full acceleration in Camera Raw.

With supported GPUs, opening and saving files is enabled automatically by default when the Use Graphics Processor option in the Camera Raw Preferences is set to Auto.

  • Save: Using GPU for Save accelerates rendering for JPEG, TIFF, Photoshop, and PNG files. This is a batch processing operation that works on more than one photo at a time.
  • Open: When you are done editing and click the Open button to move to Photoshop, Camera Raw will use the GPU to render the main image opened.
  • Filter: When you are done using the Camera Raw Filter in Photoshop, Camera raw will use the GPU to render the result.

New Camera Support

Details of new camera support added since the last release can be found here

New Lens Correction Support

Details of new lens support added since the last release can be found here

Bug Fixes

Lightroom Classic bug fixes listed here

Lightroom Desktop bug fixes listed here

Camera Raw bug fixes listed here

Disclosure: As an Adobe Community Professional I receive a free subscription to Adobe Creative Cloud.

Adobe Lightroom Classic 8.4 & Camera Raw 11.4 | August 2019

The latest updates Adobe Lightroom Classic and Camera Raw were released to customers on  13 August. These updates focus on performance, workflow, support for new camera and lenses, and bug fixes.

The headline feature in this update to Lightroom Classic and Camera Raw is Graphics Processor Accelerated Editing. In particular, the ability to take greater advantage of features built into today’s more advanced graphics cards (GPUs) while editing your photos. Other new features to be found in Lightroom Classic 8.4 are: support for PNG export, colour labels in collections, batch merge of stacks for HDR, Panoramas and HDR Panoramas

Adobe Camera Raw 11.4

GPU Accelerated Editing

Adobe are advising customers that GPU support now includes the ability to improve interactive performance while processing photos. Hmm, I seem to recall reading something similar with Lightroom 6 then again with Lightroom 7. So, what’s new?

In previous versions, the GPU was used to accelerate the drawing or ‘display’ of pixels processed by the CPU, although many users felt that it fell short of doing so. With Lightroom Classic 8.4/ Camera Raw 11.4 the ‘image’ processing has been to the GPU Compute shaders. This means that the raw photo ‘processing pipe‘ has been ported to the GPU. As such, most of the image adjustments (e.g. Exposure, Contrast, White Balance, Clarity, Dehaze, etc ) can now be computed by the GPU rather than the CPU.

Typically, when ‘full’ acceleration is enabled you will notice that the adjustment sliders in Lightroom Classic and Camera Raw are smoother and more responsive. Additionally, the affects of ‘full’ acceleration will be more  pronounced when using higher resolution displays (i.e. 4k and above).

Update – 14 August 2019

A number of recent messages to Adobes Lightroom Classic User forum have confirmed that eGPUs are supported on the Mac platform, To enable  ‘Full GPU Acceleration’ the monitor needs to be connected to a Thunderbolt 3 port on the eGPU and the OS update to macOS Mojave 10.14.6, although earlier versions of Mojave might also work.

On Windows platform it’s important that the computer is running Windows 10 and that DirectX 12 is operational. Users should also ensure that they’re using the latest GPU driver, especially if its an nVidia card. 

The feature is enabled from within the Preferences dialog under the Performance tab in both Lightroom Classic and with Camera Raw.

When you access the Performance tab, you’ll immediately notice that the Graphic Processor segment now includes 3 dropdown options:

  1. Auto
  2. Custom
  3. Off

With ‘Auto’

Both Lightroom Classic 8.4 and Camera Raw 11.4 check the capabilities of the GPU upon first launch. If the GPU fails the test for any reason then GPU support will be set to Off.

Assuming your graphics card passes the test, is supported (i.e. not on the Adobe GPU Black List) and the operating system meets the minimum requirements, then ‘Auto’ will be enabled. However, the dialog may indicate that only ‘Basic’ acceleration is enabled. This is demonstrated in below screenshot from Camera Raw 11.4.

Camera Raw 11.4 – Performance Tab

This may be due to a number of reasons, but the most common are: the GPU has not been internally tested by Adobe engineers or the photos are ‘Process Version 4’ or earlier, but don’t despair just yet ‘Custom’ might yet come to the rescue.

With the ‘Custom’ option, you can select between the following options:

  1. Use GPU for display visualisation, which is same as GPU acceleration ‘ON as in earlier versions of Lightroom Classic and Camera Raw.
  2. Use GPU for image processing.

If you have ‘Use Graphics Processor set to ‘Auto’ and the text under the GPU name indicates ‘Your system automatically supports basic acceleration’ then, follow the following steps to enable Full Acceleration:

  1. Preferences > Performance Tab
  2. Select ‘Custom’ from ‘Use Graphics Processor’
  3. Check ‘Use GPU for image processing’ checkbox.

If your GPU supports full image processing, then the text under the GPU name will indicate ‘Full graphics acceleration is enabled’. This is demonstrated in below screenshot from Lightroom Classic 8.4

Lightroom Class – Performance Tab

If the text indicates that your GPU doesn’t support ‘full’ graphics acceleration, then at least you can still take advantage of  basic acceleration.

More information on GPU support in Lightroom Classic can be found at GPU Troubleshooting and FAQ

Colour Labels for Collections

Support for colour labels in folders was first introduced June 2018. With version 8.4 colour labels have been added to Collections, Smart Collections and Collection Sets.

Lightroom Classic 8.4 – Coloured Labels for Collections

  • To apply a Colour Label to a Collection, a Smart Collection, or a Collection Set, a new option has been added in the context menu as ‘Add Colour Label’.

Add Coloured Labels to Collection

  • To remove a colour label, select ‘None’ from the ‘Add Colour Label’ option.
  • Colour Labels now can also be added to Published Collections and collections inside Publish Services.
  • You can can also filter the Labeled Collections in the same way as Labeled Folders.

Filter Coloured Labels in Collection

Photo Merge – Support for merging multiple stacks

Photo merge now supports merging multiple selected stacks.

When you select multiple stacks for a merge operation (HDR/Pano/HDR-Pano), each stack will be merged individually with the selected merge operation. For example, if one selects 10 stacks for HDR merge operation, Lightroom Classic will initiate 10 HDR merge operations – one for each stack.

Photo Merge Multiple Stacks

Note:

  •  The same merge operation will be performed on all the stacks.
  • No preview will be shown if more than one stack is detected. Previous settings will be used as in case of a headless merge.
  • Non-stacked images will be ignored if stacks are detected in input images

Other Enhancements

Folder Enumeration Performance Improvements

With this build, Adobe have worked on the improving time taken for folder enumeration when Lightroom Classic is launched. This particular performance improvement depends on complexity of folder structure, but in most cases users should see a very obvious reduction in time taken to display the number of photos in a folder compared to that taken in previous versions.

Cloud Sync – Diagnostic Report

You are now able to generate a detailed Diagnostic Report for Sync in Lightroom Classic. This report is saved to a zip file with the catalog info, sync data and diagnostic logs required for Adobe QE to establish the cause of the sync issue.

To generate Diagnostic Report, in Preferences go to Lightroom Sync tab and press ALT/OPTIONkey to see “Generate Diagnostic Report” button

Cloud Sync Diagnostics Report

Filmstrip Index Number

It’s now possible to display the Index Number of a photo in the Filmstrip. This works like Index Numbers in Library Grid. On a scale of usefulness, I rate this about 100 (negative), but some users obviously thought it worthy of a feature request.

Filmstrip Index Number

In the flesh, the Index Number appears as shown in below screenshot. However, as the strip size is reduce there is a point at which the index number and the badges disappear.  Contrary to what some have claimed in the past, this is not a bug. It’s giving priority to the thumbnail (i.e. the photo) rather that some superfluous information that’s of little real value. Is it obvious that I think this feature was a waste of time?

Index Number in Filmstrip

Export as PNG

With this build, Adobe have added ability to Export as PNG. Save Transparency is always on.

Support for New Cameras & Lenses

For a full list of supported cameras and lens profiles for Lightroom desktop and Lightroom for mobile (iOS and Android), see these resources: