P: Import is creating OS - level duplicate files named (-2) when using Devices rather than Files

11 Votes
Community Beginner ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

Since I upgraded to lightroom classic from lightroom 5.7.1, imports are now importing duplicate images, even though I have checked don't import suspected duplicates. It happens on both my nikon and canon camera images.

Bug Acknowledged
TOPICS
macOS

Views

3.6K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Employee , Jun 15, 2022 Jun 15, 2022
We have a fix for this in the next update - unfortunately, it was too late to make it into this week's release.  Note: this is not specific to Fuji. I can reproduce with Canon as well. 
Status Acknowledged

Votes

Translate

Translate
Adobe Employee , May 20, 2022 May 20, 2022
Opened new bug for investigation. Issue is still not reproducible save very sporadically. In months of attempting to reproduce, it has only happened to me once and was not repeatable.  Previous bug was only partially related to this failure. 
Status Started

Votes

Translate

Translate
replies 144 Replies 144
144 Comments
Adobe Community Professional ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

Are these newly captured photos? Or ones that have been on the card for a long time?
-------------------------------------
The Lightroom Queen - Author of the Lightroom Missing FAQ & Edit Like a Pro books.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

These are new photos and some older ones (maybe a few weeks). It seems to just randomly import images that have already been imported....and the thing is I know it is recognizing the duplicates because it renames the files with a '-2' on the end of the filename.

Votes

Translate

Translate

Report

Report
Participant ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

I'm probably out of date as I no longer use this feature but a suspected duplicate had to match the capture date and file name exactly. Not sure how it happens but copying files between folders can sometimes change the capture date. Because the file name is identical, a suffix must be added as 2 files with the same name cannot exist in the same folder. But something else is enough different that it does not treat them as the same image.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

The exact criteria for Classic is  File Size/Filename/Capture Date. If all three match it is a duplicate. If they do not it is not treated thusly. If you rename when importing this will make the duplicate check fail on Filename.

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Participant ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

He said that he is getting -2 added to the file name so we know that is matching.

Windows only comment: on Windows there are 2 sizes for a file. 1) actual size; 2) size on disk. Moving the file won't change the actual size but the size on disk is affected by both the disk technology (SSD vs HD...) and how it was formatted.

Perhaps Lightroom is checking the latter size?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

OS?
Is the drive formatted as Case-sensitive?
Screenshots of the Folder/Import Dialog?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied

Windows 10...I wonder if it has to do with windows not being able to read .CR2 data. (I just switched over to a Canon 6d mark ii from a nikon d3300). I noticed that in addition to thumbnails not being displayed for cr2 files, in windows explorer|file properties|details  all the camera fields are blank...so 'date taken' etc are all blank. But I would assume that wouldn't affect lightrooms ability to read and compare that data, which I assume exists in the raw file even though windows doesn't display it...

Btw, I think I figured out why the Nikon files imported again...I used to convert to .dng, but now with the new Canon I am just copying the raw files, so when I imported this morning it makes sense that it made new copies of the photos since they were NEF and not DNG. HOWEVER...the import was only partial, and I did a couple of imports of my Nikon card, and each time it only imported a subset of all the files that could be imported. So why is that? Why wouldn't it import all the files on the card again, instead of spreading out over 2 different imports? That is really weird. Anyways, so it is apparently just the Canon .CR2 files that are getting duplicated with the filename being appended with a '-2'.

Also, thanks for all your responses, I will do some more digging here as well...


Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 22, 2020 Jun 22, 2020

Copy link to clipboard

Copied



Votes

Translate

Translate

Report

Report
New Here ,
Jul 02, 2020 Jul 02, 2020

Copy link to clipboard

Copied

Hi! Same problem over here!!

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 02, 2020 Jul 02, 2020

Copy link to clipboard

Copied

The work around for me *seems* to be to let lightroom show all the previews first, before hitting the final import button. It's annoyingly time consuming, but so far I haven't had the issue since I started doing that.

Votes

Translate

Translate

Report

Report
New Here ,
Jul 04, 2020 Jul 04, 2020

Copy link to clipboard

Copied

Thanks for the tip. This occurs since the last update.... pretty annoying.

Votes

Translate

Translate

Report

Report
New Here ,
Jul 04, 2020 Jul 04, 2020

Copy link to clipboard

Copied

Same problem here, with MacOS Catalina, since the last LR update 9.3 june 2020 ( with .NEF files reading from a card reader )

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 14, 2020 Jul 14, 2020

Copy link to clipboard

Copied

We've logged a bug for this issue. Follow this thread for updates when this is fixed. 
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 20, 2020 Oct 20, 2020

Copy link to clipboard

Copied

Greetings,

 

Updates for the Adobe Photography Products were released on 10.20.2020 that include fixes for these issues. Please install the most recent update and confirm that your issue is now fixed. Please let us know if you encounter any issues.

 

Thank you for your patience.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

@Rick 

I'm still having this issue. I have the most-recent version of lightroom classic installed.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

Me too, it's driving me crazy, is there any way to quickly identify and delete the duplicates while we wait for a fix?

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 15, 2020 Nov 15, 2020

Copy link to clipboard

Copied

I have the same problem . Importing file after update is creating 2 files for the same picture . It’s making a duplicate!!!! What the heck!!! Imagine when you import 3000 pictures 

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 15, 2020 Nov 15, 2020

Copy link to clipboard

Copied

Same problem for me after updating last version!!!

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 15, 2020 Nov 15, 2020

Copy link to clipboard

Copied

@Rick

Not to pile on, but I'm also having the same issue as decribed here. It started with the version that introduced the Hue slider to the local adjustments (9.3?) at the time I checked with support and their solution was for me to downgrade and wait for an update to resolve the issue. Now I'm on ver. 10 of Classic (and Creative Cloud says I'm up to date) and I'm still having the same issue. On import, LRC displays both the RAW and sidecar jpeg files and imports both. I have the setting to NOT treat the jpegs as separate files. Following the advice of Support the last time, I uninstalled and reinstalled. Fixed the problem for only one import. Then back to the same problem. What's going on? HOW to fix? Permanently. This is annoying now.

 

Votes

Translate

Translate

Report

Report
New Here ,
Nov 28, 2020 Nov 28, 2020

Copy link to clipboard

Copied

Does anyone know if there is a fix yet 

Votes

Translate

Translate

Report

Report
New Here ,
Nov 28, 2020 Nov 28, 2020

Copy link to clipboard

Copied

4 months since you posted this surely you have a fix by now

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 29, 2020 Nov 29, 2020

Copy link to clipboard

Copied

This was fixed in October with the release of 10.0
Are you using this release?

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Participant ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

@Rikk , I have used the Rename file function for years, to avoid duplicate file names. Many cameras start file naming over for every 10000 images (_DSC1234 og DSC_1234). 
Lightroom Classic and predecessors have always treated duplicates reliably for me. I appreciate this function so much.

I have experienced significant problems with duplicate file names when helping people locate missing/offline photographs in catalog. I am running a Norwegian user support group with 7000 members.

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 05, 2020 Dec 05, 2020

Copy link to clipboard

Copied

This has not been fixed.  I'm using the 10.0 version and this has happened to me twice this week.  Just moments ago, in fact.  

Votes

Translate

Translate

Report

Report
Participant ,
Dec 05, 2020 Dec 05, 2020

Copy link to clipboard

Copied

Bjorn_B,

 

Did you see Rikk's comment regarding whether the drive was formatted as "case sensitive"? Only applies to MacOS or running a virtual instance of Windows under Linux. 

Votes

Translate

Translate

Report

Report