? PhotoStructure for Desktops has a “pre-flight check” of the library directory at startup. (PhotoStructure will revert this when Live Photos are properly aggregated). ? Videos and images are no longer considered for aggregation (to avoid spurious live photo matches). Again, this would only impact users with high-CPU-count servers). ? Filesystem watches for the same path are now shared within a given process (Node.js quietly fails when watch is invoked more than 3 times for the same path. WIP-), used by metadata extraction and transcoding ops, now use a filesystem mutex to avoid race conditions (this caused random import failures on high-CPU-count servers). ? Work-in-progress files, (hidden files starting with. A new syncExitTimeoutMs setting has been added, which defaults to 1 minute–this should be enough to close SQLite even on the slowest remote HDDs and largest libraries, but now you can extend this if you must.` ? Depending on how PhotoStructure was shut down, the sync process could have been force-killed while still closing the database, which would result in SQLITE_CORRUPT. ? A bug in URI root encoding caused alpha.2 through alpha.4 to have several sync reporting and progress panel-related errors, which should now be resolved. ✨/? When sync finishes for a given path, and retryEnqueued is true, sync will look at the last day of sync reports for paths that are “stuck”–paths that have a “enqueued” entry, but no subsequent “synced”, “timeout”, or “failed” entry, and retry them. If automatic organization is enabled (see the copyAssetsToLibrary setting), a new sync report row will be added when photos and videos are copied into your library. Good news, everyone, /\r?/n/g is replaced with ": " in the details column now! Although Excel and LibreOffice parse these CSVs properly, Google Sheets don’t, and there was discussion asking if these newlines could be avoided. Prior sync report CSVs could contain a “details” cell that included newlines. Sync reports now include a “started” state emitted after being dequeued from the work queue. Sync reports no longer worryingly state that all sidecars were skipped–the sync report now states what file(s) the sidecar will be associated with, and only marked as excluded if they don’t match with any sibling photo or video file. The README.txt now includes a comprehensive list of “states” for files and directories.Īdded a new “at” column that’s ISO-date-time formatted, because most spreadsheet apps don’t know how to parse millis-from-common-epoch. The sync report directory can be opened via the nav menu (if accessed via localhost), or on PhotoStructure for Desktops, via the tray and system menus. Use a smaller value if you’re serving your library over a constrained network. ✨ Lazy loading is now configurable, via the new lazyLoadExtraVh setting. Set retainFileBirthtimes=false to disable this new behavior. This isn’t a field that exists on standard Linux filesystems, so it’s not supported there. ✨ When PhotoStructure copies files on macOS and Windows, it now retains file “birthtime” metadata. ✨/? Sidecar handling was improved: photo.JPEG now matches up with. Implementation details and usage are explained in this forum post. File exclusion patterns were completely revisited in this build. ✨/?/? The prior build ( alpha.2 and alpha.3) introduced globs, but having both scanPaths and globs resulted in confusion (and several bugs). We know build against ES3, and should support ancient versions of Safari. When we heard that Nighthawk’s Grandma’s iPad didn’t work, though, this had to be fixed. ✨/? Prior versions of PhotoStructure compiled the front-end javascript against an ES5 target, which caused older, unsupported iOS devices to not render the frontend. ✨/? “Friendly” duration strings are now supported (after I typoed the fourth ISO duration string). ✨ Support for remote TCP GELF-compatible logging servers via the new PS_LOG_SERVER and PS_LOG_SERVER_LEVEL settings. We’ll just stick with the linuxserver.io standard. bash and other commands consider $UID and $GID to be reserved, read-only, and trustable environment variables, which could cause issues. Prior releases tried to be “nice” and support both $UID and $PUID (as well as both $GID and $PGID), but this turned out to be a bad idea. If you used $GID, please switch to $PGID. ? PhotoStructure for Docker users: If your docker or docker-compose scripts used $UID, please switch to using $PUID. Please report on Discord if you see anything odd, unexpected, or possibly buggy. PhotoStructure for Desktops on macOS is still not working with this build, but all other editions of PhotoStructure seem to be functional. ? There were some crash-bugs in alpha.4, alpha.5, and alpha.6. Note that these are notes for versions released in 2022. Photo by lilartsy 2022 PhotoStructure release notes August 24, 2022
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |