Skip to main content
Inspiring
February 28, 2022
Question

Problems with synchronizing, duplicates and renaming

  • February 28, 2022
  • 3 replies
  • 964 views

Same HUGE mess of umpteen folders, but three NEW bizarre problems...  I need a really good answer that'll get this working...

I've got a setup now with year folders from 2006 to 2022, holding around 30,000 images.  Now we've get to get all the OTHER folders imported into the years.

 

PROBLEM 1

This morning, doing a Synchronize Folders showed X number of images import.  Clicked the show import dialogue and started the sync.  It did the metadata update, then should have opened the import dialogue.  Instead a partial spinning circle where the folders were, that stopped after half a rotation, and the normal “busy” rotating circle for the curso.  Never opened, never finished, just hung.  Crashed LR, retried a couple times.

And YEAH, since I KNEW the first thing somebody in here would say was “delete the preferences” I did.  Other than screwing up most things that were configured it did NOTHING.

 

Tried again on a different folder.  Worked FINE.

Tried another folder, got the same thing - no import dialogue, hung Lightroom, had to crash it.

 

If I DON’T tell it to display the import dialogue, it proceeds to import the images just fine.

Doesn’t seem to matter if it’s three images to import or 500, almost all the time, it hangs Lightroom.

That’s problem ONE.

 

PROBLEM 2

As I understand it, Lightroom thinks every image in the entire catalog will be unique.  HOW does it decide what “unique” is?  Is it JUST the filename?  Is it the filename and date?  PART of the filename?  Something else?  'Cause it's NOT working currently using the filename...

 

In this catalog, there are MULTIPLE occurrences of a filename.  They shoot Sony so the filename is something like DSC1234.ARW, and this image in the 2016 folder.  You import another bunch of images, and there’s a DSC1234.ARW going in the 2020 folder.  They’re NOT the same image, they're YEARS apart, but they have the same name.

 

HOW do NORMAL people handle this – people that DON’T rename every image they shoot?  In this system there are often at least THREE images with the same name in different years.

 

What’s BEEN happening is we find one of the umpteen folders of images and import it into the correct year.  BUT, a bunch of images fall OUT because they’re duplicates.  The “don’t import duplicates” gets turned OFF because they’re NOT duplicates, they’re DIFFERENT images with the same filename but years apart in the capture date.

So HOW do y’all handle the problem – rename every image?  Something else?  And how do NORMAL people without the expertise in here do it?  'Cause I don't see the people I'm helping having ANY clue about renaming images on import...

 

PROBLEM 3

In THIS case, I have a bunch of images that actually ARE duplicates going into the 2008 folder – it’s a very SMALL folder of 8 images, so it’s perfect to experiment on.  I elected to rename the images, which is where the NEXT problem showed up.

I created a preset to put a six-digit year (YYMMDD) on the front of the filename, followed by an underscore then the “Original Number Suffix”.  When I used this on one of these Sony images, DSC12345.? Instead of getting 161013_12345.jpg or ARW or psd, I got 161013_2.jpg or whatever.  EVERY TIME.  I absolutely CANNOT get Lightroom to use the original filename OR THE “Filename Number Sequence” - it will NOT put the number from the filename into the renamed image.  What I FINALLY did was use the WHOLE filename.  So, the rename is 161013_DSC12345.jpg.  Which works, but it’s ugly and longer than needed.  But I haven’t been able to get anything ELSE to work.

 

NOW comes the REAL fun.  In the 2008 folder of 8 images I have DSC12345.ARW.  In the 2020 folder I ALSO have DSC12345.ARW.  Same EXACT name, 4 years apart.  I attempted to IMPORT a DSC12345.ARW that matches the one in 2008 – it’s the same image.  It IS a duplicate.  Lightroom removed it from the import display as it should.

I RENAMED the 8 images in the 2008 folder so they looked like 080512_DSC12345.ARW.  I tried the import AGAIN.  And again, Lightroom said I had a duplicate – I PRESUME this time it was complaining about the one in the 2020 folder.  I renamed the DSC12345.ARW in the 2020 folder to 200419_DSC12345.ARW and a check of the ENTIRE catalog shows NO OTHER IMAGES WITH  DSC12345 ANYWHERE IN A FILENAME.  So importing an image named DSC12345 SHOULDN’T have a problem – RIGHT?

It does.  Lightroom STILL turn the image off EVEN THOUGH there’s NO duplicate filename in this catalog.

WHY ISN’T THIS WORKING?  Does the import object to a PARTIAL match on the same date?  What IS it doing?  The whole point of doing this is so we can be SURE when an image is shown as a duplicate that it actually IS a duplicate.

How DO I get this to work?

3 replies

New Participant
September 27, 2025

I started using LR sync a month ago and bumped into the same issue and I hate it, cause messes up with my photos, dates and metadata, also ruins the entire point of syncing catalogues between devices 

 

It's been 3 years but the issue is not fixed

GoldingD
Brainiac
March 3, 2022

One question:

Those photos in those folders you want moved, were they already in the catalog? I ask this as importing would not be the normal process. if they had already been imported.

 

One comment

I for one, rename my photos at import, I use the syntax YYYMMDD_hhmmss. This eliminates any issues of identical names, and allows a cleaner sort. (note, LrC will add a suffix in case of photos shot in the same second).

Personally I absolutely hate using date specific folders, but that is my workflow.

 

Inspiring
March 4, 2022

No.  There were dozens of folders with images in them.  The user said they ORIGINALLY started in Lightroom, had so much trouble they quit, and switched to Bridge.  They ended up with dozens of folders of images on TWO different hard drives.  The user insists they have NO idea how they GOT all these folders with MANY MANY duplicates.  So far, we've managed to get about 42,000 images into Lightroom from these random folders,  I was able to START with a couple folders that Lightroom still had, but there was NO metadata ever saved, so all the metadata that's available is in images from Bridge.

Today I found another 109 (yes a hundred and 9) additional folders of images buried in a folder called 2020 inside inside a folder called "landscape backup".  Those contain another 860 GB of image files. There wasn't a lot of organization.

 

As for serial numbers, the user's Library Filter metadata showed at LEAST 10 cameras.  Every Canon, and Fuji, and Nikon showed a serial number.  The three Sony's - BLANK.  In the Metadata panel, everybody has a serial number.  Except the Sony's.

Sean McCormack
Community Expert
March 4, 2022

That sounds like a world of pain Dave. 

 

If there's no camera serial metadata, it's gonna be pretty hard to separate them. If force a Read Metadata from file on a random file, does it update? I'm gonna assume that the serial number is actually in the metadata somewhere, just not where Lightroom is expecting it to be. Maybe try Jeffrey's EXIF Viewer: http://exif.regex.info/exif.cgi 

It may give you an alternative field to filter on. 

 

One suggestion on getting stuff where you want it to be: 

 

Save out the metadata for sets of files. Use delete and select the Remove option to get them out of Lightroom. Then import them again, setting your own destination and using the Move option to reposition them on disk.

 

 

Sean McCormack. Author of 'Essential Development 3'. Magazine Writer. Former Official Fuji X-Photographer.
Sean McCormack
Community Expert
February 28, 2022

Don't import suspected duplicates used to be filename, capture time and file size from what I remember. If any of these are different, it will fail. 

 

If a particular change causes a fail, it makes sense to just not to do that. I've seen where Lightroom loses the suffix on edits, on it's rather annoying. I'd suggest not using the date rename until you at least have the suffix established. Also use - instead of _. The - reads as a space online so if you use custom names, it's searchable. 

 

I rename every image on Import. It's a sticky setting and means every image has a unique name. Date-Custom Text-Original Filename Suffix. It may be that your lack of text inclusion is what's confusing detection of the suffix. 

 

 

 

 

Sean McCormack. Author of 'Essential Development 3'. Magazine Writer. Former Official Fuji X-Photographer.
Inspiring
February 28, 2022

Yes, in the SAME folder it appears Lightroom uses all those - and maybe pixel dimensions, I'm not sure.

In DIFFERENT folders I'm not sure what it uses if you try to import a duplicate.  BUT, you can turn off suspected duplicates and it'll happily import and once it's in, Lightroom doesn't care.  Not even synchronize folders picks it up as near as I can tell.

It's turning out there are a LOT of ways to screw up Lightroom if you do things wrong.  And if your Lightroom catalog somehow got completely messed up and you just switched to Bridge for a few years, it looks like EVERYTHING is wrong!

Thanks for the idea about the "-" instead of the "_". 

Like you, I rename every image on it's way into Lightroom using a YYMMDD_<4-digit-sequence>, and that's always helped keep me from doing anything DISASTROUSLY stupid.

BTW:  As far as renaming, I tested a couple images from different Nikon cameras this morning.  They renamed perfectly, pulling the camera's sequence number off the text.  No problem at all.  I ALSO tried an image from an Olympus - this one looked like _1234567.ORF and it too renamed perfectly, becoming 200813_2134567.ORF.  The ONLY camera I've seen so far where it DIDN'T work was the Sony I'm dealing with.  I don't know if it's ALL Sony cameras or what.  BUT, renaming with the date and the WHOLE filename does work.

Brainiac
February 28, 2022

Yes, in the SAME folder it appears Lightroom uses all those - and maybe pixel dimensions, I'm not sure.

In DIFFERENT folders I'm not sure what it uses if you try to import a duplicate.


The documentation is clear about what it uses, and @Sean McCormack has stated it clearly. It applies across all photos that have been imported, in any folder, same rules apply whether you are talking about one folder or different folders. Having said that, I suspect this is a buggy operation, as over the years people have complained that it isn't working properly.