Meanwhile, my scan at 90% similarity just finished and it found 2 pairs of duplicates and is one, MAH00637 (1).MP4.modd and MAH00638 (1).MP4.modd is the other. (Duplicate Cleaner Pro found and deleted all the ones that were duplicated by PlayMemories Home that were also duplicated by PhotoStack.) Here's the link: The two originals were imported by Sony Picture Motion Browser. The first pair (DSC00024) is the one I checked with WinMerge, and the extra one was caused by importing with Serif PhotoStack the 2nd pair (DSC01828) is a more recent one, and was caused by importing with Sony PlayMemories Home. Okay, I uploaded 2 pairs of duplicates to OneDrive. ![]() Let me see if I can use Dropbox or OneDrive. I can crop them or change the resolution or re-compress them, but that might also change whatever is different between them too. I have a 16 megapixel camera that makes ~5 MB files. I can't upload the files, they're too big. I'm running another one again now in case I only did that with an image scan instead of a regular one. If I find what the difference is, how would I incorporate that into a Duplicate Cleaner Pro scan anyway? I've already run a scan previously with a lower percentage of difference, and when I lowered it enough to get duplicates (I forget the exact percentage), I wound up with non-duplicates that were considered duplicates, but none of the actual duplicates I was looking for. But WinMerge doesn't seem to be geared toward binary files, so I'm not sure how useful that was. One of the two photos had some kind of Adobe path listed (I think a web address, rather than a folder path), possibly appended onto the EXIF data. ![]() WinMerge found 3 differences between the two photos I loaded in it 2 of the differences didn't show up in the differences section, but the third was a difference in text. DiffImg wouldn't run on my Windows 8.1 system VisiPics wouldn't find any duplicates. Tried the last suggestion from DigitalVolcano (unchecking "Don't scan system files/folders"). These files should have the same EXIF data I don't suppose there's any way to include that as a criterion? I use FreeFileSync to sync my photos to my server and then to my laptop could that be writing something to them? *Edit: Also, File History backs them up could it be an archive flag of some sort? So I successfully deleted the newer set of duplicates. So I downloaded the newer one and used it, and it clearly has the option to import only new photos-but apparently it has a database or something to remember them, because it also downloaded every photo over again, leaving me with another set of duplicates that had " (1)" added to the filenames.ĭuplicate Cleaner Pro found all the duplicates (in Image Mode with 99% similarity, which was the first scan I tried) with the extra numbers, but still didn't find the original photos that were already on the drive before either import. After doing some reading, I determined that the program may well be incapable of importing only new images as opposed to all the images on the card, so I went back to my original program (which came with the camera)-only to find that it was being discontinued in favor of a newer one. The first program that produced the duplicates was one I had never before used to import photos, so it seems perfectly reasonable that either it or my previous one or both added something to the photos on import. (I did find that the Date Taken was one second different between one of the pairs, but that shouldn't make as much of a size difference as there is between them.) What can I use to find out the differences between my files? The metadata I can see in Windows and my importing programs don't show me anything that looks relevant. Then I remembered that Image Mode existed and tried that. I then did the Regular Mode scan with Similar Content, I think at 90% or 95%, and that's the one that found "duplicates" that weren't the same but not one pair of actual duplicates. I did do a Regular Mode scan with Same Content first. ![]() I import into a folder named after my camera model that's why they all got " (0)" added to the filenames, the import program was adding them to the same place as the previous ones but didn't recognize that they were already there.
0 Comments
Leave a Reply. |