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.
2.1.0-alpha.7 was released on 7/27 (see post below). If you mean a release of a so-called “stable” 2.1.0 that could be while still. I would not wait for it, try the alpha.7 release, in my opinion it’s not any less stable than the stable release (which is now a year old) and has A LOT of worthwhile improvements.
I installed the 2.1.0 alpha yesterday.
After several hours, nothing changed in terms of previously undiscovered images.
I did a slow rebuild, and now the number of the discovered images is around 50% of what it used to be.
And every time I check I get the following message even after waiting several hours.
I’m not sure if this is license related or a bug.
This is what I see when I click on the hamburger menu
It shouldn’t be license related: both LITE and PLUS should both sync and rebuild libraries reliably. The only difference should be the PLUS-only features (like auto organization) will be available if you have PLUS.
If you have time, can you follow “Option A” and send me your logs? There’s a chance I can determine what’s amiss with PhotoStructure on your machine if you share those.
It looks like it is progressing, it now says 2 hours remain, and Refreshing assets and previews count is decreasing.
I’ll check again when that reaches 0
If it gets stuck, I’ll do the Option A
When the count reaches 0 should I expect cr2 files to be added automatically? or should I set something for that to work?
A rebuild won’t pick up new assets: it just revisits all existing files in your current library, rebuilds metadata, re-aggregates, and rebuilds previews. A sync will pick up new files on the filesystem: