Repository navigation
v4.5.0 #1200
jaimetur
announced in
Announcements
v4.5.0
#1200
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🗓️ CHANGELOG
Planned Roadmap for the following releases
Changelog for the past releases
Release: v4.5.0
Release Date: 2026-07-18
🚨 Breaking Changes:
Immich Photos -> Remove Orphan Assetsmodule from all exposed interfaces (Web,CLI,TUI, andGUI) and from the relatedImmichdocumentation, while keeping the underlying implementation paths commented/preserved in code for possible future reuse.🌟 New Features:
Consolidate Albums Namesfeature forGoogle Photos,Synology Photos,Immich Photos, andNextCloud Photos, available from CLI, Web Interface, TUI, and desktop GUI. This action reuses the same equivalent-album-family detection logic as--consolidate-similar-albumsbut operates entirely in the destination cloud without uploading new assets. On targets that support album deletion (Immich,Synology,NextCloud), redundant albums are removed after confirmed reassignment; onGoogle Photos, redundant variants are kept because the public API cannot delete albums.Estimated Timeindicator to theAutomatic Migrationlive dashboard in both the terminal UI and the Web Interface. The estimate is computed from the current elapsed time, the number of alreadypulledassets, and the remaining pending assets (total_assets - pulled_assets), so long-running migrations now show an approximate remaining duration without being skewed by duplicate-heavy push phases.--one-time-passwordflag toAutomatic Migrationacross the Web Interface, CLI TUI, and desktop GUI whenever either the selectedsourceortargetisSynology, so Synology 2FA migrations can be configured directly from those UIs instead of only from the Synology-specific cloud module. (Issue [ENHANCEMENT]: Add support for Synology Photo OTP in Automatic Migration in the web app #1174).FeaturesandConfiguration, while keeping the shared hero/header and authentication flow. The root web route now redirects to theFeaturesworkspace, and users can switch between both pages from a dedicated top-level tab navigation.FeaturesandConfiguration, visually separated from the documentation buttons and styled as a workspace selector instead of a generic button row. This makes the active working context much clearer when moving between execution and configuration tasks.Configuration Panel -> General Arguments, explaining the purpose of shared/global arguments and listing them grouped by the same categories used in the editor cards (Logs,Execution,Naming & Folders,Filters, andOther).Configuration Panel -> Features ConfigandConfiguration Panel -> App Settings, so all three configuration sub-tabs now include an inline help summary consistent with the documentation cards already used by Takeout and cloud feature panels.Features/Configurationnavigation buttons in the Web Interface with integrated tab-style selectors attached to their corresponding panels, so workspace switching now follows the same visual language as the internal feature/configuration tab systems.Process Inputpanel to the Web InterfaceOutput Panel, placed below the live log and above theRun/Stopbuttons. When a running job requests interactive input, the web UI can now send free-form text directly to the process stdin, while still preserving the existing quickYes/Noshortcuts.Output Panelinto its own top-level workspace tab and page, placed betweenFeaturesandConfiguration, so execution output can now be opened independently while preserving the same natural tab navigation style as the other main workspaces.🚀 Enhancements:
DEBUGperformance traces forAutomatic Migrationlocal-folder pipelines and the Web Interface live log/dashboard path. Debug logs now include per-asset pull/push/album-association timing plus backend dashboard snapshot/output processing timings, and the browser can emit optionalconsole.debugrender timings whendebug_web_perf=1orlocalStorage.photomigrator_web_perf_debug = \"1\"is enabled.Automatic Migrationlive dashboard so its counters no longer depend on reparsing the execution log. The migration subprocess now emits structured dashboard snapshots, the backend persists them per job, and every browser session receives the same synchronized counters after refresh or from another device without needing the full log history.Execution Outputpanel now includes its ownRun module/Stop modulebutton pair in addition to the existing controls inFeature Selector, and theFeature Selectortitle now shows the currently selected module name (for exampleFeature Selector: Automatic MigrationorFeature Selector: Immich Photos) so the active working context stays visible while scrolling elsewhere in the page.Automatic MigrationDEBUGperformance logs so the real destination upload time is now emitted separately asautomatic_migration.asset.upload, while the end-to-end asset lifecycle is reported asautomatic_migration.asset.pipeline. This makes it much easier to distinguish backend upload cost from queue wait, album-association batching, and post-upload cleanup/finalization delays.cProfiledumps duringAutomatic MigrationtoVERBOSEmode only, and preserved the effective runtime log level inside the migration pipeline soDEBUGdiagnostics such as[PERF]pull/push traces remain visible when--log-level debugis used.Día 1,Day 2,Jour 3,Parte 4,Part 5,Session 6, and their common variants in major languages (with or without spaces, dashes, or underscores before the suffix) are normalized back to the shared base album name during similar-album grouping, while post-reassignment confirmation now refreshes keeper-album membership each time before deciding whether a redundant album can be removed.Consolidate Albums Namesfamily discovery into a shared cloud utility used byGoogle Photos,Synology Photos,Immich Photos, andNextCloud Photos. The scan now groups albums by reusable-name family in a single pass instead of rebuilding the full family plan for every album, which reduces duplicate work on large libraries and keeps the preview/keeper-selection logic consistent across all cloud targets.Automatic Migrationalbum-association confirmation for targets such asImmichandSynology. After associating a batch, PhotoMigrator now re-reads the destination album membership and, when needed, performs a short delayed second refresh before warning and scheduling a delayed retry, avoiding false negatives when the target actually associated the asset but exposes the new membership with a small delay.Automatic Migrationalbum association into a hybrid flow. When the destination upload immediately returns a reusable target asset id, PhotoMigrator now associates that asset to its destination album right away inside the push worker so an interrupted migration still leaves most already-uploaded assets attached to their album. Only the expensive duplicate-id resolution path and the assets that still do not have a reusable destination id are deferred for later recovery/finalization.Automatic Migrationalbum association until the source album has finished pulling by default. Album-bound uploads that already have a reusable destination id are associated immediately during the hot push path, while duplicate-heavy or unresolved assets are accumulated and resolved once the puller marks that source album as complete. This keeps interruption safety for already-uploaded assets while still removing the expensive duplicate-id lookup work from the main hot path.Automatic Migrationpush retries and album-association verification retries by default. Failed uploads are now treated as single-attempt failures unless the user explicitly re-enables retries, which keeps the hot path free of delayed re-enqueues and leaves failed files in theAutomatic_Migration_Push_Failed_*temp folder for manual inspection or a later rerun.Automatic Migrationalbum-association stage, together with target-specific auto-tuned batching/flush behavior.Automatic Migrationretries into two separate behaviors: real upload failures still use the normal delayed push-retry pipeline, while unconfirmed album associations now use short verification retries without being counted as upload retry attempts. This avoids misleadingattempt 1/3push retries for duplicate-resolved assets whose upload already succeeded but whose album membership was not yet confirmed by the target.Automatic Migrationalbum association recovery forImmichtargets whenPOST /api/albums/{id}/assetsreturns ambiguous400/500responses. Before warning that album membership was not confirmed, PhotoMigrator now refreshes the destination album membership, retries unresolved assets individually, and performs one last membership refresh so assets that were actually associated by Immich are confirmed instead of being left as false-negative warnings or unnecessary follow-up retries.Immichalbum-association batch size and now use API-confirmed per-asset add-to-album results before forcing a full destination album re-list, which lowers queue stalls and avoids unnecessary full membership refreshes on large duplicate-heavy migrations.Automatic Migrationpush scheduling so photo/live-photo uploads are drained ahead of regular video uploads by default. This does not change the raw network/server upload speed, but it reduces artificial queue buildup from long-running video uploads monopolizing push workers while faster photo uploads are waiting.Album Finalize Waitingprogress diagnostics duringAutomatic Migrationwhenever an album cannot yet be counted asAlbum Pushedbecause it is still active, still has pending local files, or is waiting on duplicate-resolution/association cleanup. This makes stalled album progress visible in logs instead of failing silently while the album is still legitimately incomplete.Automatic Migrationalbum-association verification retry delays from2s/10s/30sto2s/5s/10s. These retries are only used to re-check delayed album membership confirmation after a successful upload or duplicate resolution, while real push-failure retries still keep their longer independent delay policy.Automatic Migrationalbum handling acrossImmich,Synology,Google Photos, and the other cloud targets so the hot upload path now creates/reuses the exact working album first, immediately associates assets whose upload already returned a reusable destination asset id, and defers only the expensive duplicate-id resolution plus final canonical/similar-album consolidation to album-finalization time. Duplicate uploads rejected without a returned destination id are now kept in a per-album pending-resolution list and are resolved only once the source album finishes, which removes per-asset remote duplicate lookups from the main upload path while preserving correct album membership before the temporary album folder is cleaned up.Automatic Migrationfinal summary with album-reuse stats (Consolidated Albums,Canonicalized Albums) and now auto-runs targetremove_empty_albums()at the end when the destination client supports it.Execution Outputrefresh interval to250 ms, so live job output appears closer to real time while preserving the current structured-dashboard and compact-log pipeline.Automatic Migrationand the other cloud/local modules. A new base client contract now defines the common polymorphic operations and broader shared API surface, including album creation/listing, album asset listing, add-to-album, push/pull operations, upload/download workflows, album-maintenance actions, and common helpers such asalbum_exists,get_album_assets_count,get_album_assets_size, andget_assets_by_filters. The concreteLocal Folder,Synology Photos,Immich Photos,NextCloud Photos, andGoogle Photosclients were updated to expose homogeneous public method names and argument names across operations such aspush_albums,push_no_albums,push_all,pull_albums,pull_no_albums,pull_all,remove_all_albums,remove_empty_albums,remove_duplicates_albums,merge_duplicates_albums, andremove_all_assets. Optional context parameters that only matter for specific backends (for example Synology album context) are now accepted consistently as no-ops by the other clients where applicable, and the contract-signature test was extended to catch future interface drift automatically before it becomes a runtime failure.Automatic Migrationalbum-completion logging so eachAlbum Pushedline now includes a per-album asset summary withTotal Assets,Pushed, andDuplicates, plusFailedwhen applicable. These counters are accumulated from the real migration events per source album, so long-running runs now expose the final per-album outcome directly in the log without having to infer it from scattered asset-level lines.setInterval, so the browser never overlaps multiple/api/jobs/{id}requests when a previous poll is still being processed. The polling endpoint also supports a compact response path and now exposes anoutput_versioncounter, allowing the frontend to skip log repaints and dashboard refreshes when neither the compact log buffer nor the structured dashboard snapshot changed. This reduces unnecessary backend recomposition, JSON serialization, and frontend render work during progress-heavy runs and avoids the severe execution slowdown previously observed when aggressively lowering the poll interval to25-50 ms.\\r, strips embedded__PHOTOMIGRATOR_DASHBOARD__snapshots from the visible stream, and avoids the previous extra log repairs such as orphan level-prefix reconstruction, GPTH-specific prefix stitching, embedded progress/log line splitting, and paginated log-history APIs. The frontend now just polls the compactoutput_lines, colors each complete line by type, preserves manual selection freeze, and applies the existing auto-scroll / near-bottom behavior without virtualized history windows or additional client-side progress reinterpretation.Automatic Migrationpolling while preserving the corrected GPTH bar rendering.Organizing files with year/month structure ... 128557 files [02:01, 1346.55 files/s]are now recognized as progress updates and compacted in place instead of flooding the visible log with one line per refresh during long post-processing phases.Automatic Migrationlive dashboardEstimated Timecalculation so it now starts from the real beginning of the asset transfer phase (pull/push workers launch) instead of the earlier module/job start. This prevents long Google Takeout or other preprocessing stages from inflating the ETA by hours before the first assets actually begin to move.--input/--outputruns as well. PhotoMigrator now also scans the final processed output of standard GPTH executions and moves localizedArchive/Trash/Locked Foldervariants such asCarpeta privadaout ofAlbumsintoSpecial Foldersbefore publishing the processed library.Automatic Migration --move-assets truelocal sources so once an album is truly finalized asAlbum Pushed, PhotoMigrator now also tries to remove the corresponding emptied source album folder immediately instead of waiting only for the final cleanup pass. The final local-source cleanup was also hardened to treat runtime housekeeping markers such as.activeand*.lockas ignorable emptiness artifacts together with the existing excluded Synology/system files.Automatic Migrationlive dashboards across the Web Interface and terminal dashboard so queue/backlog metrics are now split into three explicit bars:Assets in Queue(real push queue only),Album Assoc Queue, andDelayed Retries. The dashboard also now showsBlocked Assetsimmediately belowBlocked Albums, renamesInvalid FilestoUnknown Files, moves the elapsed/remaining timers into the Pull panel with a visual separator, addsDelayed Recovered/Delayed Failedcounters to the Push panel, and counts real iCloud metadata CSV inputs asTotal Metadatawhile excluding generic generated reports such asPhoto Details.csvmismatches,Unresolved_Assets.csv, orNo_Date_Assets.csv.Automatic Migrationphysical asset accounting and post-upload cleanup semantics. Pull/push/duplicate/failure counters now stay aligned to the real physical files represented by each staged upload bundle, includingImmichlive-photo pairs where one queued photo item also carries a companion video. In addition, assets whose upload succeeded but whose destination album association still could not be confirmed are no longer deleted from the temp staging area: PhotoMigrator now removes them from the source when--move-assets trueis enabled, preserves the staged files underAutomatic_Migration_Push_Failed_*/Album Association Failed/<AlbumName>/, and keepsAlbum Assoc Unconfirmedas an informational follow-up counter instead of folding it into the hardPush Failed Assetstotal..webpfiles (for exampleIMG_20210805_112248_719.webp) are now treated as supported photo/image assets consistently across the local-folder and Synology-backed workflows instead of being classified as unknown/unsupported files.Features,Output,Configuration) and the secondaryConfigurationtabs now use stronger theme-aware color palettes, making the active workspace and configuration context more visually prominent while preserving the attached natural-tab layout.FeaturesandOutputworkspaces now use compact, uniform-widthRun/Stopaction buttons, dangerous-run confirmations use the same shorter wording, and starting a job fromFeaturesnow switches automatically to theOutputworkspace as soon as execution begins.Immich Photoslong-running module feedback so operations that spend noticeable time listing albums, gathering album assets, collecting assets without albums, or scanning local upload trees now emit an explicit progress message before the firsttqdmbar appears. This removes the silent waiting period previously seen in modules such asRemove Empty Albums,Remove Duplicate Albums,Remove All Albums,Pull Albums,Pull All, and the upload flows, without adding extra parsing load to the Web Interface log pipeline.Command Previewso it now displays a compactPhotoMigrator ...command instead of the full Python interpreter and.pylauncher path, and aligned the real execution order with that same preview ordering. Context-defining arguments such as--client,--account-id,--source,--target, and the main action flag are now shown and executed first, while secondary album-normalization flags such as--consolidate-similar-albumsand--prefer-canonical-album-namesare pushed near the end just before--configuration-file.User Descriptioncards so theSupported moduleslist is now displayed as a cleaner two-column layout without inline|separators, making the available cloud actions easier to scan at a glance.Output Panelheader so it now reflects the currently selected feature and, when applicable, the selected module as well (for example:Output Panel: Immich Photos - Upload All).Output Panelnow stays bound to the feature/module that is actually executing instead of following later selections made in theFeaturestab. This also keeps theOutput Paneltitle aligned with the active job context until the execution finishes.Automatic Migrationstaging intoAutomatic_Migration_<TIMESTAMP>/Push_Queue/. Local-folder sources now preserve their original relative directory hierarchy while assets are copied there, or moved there immediately when--move-assets=true, instead of using the oldAutomatic_Migration_Push_Failed_*working folder.Automatic Migrationqueue folders: failed uploads move fromPush_Queue/toPush_Delayed_Queue/, are retried three times at five-minute intervals, and move toPush_Failed/after the final unsuccessful retry. Push workers now prioritize timer-ready delayed retries ahead of newPush_Queue/work. Duplicate uploads without a reusable destination asset ID are stored inAlbum_Association_Queue/and processed by dedicated album-association workers.Album Assoc Queuedashboard depth to report the physical files retained inAlbum_Association_Queue/, including assets already held by an album-association worker for batching, instead of showing only the in-memory queue entries waiting to be claimed.Album_Association_Queue/as well. The dedicated album-association workers now resolve the existing destination asset first and then associate it to the album, so no album-bound duplicate work remains hidden in a separate in-memory pending set.Album_Association_Queue/is reserved exclusively for duplicate assets that first require remote target-id resolution.Automatic Migrationlive dashboards (Web, CLI, TUI, and GUI) soDelayed Retries QueueandAlbum Assoc Queueuse the total number of migration assets as their progress maximum.Album Assoc Queuenow appears directly belowDelayed Retries Queue.Total <type> (New / Duplicates / Failed), widened Info Panel labels to keep queue names on one line, and renamed the backlog indicator toDelayed Retries Queue.Delayed Retries QueueandAlbum Assoc Queueprogress maxima to the physical assets admitted to each queue during the migration, rather than the full migration asset count. Repeated retries of the same asset do not inflate either maximum.Automatic MigrationPush dashboards across Web, CLI, TUI, and GUI. ThePushed Assets,Pushed Photos, andPushed Videosbars now track physical assets once a pusher worker has removed them fromPush_Queue, whileNew,Duplicates, and finalFailedoutcomes are displayed separately for each media type. Added cumulativeDelayed RetriesandDelayed Recoveredcounters; album-association follow-up failures remain excluded from hard push failures.Automatic MigrationPull dashboards across Web, CLI, TUI, and GUI so each indentedFailed Assets,Failed Photos,Failed Videos, andFailed Albumscounter is displayed directly below its matching progress bar.🔢counter marker to eachNew / Duplicates / FailedPush outcome summary across Web, CLI, TUI, and GUI.Automatic MigrationLive Dashboard renderer out ofAutomaticMigration.pyintoLiveDashboard.py, keeping the migration orchestration and web-dashboard snapshots isolated from terminal presentation code.Global Settings, followed byOptional Flags UsedandOptional Flags Defaultsections. The latter reports effective defaults for optional flags applicable to the selected feature that were not supplied by the caller. Modular cloud and Other Features runs now also identify their selected module. Configurable flag values were removed fromGlobal Settings, leaving only hardcoded or runtime-derived settings there.Automatic MigrationLive Dashboard Info, Pull, and Push panel band by one terminal row, giving the live log panel more vertical space.Supported moduleslists render in one column on narrow screens.Delayed Retries QueueandAlbum Assoc Queuedashboard totals so they display0/0before any asset enters either queue instead of showing a synthetic total of1.--move-assets, PhotoMigrator copies that content, removes only the original symlink, and never moves its shared physical target away from other album links.Estimated Endto every Automatic Migration live dashboard: it appears afterRemaining Timein the Web dashboard header and beneath it in the Pull panel across Rich CLI, TUI, and GUI dashboards.Pushed Albumsonce the pipeline drains.Album Assoc Retry Schedulednow counts the physical files admitted toAlbum_Association_Queue/once rather than every retry attempt, andAlbum Assoc Retry Recoveredonly counts files whose association is actually confirmed after a retry.Album_Association_Queue/instead of being moved toPush_Failed/; unresolved terminal cases are reported as album-association failures. Remote duplicate lookup now indexes the destination library by filename to avoid repeatedly scanning every asset.Pull_Failed/: every failed pull is written topull_failed_assets.csvwith its filename, album, source/staging paths, preserved-file path, and reason. Any partial staged file is copied there with its relative hierarchy. The terminal cleanup now also removes orphaned files left inPush_Queue/only after every push worker has stopped.Push_Delayed_Queue/and use the configured retry policy instead of moving directly toPush_Failed/.Album Pushedlines. Albums now re-evaluate their normal finalization as soon as pulling completes, so their regularAlbum Pushedsummary is emitted during the migration instead of being deferred to the final reconciliation. When album consolidation or canonical naming is enabled, each completed consolidation/canonicalization also logs its source and destination names together with the original and final destination asset counts.Album Pushedsummary during the migration, and queue depth ignores Synology@eaDir/__MACOSXartifacts. Immich album-association retries now invalidate and re-resolve a destination ID that returnsAlbum not found, with an explicit protected-folder diagnostic for names such asCarpeta privada.Locked Folderwithout an unlocked API session as a common possible cause when association cannot be confirmed.Album_Association_Queue/now receives only duplicate assets whose push did not return a reusable destination ID. Its workers perform the initial remote-ID lookup plus one retry by default; failures with an already known target ID remain in the hot path and move directly toAlbum_Association_Failed/. Repeated retry diagnostics are reduced toDEBUG, and terminal queue assets preserve their relative hierarchy inAlbum_Association_Failed/.Album Assoc Queuedashboard total to count only physical files actually admitted toAlbum_Association_Queue/; known-ID hot-path association failures are no longer represented as queued assets.Delayed_Queue/toPush_Delayed_Queue/.🚩 Album Assoc Failedterminal-outcome row to the Push panel in the Web and Rich Automatic Migration live dashboards.🐛 Bug fixes:
Automatic Migrationregression introduced afterv4.0.0where duplicate-heavy album uploads could become dramatically slower because the migration pipeline tried to resolve reusable destination asset ids and apply album-family consolidation in the hot path for every asset. Known-id assets are now still associated during the normal migration flow, while duplicate uploads without an immediate reusable id are postponed to a final per-album resolution pass instead of forcing repeated remote lookups during each upload.Synology Photosshared-album/shared-space follow-up regression originally surfaced from issue#1159and later tracked as issue#1173. Shared album requests are now scoped by the currentalbum_idinstead of listing against only the shared passphrase context, which prevents runs from reusing the same unrelated asset across many albums and restores proper asset discovery for shared-space album migrations. Also stopped treating--filter-by-type allas an active filter, soAutomatic Migrationanalysis no longer accidentally falls back into personal-space-only Synology filtering when the user explicitly wants all asset types. In addition, Synology album classification now distinguishes albums merely shared by their owner from trueshared with mealbums, so owner-shared albums keep using the normal owned-album asset listing flow and are no longer incorrectly blocked just because their invitees haveviewpermissions.Automatic Migrationregression introduced by the new Synology blocked-shared-album guard. Non-Synology sources such asLocal Folderand processedGoogle Takeoutno longer call Synology-only helpers during album analysis/pull, so local migrations no longer abort withAttributeError: 'ClassLocalFolder' object has no attribute 'is_blocked_shared_album'.Automatic Migrationrace in the local/Takeout staging pipeline where a duplicate-detected asset could delete a staged file or live-photo companion that had already been dequeued by another push worker but was still being uploaded. Staged files are now treated as reserved both while queued and while actively in-flight, preventingFile not found: .../Album/<name>.MP4failures caused by premature cleanup during duplicate handling.Automatic Migrationlocal/Takeout live-photo staging bug forImmichtargets. When a photo was enqueued together with a same-stem video companion forpush_live_photo(), that companion path could still be discovered later as a standalone video asset, copied back into the temp album folder, and only fail much later withFile not foundor leave orphan.MP4files after the photo workflow had already consumed and cleaned it. Live-photo companion paths are now reserved as consumed as soon as the paired photo is queued, so they are no longer re-enqueued later as independent video uploads.Automatic MigrationImmichlive-photo staging edge case where a same-stem companion video could already be sitting in the push queue as a standalone asset before the paired photo later claimed it forpush_live_photo(). Those consumed companion paths are now explicitly marked and skipped both while enqueuing and again inside the push worker, so they no longer survive long enough to fail later withFile not found: .../<name>.MP4after the paired photo workflow has already consumed and cleaned them.Shared Space, trueshared with mealbums, and regular owned albums. PhotoMigrator now documents and follows the browser-observed Synology API behavior more closely: albums surfaced undernormal_share_with_meare no longer blindly treated as passphrase-based shared albums, Shared Space albums owned by the current user prefer the browser-styleSYNO.Foto.Browse.Itemversion=7listing flow withalbum_id, and album downloads now also includealbum_idcontext with passphrase fallback only for true shared-with-me cases. This resolves the remaining#1173gap where Shared Space albums were detected but their assets could not be listed/downloaded correctly. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).Synology Photosowner-id learning forShared Spacealbums sonormal_share_with_mealbums can still be reclassified as owned even when no personal albums were seen first. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).Automatic MigrationandDownload Albumskeep trying alternate item-list variants when album counts are missing instead of treating the first empty success response as a truly empty album. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).__PHOTOMIGRATOR_DASHBOARD__snapshots no longer leak into progress lines, create blank lines, or leave strayINFO :fragments inExecution Output.Execution Outputpanel so manual text selection is preserved whileAuto Scrollis disabled even if a live progress bar keeps updating, and addedCtrl+C/Cmd+Ccopying for the currently selected log text.@eaDir,@Recycle,.DS_Store, or thumbnail files are now treated as empty and can be removed both during album completion and in the final cleanup pass.Synology Photos/Automatic Migrationfollow-up around issue#1173.--filter-by-type allis now treated consistently as “no active filter” inside the migration pipeline as well, so Synology Shared Space runs no longer fall into the filtered album-validation path during analysis or pulling. In addition, Synology shared-album classification now also reads owner/permission details whensharing_infois returned at the top level of the album payload instead of only underadditional, which improves reclassification ofnormal_share_with_mealbums that are actually owned by the current user and keeps them on the correct Shared Space listing/download flow. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).Execution Outputauto-scroll behavior so scrolling upward now disables live tail following automatically, and returning near the latest visible lines re-enablesAuto Scrollautomatically without requiring a manual toggle.Auto Scrollautomatically before the fresh job output begins, preventing a previous manual scroll-up state from leaving the new run stuck without live tail following.Automatic Migrationclient-interface regression where Synology-specific album context arguments such asalbum_scope,album_expected_count, andalbum_idcould leak into generic source-client calls during album pulling, breaking non-Synology sources likeLocal Folderwithunexpected keyword argumenterrors. The migration pipeline now only sends those extra kwargs when the active source client is actuallySynology Photos, and the public album/pull method signatures acrossLocal Folder,Immich Photos,NextCloud Photos, andGoogle Photoswere also aligned to tolerate the shared optional album-context parameters as no-ops for stronger cross-feature compatibility.Automatic Migrationintroduced while adding per-albumAlbum Pushedsummaries. The new album-stat counters were originally wired through local helper closures, which could fail withNameErrorinside threadedpuller_worker/pusher_workerexecution in some runtime environments. Album summary counters are now updated through module-level helpers with explicit shared state, so threaded migrations no longer abort with_ensure_album_stats/_increment_album_statlookup failures while building the final per-album summary line.Synology PhotosShared Spacefollow-up around issue#1173by aligning the affected album-detail, album-list, item-list, count, and download requests with the browser-observedPOSTtransport used by Synology Photos, while keepingGETas a compatibility fallback. Shared Space runtime album-detail hydration now also requests the same extra fields observed in the browser (flex_sectionandprovider_countin addition tosharing_infoandthumbnail), which helps keep owner-shared album classification and item discovery aligned with the real web client. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).Automatic Migrationsimilar-album consolidation confirmation for targets such asImmich. The consolidation path now reuses the same robust album-association verification flow already used by normal asset pushes, including confirmed-id tracking and follow-up membership refreshes, instead of relying on a single immediate album reread. This prevents falseAlbum Consolidation Partialresults such as repeatedN-1 / N confirmedcases where the keeper album had actually accepted the missing asset but the simplified consolidation check undercounted it.Synology PhotosShared Spacefollow-up around issue#1173where album-scoped item listings could still be emptied after retrieval by being revalidated against the globalget_assets_by_filters()result set even when no explicit filters were active. Synology album listings now keep the assets returned by the album API unless real user filters must be applied, which avoids discarding validShared Spaceassets just because the global library listing exposes a different namespace than the album context. Also fixed Synology user-id normalization soowner_user_id=0is preserved instead of being dropped, which keepsShared Spaceowner metadata available for diagnostics and future classification logic.Execution Outputpanel scroll handling after the incremental log renderer refactor. Horizontal scroll is now preserved while new log deltas arrive, reaching the bottom manually with the mouse wheel no longer forces an unexpected snap/repaint cycle, and re-enablingAuto Scrollnow jumps reliably to the latest visible log lines instead of rebuilding a full snapshot unnecessarily.Automatic Migrationregression in theAlbum Association Failedfallback cleanup path. Assets whose upload had already succeeded but whose destination album membership could not be confirmed were calling_finalize_album_association_failed_asset(...)with the newer shared finalization kwargs (asset_type,count_push_stats), while that helper still exposed the older narrower signature. The fallback cleanup path is now aligned to the new signature and additionally guarded so any internal cleanup/move error is logged as an album-association cleanup issue instead of incorrectly degrading an already uploaded asset toPush Failed. This prevents falsePushed + Faileddouble-counting for cases such as video assets inside localized special albums likeCarpeta privada.Local Folderinitial file-type analysis so unsupported uppercase.MPfiles are now classified consistently asunknown/ non-supported assets instead of being filtered inconsistently by suffix-only logic, and auxiliary JSON files such asprogress.jsonare no longer counted as real metadata assets during the initial Takeout/local analysis.Automatic Migrationlocal-source asset selection so files already classified asunknown/ unsupported (for exampleprogress.jsonor unsupported.MPfiles) are no longer returned by the generictype='all'no-album scan and therefore are no longer pulled, staged, or pushed as if they were migrable assets. Also fixed theLocal Folderno-album asset cache so results are now isolated per requested type instead of leaking a previousallquery into laterunsupported/metadatalookups.Import Configflow so importing a.ini/.cfg/.txtconfiguration now preserves the original path values declared inside the imported file instead of rewriting them immediately to the active web user's allowed roots during import. Runtime execution still re-sanitizes effective path arguments per user as before.Synology Photosowned-album listing for modules such asRemove Empty Albumsby routing theSYNO.Foto.Browse.NormalAlbum -> listcall through the same resiliententry.cgitransport fallback used by the newer Synology shared-space code paths, instead of relying only on the older directGETrequest. Also fixed the associated error log so failed album-list responses now include the real Synology payload for diagnosis.account-idis now persisted independently for each cloud module (Google Photos,Synology Photos,Immich Photos,NextCloud Photos) instead of being shared globally across all of them. Changing the selected account in one cloud feature no longer overwrites the account used by the others.Command Previewand matching execution command formatting so the visible command now uses a compactPhotoMigrator ...prefix instead of the full Python interpreter and.pylauncher path, orders context-defining arguments first (--client,--account-id,--source,--target, main action flags), moves secondary album-normalization flags such as--consolidate-similar-albumsand--prefer-canonical-album-namesnear the end before--configuration-file, and renders single-value options in--flag=valueform for better readability while keeping multi-value options space-separated.Command Previewand the real execution command now follow the same argument order as the upper Web Interface panels instead of a separate manual priority list. This also guarantees that--prefer-canonical-album-namesis emitted before--consolidate-similar-albumswhenever both are present, matching the order shown inGeneral Arguments -> Execution.Synology PhotosShared Spacediagnostic and recovery follow-up around issue#1173for the remainingNo Albumspath. The global Synology asset listing used to derive assets without albums now emits targetedDEBUGsummaries per request variant and after the final merge, including counts plus sampledid/filename/owner_user_id/provider_user_idvalues so mismatches between personal-space andShared Spaceuniverses can be inspected from a normal debug log. In addition, the global asset scan now tries an extra browser-styleSYNO.Foto.Browse.Itemversion=7/method=listvariant and merges successful results by assetid, while the downstreamNo Albumsdifference now also uses assetidinstead offilenameto avoid false matches when different assets share the same file name. (Issue [BUG]: Photos from the Synology Photos Shared Space are not imported, but all albums that are created contain the same photo #1173).Automatic MigrationRich Live Dashboard failing on its first render withNameError: _compute_dashboard_estimated_time. The dashboard timing helpers now live with the terminal renderer and remain shared with the web snapshot path.Stopbutton being disabled forAutomatic Migrationruns launched in an external Live Dashboard terminal. The GUI now tracks the external migration PID and sends the stop signal to that process rather than only tracking the terminal launcher.Automatic MigrationLive Dashboard startup after its renderer extraction. Its estimated-time calculation, UTC timezone dependency, background progress parser, and visible-progress-row selection now reside inLiveDashboard.py, preventingNameErrorfailures while rendering or consumingtqdmprogress lines.Automatic MigrationLive Dashboard layout so the Info Panel has enough height to renderAssets in Queue,Delayed Retries Queue, andAlbum Assoc Queuetogether. Pull failure rows and Push🔢 Total (New / Duplicates / Failed)summaries now remain on one line below their matching bars.Automatic MigrationLive Dashboard panels with the web layout:Blocked AlbumsandBlocked Assetsnow remain only in Info, the queue label uses a consistent-width timer emoji, and full-width separators now precede Info queues, Pull timing, and Push delayed-retry counters.Automatic MigrationLive Dashboard runs. PhotoMigrator now stays in the foreground terminal job while its PID is still reported to the GUI forStop, preventingzshsuspended (tty output)/terminatedjob-control messages from shifting the final Rich dashboard.Automatic MigrationLive Dashboard panel alignment: the Push delayed-retry divider now has matching vertical spacing, both delayed counters use the same-width emoji, and the shared panel height was reduced after the layout fit was corrected.zshjob-control suspension of the external RichAutomatic MigrationLive Dashboard by disabling shell job monitoring before the foreground launch. Rich panel separators now also size themselves to their current panel width instead of overflowing fixed-length divider strings.Automatic MigrationLive Dashboard finalization and layout: GUI-launched dashboards now report migration completion back to the GUI before waiting forCtrl+C, so final statistics remain visible while the GUIRun/Stopcontrols reset correctly. The completion prompt is shown inside the dashboard log panel, and the Info, Pull, and Push panel dividers are now rendered as full-width Rich rules instead of split table-cell fragments.f-stringexpression.📚 Documentation:
Automatic Migrationdocumentation to explain the current physical-file counter semantics, the meaning of each live dashboard counter, and how to interpret leftovers inAutomatic_Migration_Push_Failed_*, especially the newAlbum Association Failed/<AlbumName>preservation path. Also updated the Web Interface documentation panels soAutomatic Migrationnow lists--one-time-passwordunderOptional arguments, andGoogle Takeout/iCloud Takeoutnow expose their feature documentation panel directly above the argument form.💾 Download
Download the tool either for Linux, MacOS or Windows (for both x64 and arm64 architectures) or Docker version (platform & architecture independent) as you prefer, directly from following links:
Linux::
Mac OS:
Windows:
Docker Launcher:
Full Changelog: v4.4.1...v4.5.0
This discussion was created from the release v4.5.0.
All reactions