There's also an active forum for both support and to discuss what and how new features are built out.
Disclaimer: I'm the (only) author.
There's also an active forum for both support and to discuss what and how new features are built out.
Disclaimer: I'm the (only) author.
I know you previously responded that people should upvote that feature, but the inability to distinguish video from photo just seems like a must have fix over other potentially over engineered stuff that others are asking for.
- 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.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/
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
> 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-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...
- [1] <https://www.youtube.com/results?search_query=%22photostructu...>
It's also why I implemented bitrot detection and metadata inference. A beta tester just called the date parsing heuristics "freaking awesome and so close to black magic…" :)
https://forum.photostructure.com/t/combining-images/524/7
(And if you prefer the command line, know you can do tons of things via the CLI: https://photostructure.com/server/tools/ )
https://photostructure.com/getting-started/automatic-library...
I tried a few things with ImageMagick, but ran into problems. I'll have to try your app!
https://photostructure.com/server/photostructure-for-servers...