My library looks like yours: tons of dupes.
I’ve been hesitant to delete files from the library that aren’t considered the “primary,” given
- there are fuzzy heuristics involved
- there may be edge/corner cases I haven’t considered yet
- users may be surprised by which asset variation is considered the “best”
In thinking about this more, though, I think I could do the following and still be “safe”:
- Only copy new asset variations into the library if they are the new “best” variation
- Only remove prior-copied variations from the library if there’s an existing copy of the file that PhotoStructure has found on a different volume, the volume is mounted, and the file’s prior SHA matches the current SHA (to ensure that there’s no data loss by deleting the copy)
What do you think?
(Edit: in re-reading your post, I may have misunderstood: are you wanting PhotoStructure to delete duplicate files that are outside of your library?)