Is Lightroom Classic 7.0.1 Auto Import Corruption a bug?

[Pixelpaddler]

As a user of LR from its origin, and now running LR Classic 7.0.1, I am distressed to experience my first corruption related to Auto Import. I'm on a Mac running OS 10.11.6. Have been using Auto Import for several years to pull in images as I scan them with an Epson Perfection3200 Photo. Images scanned in this project are over 4000 so I've been using this feature for a while, love it when it is working.

Today, after scanning over ten other images that were imported automatically correctly, I returned to a destination folder used previously. After scanning an image, instead of it appearing in the destination folder, a copy of the previously scanned image appeared. The content is the previous image. The filename is the previous image. The index number is incremented and would be correct.

I checked the folder holding the actual image files. The new scan is there with its proper filename.

I changed the filename of the new duplicate image (which should have been the new image) but when I did that, the filename on the previous image also changed to match the name as I had changed it.

I optimized the catalog and received the confirmation upon its completion. The issue persists: I have two copies of one image - not marked as Virtual Copies are shown - and the newest scan does not appear.

I tried Synchronizing the folder. It showed - correctly - that one image needed to be imported. When I did so, I now have two improper copies of the image that had been the last one in the folder before the troubles began. Further, on the new, second duplicate, there is an icon where file location problems are shown, "Metadata for this photo has been changed ..." with the three buttons to import from disk, cancel or overwrite.

When I selected the second duplicate (the set: original, first duplicate, second duplicate), and Rejected it with an X, then Remove Photo from Catalog, all three versions of the image were removed. When I Synchronize the Folder, it correctly shows two images are present. However, then I did that import, problems expand: I now have an improper copy of the second previous scan, no copy of the previous scan and one of the newest scan.

My catalog has over 48000 images. I back it up every time I close LR. I have searched on "Auto Import" and find no other issues like this one.

This behavior is unacceptable. 

[PhilipDN]

I am running LR Classic 7.3.1 and have been scanning photo prints for some time now. I move the images from the watched folder to a new folder. Lately Auto import has started importing duplicates of previously imported images and not importing those that are in the watched folder. These are the exact same images and if I 'remove' them from the library of course all copies disappear. A manual import will bring in all the images.

I have had to stop using Auto Import and import in batches. This is actually not much of an inconvenience but it is annoying to not be able to use a useful feature.

[Sean McCormack]

Interesting. There was a similar duplicates bug that was fixed in an earlier version of 7, I wonder if there has been a regression. I'll attempt to recreate it shortly.

I'm sure you've already checked that your Auto Import settings haven't changed and that the watched folder is empty before enabling Auto Import.

[PhilipDN]

Sean, yep. I have a dedicated folder that is kept empty called "auto imported photos".

Oe thing that I was doing around the time this behaviour started was changing the file name of some of the images within LR. I use the file name as a date reference. Sometime I forget to change it in my scanning software. I don't see how this would cause Auto import to load a different file though. I will turn Auto back on and try some more without touching the file names.

[Sean McCormack]

It should be fine-unless you're adding illegal characters. I rename myself.

Try a completely different set of names (for watch and for destination) and see if it makes a difference.

[PhilipDN]

Found the trick. I have been 'Moving' all new scans to a particular folder -say "1980s" the odd one will not belong in that folder so I will then drag it to another folder. I did this just now from the 'Previous Import" smart folder and the next image I scanned did not load, instead the previous image re-loaded. I tried moving from the stored folder "1980s" with the same result.

The odd thing is that the Auto Import folder is empty so where is it getting the image from to re-load.

As I said earlier if I try to 'remove' the extra images it takes out all instances and I have to re-import them from the folders they were sent to.

Hopefully you can replicate this. I can avoid the issue by not moving any scanned images but that is a pain in the butt. Back to manually importing. 😞

[Sean McCormack]

Actually the bug was fixed in later versions of 7. Just saw the .0.1 bit.