Lightroom Classic: Import Priority Options

  • 1
  • Idea
  • Updated 6 months ago
  • (Edited)
I'm curious, would importing large quantities of raw files be faster if LrClassic wasn't trying to render previews before the import was finished? I'm currently importing about 8,000 5DIV raws and it's going pretty slowly, since there's no way to tell LR to prioritize the import before preview rendering (which is set to Standard). 

I'd really like to see a few advanced features added which let users set priority functions, as well as CPU limits, since apparently the devs don't believe we should be using our machines for anything else while Lr is rendering previews or exporting...

Also, and i'll create another post for this, but Embedded and Sidecar appears to be broken again. It took nearly 10 years for this to be fixed the first time and now it's back to its old bad behavior. Those 8K raws i imported with Embedded as the preview, created 30GB of previews when it should have been 0MB.
Photo of eartho

eartho, Champion

  • 1530 Posts
  • 529 Reply Likes

Posted 6 months ago

  • 1
Photo of Bill

Bill

  • 294 Posts
  • 55 Reply Likes
  1. You don't have to wait for previews to finish before editing your images, tagging with keywords, etc. It will just keep creating the previews in the background. 
  2. Creation of previews can be disabled in preferences if you prefer. 
  3. While it doesn't completely eliminate the creation process, when importing, see File Handling. For Build Previews, choose Minimal. 
Photo of eartho

eartho, Champion

  • 1530 Posts
  • 529 Reply Likes
Thanks Bill. What i want is standard previews, but only after all the raws have finished importing. Just wondering if the ingestion process would be faster if the CPUs weren't maxing out while LR is trying to render previews at the same time. And we can't exactly apply keywords or other metadata updates until all the files have finished importing, which is why i'm asking about being able to prioritize... When i'm doing big ingestions and trying to get the ball rolling, i want to get everything imported, renamed, tagged, backed up immediately and then start culling after.
Photo of Bill

Bill

  • 294 Posts
  • 55 Reply Likes
Notice the progress bars at the top left. The import bar finishes long before it has finished creating previews. And YOU CAN apply keywords during the import process, I do it all the time. In terms of priorities, it does prioritize on imports, it just doesn't wait until the import is complete before creating previews. 
 
Perhaps you are using a slow computer, perhaps a laptop. Your finances are none of my business but using a fast desktop makes this much less painful: XEON processor with at least 4 memory lanes, 32GB of RAM minimum, dedicated SSD for Lightroom photos and catalog, separate SSD for Lightroom Preview Cache, all storage connected internally, not through USB or Thunderbolt ports... 
  
Photo of eartho

eartho, Champion

  • 1530 Posts
  • 529 Reply Likes
Thanks again, Bill. I'm working on highly optimized machine which is used for very large, high-end compositing/retouching work and has 128GB ram, NVMe, SSD and then another 40TB of hdd. I've been a Lightroom user since the v1 beta and was in PR up until v5. I'm very familiar with how it all operates =) Again, the question is, when importing large quantities of raw, would the initial ingestion be faster if preview rendering wasn't active? LR is very poorly optimized for multi-tasking and doesn't use a good priority system, at all. As an example, i needed to move a few thousand raws just now within LR, while the previews were rendering, and of course, it took way too long since LR's trying to do everything at once instead of prioritizing the move. And the only way to pause preview rendering is to cancel it, which means you have to select all and then re-render the whole batch...
Photo of Jeff

Jeff

  • 83 Posts
  • 20 Reply Likes
EDITED for location: There is a secret setting for this - hope I don't get in trouble here. You need to add a line to config.lua

Previews.DisableConcurrentWithImport = true

This file should be in the "Lightroom Settings" folder and might need to be created. It's just a text file. 

To locate the correct location for this file, Help > System Info. Scroll down until you see Settings Folder (typically %AppData%\Roaming\Adobe\Lightroom) and create the file there. Restart LR CC, then check in Help > System Info (scroll down a little) until you see Config.lua flags, should be below Installed Plugins.

(Edited)
Photo of eartho

eartho, Champion

  • 1529 Posts
  • 529 Reply Likes
beautiful, thank you Jeff! Sure would be nice if they added a slider or switch to the UI to activate or prioritize this function. And Adobe has been fine lately with sharing these text-file "hacks", so no worries there.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7714 Posts
  • 1778 Reply Likes
Just keep in mind when you choose to edit a config.lua file that you must remember that you've done this going forward. Many times weird behavior has been traced back to a previous config.lua entry that made sense at the time but no longer applies or trips something else.  
Photo of eartho

eartho, Champion

  • 1529 Posts
  • 529 Reply Likes
Understood, thanks Rikk. I sure do wish that we had a few additional controls in Lr for adjusting priorities and setting CPU limits. Trying to run LR exports, metadata saves, preview rendering, etc. while doing anything else with your computer is a very unpleasant experience. Many of us have jobs to do and limited hours to get the work done. Having to walk away from our machine while a big Export finishes is not great for the bottom line. I would really love to be able to continue doing my retouching work while LR exports, but it's not possible with the current CPU behavior... 
Photo of Bill

Bill

  • 290 Posts
  • 51 Reply Likes
Just ran an import test:
  • created a folder on my system NVMe drive with 3076 raw files, 42.3GB 
  • Lightroom Import (ADD) took 59 seconds
  • Standard Previews took 28 min 35 sec 
  • 6-core, 12-thread CPU ran at 100% busy the whole time: Xeon 3.6/4.0 GHz - see CPU busy chart below
  • scrolling the Library window would cause a short dip to about 50-80% of perhaps 1/4 sec
  • as soon as an image appeared in the Library view, I was able to Develop it
  • Developing was 2-4 times slower depending on the function
  • Keywords added without delay
Configuration: 
  • HP Z440 workstation with Windows 10 Pro, current updates 
  • XEON E5-1650 V4 
  • 64GB ECC ram
  • 512GB NVMe Samsung Pro on the PCIe bus for the OS and program libraries, no data except the folder for this test
  • 2TB Samsung EVO on the PCIe bus for the Lightroom library and catalog
  • 1TB Samsung EVO SATA drive on the SATA bus for the Lightroom Preview Cache
  • 2 other SSDs and 2 Hard Drives not in use by Lightroom
  • Nvidia QUADRO K1200 driving two 4K monitors, fresh update of the driver  
Bill