Sorry you have a sync glitch. I wrote a ton of code around trying to avoid exactly this situation:
I have timeouts on all I/O operations and sync-file operations, so if anything gets “stuck”, it gives terminates that process and retries one more time. If that retry fails, it marks the file as “un-importable”.
The work queue is stored in another SQLite db, so if sync crashes or you reboot your computer for any reason, the sync will restart from where it left off (rather than restarting from scratch, which meant I could never finish scanning some of my larger hard drives).
Directory content listings are cached if they take longer than a couple seconds to fetch. This is a workaround for directories from smartphone backups, which commonly don’t use sub-directories, resulting in a single directory with 10k+ files
So. Something is still slipping through the cracks here.
If you have time and want to help me debug what happened:
Shut down PhotoStructure
Restart PhotoStructure, wait a couple minutes for sync to retry that last file
If you just want to scan your other drives, go into your settings page, and instead of using “automatic”, use “manual”, and add the other drive letters (or directories) that you want to import. It’ll look like this:
I’m not sure my camera qualifies as newer Canon,
It’s a Canon 20D and the photos are from 2005 2006
You think alpha 2.1 would help?
I’ll upgrade if you think it would, but from the sound of it, the upgrade would help for newer .CR3 files.
As for backup, is sqlite3 db backup sufficient or do I need to backup the entire .photostructure folder (Windows 11)?
Just to be clear what you mean by private content, you want me to strip out the exif data? it has some personal information like Name / Serial number …
Or more about the photo content?
As long as it is not shared publicly, I have no problems sending it to you as is, I’d assume you’d want the exif data intact.