Skip to main content
Adobe Photoshop Family

26 Messages

 • 

426 Points

Thu, Jul 23, 2020 10:29 AM

Lightroom Classic: Dandoff to Photoshop is very slow

I'm trying to discover why it takes so long to open a NEF from Lightroom Classic into Photoshop i.e. "Edit in Adobe Photoshop", which takes around 18-20 seconds, even if Photoshop is already open. Up to about a year ago it was only about half that time.

The timing is pretty much the same for full sized RAW images from D800/D850/Z7.

If I export and create a full-sized JPG copy of the NEF into the LR catalog, then open that in PS, it opens in about two seconds. The conclusion, therefore, is that the extra time is concerned with the creation of the TIFF/PSD file (almost no difference in timing whichever I use) and Camera Raw processing.

Here are some things which you may ask...
Windows 10 latest version 64bit; 32Gb memory
CPU Intel i7-8700k 3.7Ghz
GPU is Nvidia GeForce GTX 1650 super 4Gb
GPU is activated in LR/PS Performance option
Latest versions of all Adobe apps and Camera Raw: The software is on an SSD
LR catalog and previews are on an SSD
LR and Photoshop scratch areas are on an SSD
Image files are on an SSD (though the difference if they are on my NAS is only about 1 second)
Opening the same NEFs from Bridge also take about 18 seconds.

Once I have edited a NEF in PS and returned to LR, I can go back to the new PSD version in PS in about 4 seconds.

I've tried with/without using presets, 8/16 bit, and with/without just about everything else I can think of. I've tried searching for a solution on Google to no avail.

Here's a screenshot from Task Manager, annotated with the key milestones.


Thanks for any suggestions.

Geoff

Responses

248 Messages

 • 

6.2K Points

2 months ago

Hi Geoff - out of interest - if you create a one-layer smart layer of the raw file and save that as a PSD does that also open fast?  

26 Messages

 • 

426 Points

2 months ago

Yes, in about 3 seconds.

26 Messages

 • 

426 Points

2 months ago

I knew that a RAW file without any adjustments would open in PS in half the time that it would otherwise and after exhaustive check-box checking/unchecking I concluded that PS was pondering over the adjustments before getting on with opening the file. I therefore decided to see if the delay was setting specific: it is!

My unadjusted reference image opens from LR to PS in 10 seconds.

Here are the worst culprits which push that time up to 21 seconds:
Highlights
Shadows
Clarity
B&W

Even the slightest adjustment will do it (e.g. +1 on Highlights)

Here are the second worst culprits that push the time to 15 seconds
Dehaze
Adjustment Brush


Anything else in the LR panels I can alter as much as I like and the opening time stays at 10 seconds.

My question to Adobe is, therefore, why the processing of these adjustments isn't using more CPU power than at present, which as you can see from the above graph, is only just over 10%.

Champion

 • 

2.1K Messages

 • 

36.3K Points

2 months ago

I have a similar system and seeing 4.0 sec. with 21 mp Canon 5D MKII CR2 files and 6.0 sec. for Nikon D850 45.7 mp NEF file Edit in PS time to open. (See LR settings below)

After updating to Camera Raw 12.3 I discovered Preferences in Bridge for Performance> 'Use GPU for Image Processing' was grayed out and not selectable.  Check your system and if not selectable reintsall ACR 12.3 as outlined at the below link. Once 12.3 is reintsalled you should be able to check both Performance options as shown below.

https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-in-installer.html









26 Messages

 • 

426 Points

Hi Todd, the GPU was enabled in LR, PS and Br but I reinstalled ACR anyway, but no change. I noticed, however, that although we have identical CPUs, your Task Manager info showed Virtualisation as Enabled, whereas mine was Disabled. After a bit of Googling, I was able to enable it in the BIOS. D'oh! No change in Lr to PS speed.

Any further suggestions would be welcomed.

Thanks, Geoff

Champion

 • 

2.1K Messages

 • 

36.3K Points

2 months ago

Some other things to try:
1) Check that all of your drives have at least 50 GB free space.

2) Check your Camera Raw Cache folder size and set it in LR Preferences> Performance to 2x that size. Mine is about 50 GB and I have it set for 100 GB.

3) Try resetting PS Preferences file by renaming it with a .OLD extension or move it to your desktop. That way you can easily restore if of no help. Restart PS and it will create a new default settings Preferences file.

C:\Users\USERNAME\AppData\Roaming\Adobe\Adobe Photoshop 2020\Adobe Photoshop 2020 Settings\Adobe Photoshop 2020 Prefs.psp.OLD

4) Uninstall and then reinstall PS 21.2.1 using the CC app.

26 Messages

 • 

426 Points

2 months ago

I tried those Todd.
1.  80Gb free on the system drive, over 500Gb free on the others (all SSDs).
2. Camera Raw Cache is set to 200GB.
3. No difference with default settings.
4. Still no change.

Geoff

Champion

 • 

2.1K Messages

 • 

36.3K Points

2 months ago

1) Shutdown you system, turn the power off, remove ALL USB connected drives and devices except mouse and keyboard, wait 10 sec., and power back up. Try again.

2) Temporarily disable your firewall, antivirus, and any other malware programs you have running. Try again.

If the delay persists export one of the NEF files to DNG file format with your LR settings applied. Confirm the DNG file also exhibits the same slow open using Edit in PS. Upload the DNG file to Dropbox or other file sharing site, paste the share link here, and I'll check it on my similar system.

26 Messages

 • 

426 Points

2 months ago

Thanks Todd. I'll try that too but I'm pushed for time now so it won't be until tomorrow afternoon (UK time).

26 Messages

 • 

426 Points

2 months ago

Todd, 1 and 2 made no difference.

Here's the difference between a NEF transfer and DNG:


So here's a Dropbox link to the two files and also an XMP produced from LR after a few edits have been applied. https://www.dropbox.com/sh/d84l230l95aeix8/AACLXHEcTH823KowJRYfwOFGa?dl=0

Geoff

Champion

 • 

2.1K Messages

 • 

36.3K Points

2 months ago

1) In Task Manager I'm seeing about 8.0 sec. to open your NEF file in PS. In the1st screenshot below the arrows show actual Edit in PS start (CTRL +E keys) and when image opens in PS. I measured 8.0 secs using a stopwatch. Notice the initial lower level of CPU activity in your screenshot isn't present on my similar system. PS was already open in your screenshot, correct?

2) In the 2nd screenshot below notice it's showing 100% Utilization and 4.29 GHz. Turbo Clock Speed. Check your system.

3) Also try Resource Monitor as shown below. On my system all 12 virtual cores are working at the same level throughout the Edit in PS opening process. Check your system.

Just trying to determine why your similar i7-8700K system is behaving differently.

(Performance Monitor Normal Setting = 4.0 sec. per division)



26 Messages

 • 

426 Points

2 months ago

1. Yes, PS was already open for my timings. In my Performance monitor, each division is definitely 3 seconds.

2. Only one screenshot was attached, but at peak activity (shown here) I have 4.29GHz too.


3. When PS gets to the "Reading Camera Raw format" stage, all 12 cores are working at max. Before that, only CPU 1 seems to be working hard on something (marked here from "Open in PS" in LR to seeing the image on screen in PS)


The confusing thing is that if I'm processing an image with no LR import of Develop changes, I see almost no 'preamble' before ACR kicks in. Here's the same image having Reset in the Develop module, so it's clearly something to do with the adjustments, but why the lag on my system but not on others.


A couple of friends have also processed the image and see similar performance to your system.

Geoff

26 Messages

 • 

426 Points

2 months ago

Todd, Here are my key PS preferences. I have tried activating/deactivating everything that seemed likely to affect performance.

Champion

 • 

2.1K Messages

 • 

36.3K Points

a month ago

Your settings are the same as mine. I can confirm with the Develop settings reset to defaults (0) it's faster (4 sec vs 8 sec.). What we haven't tried is to 1) reset LR Preferences and then 2) a LR reinstall.


1) Close LR and rename the Lightroom Classic CC 7 Preferences.agprefs as shown below so you can restore when we're done with this test. Try Edit in PS again. If still the same go to step #2 below.


C:\Users\USERNAME\AppData\Roaming\Adobe\Lightroom\Preferences\Lightroom Classic CC 7 Preferences.agprefs.OLD

2) With the new default settings Preferences still in place use the CC app to uninstall LR 9.3 and then reinstall 9.3. Try again.


3) If still no joy I suggest running a system performance test. PassMark's Performance Test is good and has a free 30 day trial here:


https://www.passmark.com/products/performancetest/download.php

Champion

 • 

2.1K Messages

 • 

36.3K Points

a month ago

I think I may have found what's causing the longer Edit in PS time. I checked your profile trying to determine what resolution display(s) you're using and found this post:

https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-9-2-lr-will-not-sync-file-s...

It appears you're storing your image files on a QNAP NAS drive. Create a folder with some NEFs on one of your local SSD system drives and see if the Edit in PS times are better.

26 Messages

 • 

426 Points

a month ago

Hi Todd, I still have that situation if I import to a new folder on the NAS, which is caused by Windows not being consistent in its path naming, so I may have a folder in LR called QNAP/Pictures/... but if Windows gives qnap/Pictures... when selected in the import dialog LR assumes its a different folder. I recently had a couple of SSDs installed, so now I always import to a folder "Lightroom new import area" on an SSD and do initial PP there, then drag the keepers to the desired NAS folder.

Anyway, doing the LR to PS switch with a file that is resident on the NAS makes no noticeable difference in time to get into PS. As a check, I ran a test last week with an SSD based image and with the network disconnected to make sure that PS wasn't trying to get back to the NAS for some reason.

As for your latest suggestions above, (1) No change. (2) I did that and for good measure also reset PS preferences and reinstalled that too. No change.

Here's the headline Performance Test result:

I wonder how that compares to your CPU.

If/when you ran out of ideas I was thinking of calling the PC manufacturer's (Chillblast) tech support team who are knowledgeable about LR and PS to see if they could come up with anything. I'm beginning to think that there could be a hardware/BIOS issue.

Geoff