Asset importing rejection reasons are no longer âerrors,â which caused the sync-file process to be recycled (and slow down the import)
Health checks are now automatically run, separate from file importing. Unhealthy processes could result in files being skipped in prior builds.
Raw image and video importing are now more reliable. Previous implementations would make a go/no-go decision based on the first buffer seen on stderr outputâbut ffmpeg streams warnings and errors throughout the processing of a video, so this go/no-go was based on incomplete data.
Improved docker mountpoint filtering (scans could get âstuckâ in /proc/* volumes)
Remote MacOS AFP volume hostnames are now properly parsed.
/ Nav menu improvements on mobile: more reliable scrolling on iOS Safari, and the bottom element should now be visible (even when the bottom button bar is shown)
--force now re-transcodes videos (handy for benchmarking ffmpegHwaccel)
--no-filter now disables all filters (including NoMedia)
The server dockerfile no longer specifies VOLUMEs
Changed the default for ffmpegHwaccel from auto to disabled. Docs suggested that auto would be safe, but in practice some platforms (like macOS) throw errors. Feel free to try it out on your box, but donât be surprised when it doesnât work⌠(see this forum post)
The config, library, and cache dir now remove rwX from Group and Other to help with security.
main now runs health checks on the web service every minute, and the sync service every 15 minutes, just to reduce system load.
maxSyncFileJobs and sharpThreadsPerJob can be overridden (if cpuLoadPercent doesnât do what you want).
.cache directory cleanup is more efficient now (the prior implementation could get âstuckâ if concurrent writes happened during sync)
/logcat now reads from stdin when no filenames are provided.
The libraryPath/PS_LIBRARY_PATH setting has been renamed libraryDir/PS_LIBRARY_DIR. This matches all other directory settings. An alias was added for backward compatibility.
Added new remoteFilesystemTypes that defaults to sshfs and s3fs (note that non-FUSE filesystems are already handled properly)
Installation instructions and other details
Setup instructions are the same as prior beta releases. See:
On one of my Macs Iâm getting âCannot set service name twiceâ on startup of the new app version (manual download from the website, not an update in place from beta.9). Iâve deleted the application and reinstalled. But still getting this. Any tips?
On Windows 10 desktop beta 9, I did the check upgrade and it successfully upgraded to beta 11. After the upgrade PhotoStructure did not automatically start; I donât know if it should.
After starting the program I went to Help/About⌠and the About window displayed âError Internal Server Errorâ I closed the window and opened About again and normal information displayed
In first start-up of the program, it automatically started and did some minor syncing but the About window initially displayed with Internal error mentioned aboveâŚ
I shut down Windows 10 desktop beta 11 and then restarted the program. This time I was asked to login to my account again and select the PhotoStructure library (the default library location was shown and selected and I had to change the library to where my library is located) All photo locations were correctly shown. Once I had logged in and library location selected, it worked correctly with no obvious syncing etc. The About window showed correctly.
Donât know if I caused this or not, but figured I would mention it.
Had loaded beta.10⌠had it rebuilding (slow) my database.
Then 11 came I and I thought âwhy notâ, so I updated to 11.
It went through the âwelcomeâ and âsettingsâ screen instead of just starting. Had all my data and after clicking through it picked up where it had been and seems to have finished just fine.
This is a docker running on unRaid.
So⌠short version - when should you see the welcome screen?
Prior-to-beta.10 library paths were ignored by beta.10 and beta.11. This meant if you upgraded to beta.10 or beta.11 youâd have to re-select your library.
I am a noob with docker but here is my experience, probably self-inflicted â I edited my run (terminal/cli) bash script from beta 9 to 11, and ran it. it took me thru the welcome and login, verify, then the settings. i was lazy and just clicked âmanualâ on where to scan but did not fill in all of the various places that I had entered previously⌠I will check later to see if it actually re-used my previous settings or not.
It did remember my previous file paths, and picked up the new photos I added today. thanks!
beta.10 didnât properly migrate libraryPath, and for docker users, the prior behavior defaulted writing settings directly into /ps/config, but beta.10/11 wanted to write to /ps/config/PhotoStructure, which resulted in people unexpectedly seeing the welcome page or Error: code ENOENT: ENOENT: no such file or directory, open '/ps/config/PhotoStructure/settings.toml'
Added 
Volume metadata is now multithreaded to scale to systems that have many attached drives and very slow network drives. See the forum for details.
Process handling was rebuilt
(see this forum post)
Prior-to-beta.10 library paths were ignored by beta.10 and beta.11. This meant if you upgraded to beta.10 or beta.11 youâd have to re-select your library.