Skip to main content
D
DavePinMinn
Inspiring
May 24, 2018
Question

Import failed and left a few HUNDRED temp folders

  • May 24, 2018
  • 1 reply
  • 805 views

I almost never import directly from memory cards into Lightroom.  But, today I THOUGHT I'd make life easier and copy 628 images from the XQD card, directly into Lightroom 7.3.1 with a rename... 

I went out and rummaged to see what was going on and it turns out I can be added to those who've "complained" as was said in the Lightroom Queen forum...

Ordinary PC laptop, Windows 10, Lightroom 7.3.1, Nvidia GTX 970, 16 GB memory.  Ordinary laptop...  Images are 628 images from a Nikon D850, shot as RAW.  Very ordinary images.

Told Lightroom to import them the 40GB or so of images, copy to a folder on a drive with over a Terabyte of free space, and rename them.  Off it went.  And churned...  For a little over THREE HOURS.  Came back, LR is greyed out and not responsive.  Just sitting there using 5GB of memory and 30% of the CPU, and NOTHING is happening.  Waited so minutes and it's STILL on the same image - no new images showing up in the folder.  TempParent folder contains hundreds of child folders, each with ONE image in it.

After another HOUR without a single additional image being added (now makes it 4 1/2 hours), I killed Lightroom and restarted it.  And a couple unpleasant new things happened:  1:  It didn't change the Start Number for the import, so it started importing the previously unimported images using the same sequence number previously used with a -2 on it.  Not useful.  2:  I figured this out after about a dozen images and cancelled the import.  Reopened the import, changed the Starting Number, and expected it to grab the remaining 200+ images.  Nope.  I showed all 628 images again, and when the import restarted, it started putting all 600+ images in the folder with a different rename.  Even less useful than importing the remaining 200+ images that needed importing.

I've now emptied the incoming folder and I'm back to copying the images as they came from the camera into a folder OUTSIDE Lightroom.  Once they're there, I'll import them WITHOUT renaming, then do all the initial culling, then EVENTUALLY just do a rename on the remainder...  Which is the less efficient, but at least successful, process I've used in the past.

COPYING the 600+ images from memory card to hard drive took fewer than 20 minutes and nothing hung.

Was this the intended behavior?

    This topic has been closed for replies.

    1 reply

    JP Hess
    JP Hess
    Inspiring
    May 24, 2018

    Sounds like some really strange behavior, for sure. I have encountered some problems with importing directly from a SD recently, and it appears that it is a problem that has been confirmed by Adobe. While they are working to resolve the issue, I have resorted to copying images to a folder on my hard drive using File Explorer first, and then importing into Lightroom using the Add option. I don't know if the behavior you encountered is specifically related, but you might trying the same procedure.

    D
    DavePinMinnAuthor
    Inspiring
    May 25, 2018

    So at some undetermined time in the future are we now going to get 7.3.1.1 or 7.3.2 to fix all the stuff they broke in 7.3 and didn't fix in 7.3.1 or broke in 7.3.1 to fix the mess that apparently was 7.3?

    Good grief, this is just getting sad.

    Fortunately, I'm at the age where I"m largely doing this for fun - I generate revenue, but I don't have to make a living relying on Lightroom.  What are y'all who HAVE to actually create high quality output, fast, in the most efficient environment possible doing?

    No wonder they're pushing the snot out of Luminar as an alternative (unfortunately, I've tried it, s'not a great alternative - Yet).

    JP Hess
    JP Hess
    Inspiring
    May 25, 2018

    When dealing with multiple operating systems, and issuing multiple updates every year, it's inevitable that unforeseen issues will develop. I outlined what I consider to be a reasonable solution until this problem is resolved. If you can't deal with that kind of a solution then maybe you can switch to another software and deal with the issues that will inevitably be encountered with it.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices