5 ms·
I really didn't have much luck with the de-duplication. I tried photostructure for about 3 weeks and since stopped. I was trying to pull photos from multiple di
by kingosticks 5y ago
I really didn't have much luck with the de-duplication. I tried photostructure for about 3 weeks and since stopped. I was trying to pull photos from multiple different drives/folders into one central organised place. A few issues:
- The de-duplication didn't seem to work, it at least was defeated by my messy files. I spent many hours manually going through the results and finding many dupes. Then I lost interest in doing that and gave up.
Edit: I've just realised, was this (by design) simply copying each photo into the merged tree but then if I browse using the photostructure app it will hide the dupes? Can I prevent it making a copy? I want to use other file/photo browsers also.
- can't use datestamp info in the filename?
- very, very slow to sync from my external USB 3 drive. I'd be happy with that if the de-duplication worked. Also the status about what it's doing seems sporadic and half the time appears to be doing nothing at all. Maybe my laptop is too slow?
- no map view
I did like the feed of random photos. I saw loads of great old snaps I'd forgotten about. Somewhat bizarrely, when I wanted to share them quickly with others I ended up taking a photo of the photo(s) with my smartphone and sharing that via WhatsApp. That's more my failing but it did seem a bit silly that I resorted to doing that.
- mceachen 5y ago> if I browse using the PhotoStructure app it will guide the dupes Yes: out of an abundance of caution, the unique (by SHA) variations of each asset are copied into your library. There are heuristics that pick which is the "best," and although those heuristics seem to be robust for most beta users, I didn't want to be the source of want data loss. > datestamp info in the filename? The metadata in the file is trusted more than any date extracted either from the filename or the directory hierarchy. Details are here: https://photostructure.com/faq/captured-at/ https://photostructure.com/faq/captured-at/ If you use the info tool, it'll tell you how it's extracting the date from any given file: https://photostructure.com/server/tools/#file-information https://photostructure.com/server/tools/#file-information > slow to sync PhotoStructure scales imports to accommodate current hardware, in Ann effort to keep the system responsive. Parallelism is limited by available RAM and CPU count. If you think it was being too conservative, please send me a screen shot of your about page (it includes both system metrics and what is thinking for scheduling limits), and if you want, debug logs, and we can look into what's going on. https://photostructure.com/faq/error-reports/#how-to-manually-send-your-logs https://photostructure.com/faq/error-reports/#how-to-manuall... > no map view This is a popular feature request that I'm looking forward to building: https://forum.photostructure.com/t/support-reverse-geocoding-to-automatically-tag-assets-with-location-names/231 https://forum.photostructure.com/t/support-reverse-geocoding...
- kingosticks 5y agoThe metadata for some of my filew is total junk. If I used another tool to strip that bad metadata would it then use the datestamps in the filename? I think this was defeating the de-duplication also. In an ideal world I'd be able to configure everything from a particular source folder to use filename datestamps.
- mceachen 5y agoYes: you can use `exiftool -all: $file` to strip all metadata, but please have backups before you do anything: ExifTool is both powerful and fast.