Duplicate file names, but not actually duplicates getting "cleaned up".

[punchykat]

Due to me using Google Photos to be able to clear the photos on my phone once they were backed up, over the years a lot of my photos have the same name. Example: IMG_0051 appears as IMG_0051(1), IMG_0051 (2), IMG_0051 (3), as well as the "live photo" file with the same name for each corresponding photo.

During

Cleaning and Pairing Files
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ℹ️ Cleaning and pairing media files with JSONs...

It is deleting my photos in the output folder when it is renaming them to remove the numbers.

✅ Renamed JSON "S:\Organised\MetaSort_temp\IMG_0051.HEIC_2.json" to "S:\Organised\MetaSort_temp\IMG_0051.HEIC.json"
✅ Renamed JSON "S:\Organised\MetaSort_temp\IMG_0051.HEIC_3.json" to "S:\Organised\MetaSort_temp\IMG_0051.HEIC.json"
✅ Renamed JSON "S:\Organised\MetaSort_temp\IMG_0051.HEIC_4.json" to "S:\Organised\MetaSort_temp\IMG_0051.HEIC.json"

A lot of photos are therefore getting missed. Is there a way to prevent this?

[hensansi]

There is a way to prevent this. I'm not sure if I will push my changes to my fork, but if I do, will open a PR and then is just a matter of time until it gets merged. I recommend everyone keep a backup of the Google Takeout files because, besides this one, there could be potentially other data losses.

Edit: There are also some other forks that made it faster to process the files.