CI / Build and test (push) Successful in 5m11s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 6s
Release / Build, test and publish (push) Successful in 8m57s
CI / PostgreSQL 16 integration (push) Successful in 3m10s
CI / PostgreSQL 17 integration (push) Successful in 3m30s
CI / Docker image (push) Successful in 49s
Release / Server image (push) Successful in 1m4s
- :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels); bad tags are refused before anything is built. - Unraid: CHRONOS_SPACE_PATH and the template's Array view show the array's free space; the write volume (cache) is shown apart; completions check the archive volume (507). - Settings is a gear, docked at the foot of the admin sidebar; About is the last part of Settings on the desktop and the panel. - Import > Folder > Whole folder: one sequence per format (desktop only). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
58 KiB
58 KiB
Changelog
All notable changes. Format: Keep a Changelog; versions follow SemVer;
commits follow Conventional Commits (release notes are generated from them by Chronos.Tools changelog).
[Unreleased]
[0.1.0-rc.3] — 2026-10-26
Added
- Import › Folder…: Group › Whole folder imports the picked folder, with its subfolders when Subfolders is on, as one sequence per file format, whatever the cameras and pauses (RAW+JPEG stays two sequences). The title defaults to the folder's name, and an interrupted or repeated import of the folder continues the same sequence without renaming it. Desktop only (owner review 2, R9).
- Server:
CHRONOS_SPACE_PATH(SpacePathinserver.json) makes the admin panel show the free space of that folder's volume instead of the archive's. The Unraid template maps the share's array view (/mnt/user0/Timelapse) read-only to/space(Array view), so the dashboard shows the array's free space, not the cache's (owner review 2, R2). - Admin panel: the storage figures' tooltip names the volume and its file system, and on an Unraid share without a space path explains that they are the share's primary storage; a Write volume line shows the archive's own volume when it differs.
- Server diagnostics: the environment report lists the archive, space and data volumes with their free space, file system and mount.
Chronos.Tools release-channels: which channels a release tag moves (latest=,image_latest=), by SemVer 2.0 precedence among the published releases (every page of Gitea's list, one--releasesfile per page).
Changed
- Server image:
:latestnow follows the highest stable release, or the highest pre-release while no stable release exists, so the Unraid template and the compose file find an image from the first pre-release on. The public releases repository still follows stable releases only, and re-publishing an older tag never moves either back. When the release workflow cannot decide (the releases list unreadable, or a tag older thanrelease-channelssuch asv0.1.0-rc.2published again) it warns and moves neither, and still pushes the version's image.:nightlystays the nightly build ofmain, for testing only (owner review 2, R1). - Release workflow: the tag must be SemVer 2.0 without build metadata (no leading zeros such as
v01.2.0, no empty identifiers); any other tag is refused before anything is built. - Desktop: About is the last page of Settings and the rail keeps Settings alone at the bottom. Check for updates and the Releases link are on Settings › Updates; the data folder and the diagnostics bundle are on Settings › Advanced only (About's own copies of those buttons are gone) (owner review 2, R5).
- Admin panel: Settings sits at the foot of the sidebar, above your account (at the end of the top bar on narrow
screens); on a short window the pages above them scroll instead. About is the last section of Settings, without the
server name and certificate fingerprint already shown above it, and its database and uptime fill in without holding
up the form; old
#/aboutlinks open it there (owner review 2, R4, R5). - The Settings icon is a toothed gear in Chronos, the Uploader and the admin panel; it no longer looks like a sun (owner review 2, R4).
Fixed
- Import: a session that ends on another day shows both dates in its plan row and in Show plan, not only the first.
- Server: completing an upload, a render upload or a render node's result now checks the archive volume's free space
first. A full volume answers 507
insufficient_storageand the upload stays resumable, instead of the copy into staging failing (owner review 2, R2).
[0.1.0-rc.2] — 2026-10-23
Fixed
- Update check: the release page and the download links come from the repository address the build names
(
ChronosReleasesUrl), not from Gitea's answer, whose links use Gitea's ROOT_URL; with the owner's plain-http LAN ROOT_URL every release was ignored (the check accepts only https links).
[0.1.0-rc.1] — 2026-10-23
First pre-release, built and published by Gitea Actions.
Added
Foundation
- Solution and build rules: warnings as errors, nullable, .NET 10 SDK pin, zero-package guard (build target and
Chronos.Tools package-guard). Chronos.Testing: in-house test framework and runner (theories, categories, timeouts, environment and Windows gates, serial classes, parallel runs, JUnit XML, workflow annotations).- Localization runtime (
Loc, CLDR plural rules with few/many forms, runtime culture switch, RTL),en+itcatalogs, machine translations with per-language glossaries,i18n check/export/missing/import. - Brand mark geometry, SDF rasteriser, PNG encoder, ICO writer and
make-icon(icons generated at build time). - VS Code debug configurations for the Windows programs (
.vscode/launch.json,tasks.json): Chronos, the Uploader, the server on SQLite with its data inout/debug/server, the screenshot captures,Chronos.Toolsand the test programs, each built in Debug first.
Engine (Chronos.Core)
- Metadata: signature sniffing, TIFF/Exif/GPS/XMP/MakerNotes, JPEG segments, ISO-BMFF (HEIF, CR3), RAF, PNG,
WebP and RIFF parsers with fuzz-tested partial results;
MetadataBuilderfallback chains;ExifWriter. - Codecs: JPEG (baseline, progressive, lossless; libjpeg-exact integer IDCT), PNG, TIFF, linear DNG writer, GIF and APNG encoders, ICO; native RAW development for DNG (opcodes, AHD demosaic, DNG colour), CR2, NEF, ARW, PEF, RAF.
- Imaging: planar linear-light buffers, decoder providers and decode tiers, separable resampler, frame window with
read-ahead, memory budget and float32 spill,
thumbs.pack, thumbnail cache, proxy builder. - Analysis and advisor: frame statistics, colour temperature, deflicker (global and regional), holy-grail step
redistribution, white-balance smoothing, light analysis with findings, streaming deep analysis with checkpoints;
Advisorrecommendations with localised reasons, apply/optimise, sequence presets. - Motion: FFT and phase correlation, pyramidal Lucas–Kanade flow, motion blur, nine-patch stabiliser, virtual camera, frame interpolation, stacking and star trails.
- Render and export: render plan (constant, adaptive, interpolated, remapped timing), preparation pass, geometry,
pipeline, self-test suite (
Chronos.Tools selftest); preset resolution, encoder selection with hardware preference and fallbacks, output naming. - Video: streaming MP4 muxer (H.264/HEVC/AV1) with inspector, AVI-MJPEG with OpenDML indexes, NV12/P010 conversion, level tables, managed encoder provider (MJPEG-AVI, image sequences, GIF, APNG).
- Archive format: layout and naming templates, sidecars, leases, index snapshot, scanner, verify, adopt, orphans, rename plans; card import planning, sessions, hash-verified copy and verified erase; TPK1 installer payload.
- Diagnostics:
SecretScrubberandDiagnosticsArchivefor diagnostics bundles that never carry passwords, tokens, keys or photos.
Data (Chronos.Data)
- SQLite binding (winsqlite3 / libsqlite3) and in-house PostgreSQL wire protocol v3 client (pool, prepared statements, COPY, LISTEN, cancellation).
- Migrations, repositories and the
ChronosDatabasefacade; one persistent job engine with checkpoints, pause/resume, priorities and crash recovery for client and server. - Archive engine: create/adopt/open, incremental and full scans, rebuild from sidecars, ingest of uploads and card imports, verify, thumbnails and proxies, maintenance, mass rename, job handlers.
- Analysis and render engine: light/deep analysis and render job handlers, render node client.
Programs
- Chronos desktop: shell with rail, job bar and toasts; Welcome, Library (virtualised grid and list, filters, sort,
hover scrubbing), Jobs, Server (trust-on-first-use sign-in, DPAPI token), Settings (general, archive, rendering
with encoder inventory and self-test, storage, server, updates, advanced) and About;
--capturescreenshots. - Update check against the releases repository on Gitea and Download: the setup (the portable zip for a portable
copy) is fetched into
%TEMP%\Chronos\updates, verified against the release'sSHA256SUMSand shown in Explorer; an interrupted download resumes, Cancel stops it, and a transfer that stalls for 60 s fails. - Diagnostics bundle (Settings › Advanced, About): environment, codec and encoder inventory, scrubbed settings, recent failed jobs and logs.
- Chronos Server: configuration from
server.jsonandCHRONOS_*, TLS (auto, PEM, proxy), API v1 (auth, users, sequences, frames, uploads, sync, jobs, render nodes, events over WebSocket, archive), admin panel (dashboard, users, archive, jobs, settings, logs, about), audit log, LAN discovery, Windows service. - Server diagnostics:
GET /api/v1/server/diagnostics(ManageArchive, audited) and a Diagnostics button in admin › Logs. - Admin panel: light and dark themes following the browser with a toggle, plural-aware counts, audit filter by
several actions, password change, typed confirmations, right-to-left layout; an administrator cannot reset their
own password from Users (409).
DELETE /api/v1/sequences/{id}moves the sequence to the archive's trash and answers 409 or 503 with a reason when it cannot. - Chronos Uploader: tray program with resumable persisted queue, session grouping, watch folders, bandwidth limit, verified-only source deletion.
- Chronos Setup: one-screen installer, per-user or all-users, components, shortcuts, file types, upgrade in place, silent mode, uninstaller that keeps user data unless asked.
Desktop workflows
- Library: timeline with year bands (keyboard), saved views, quick actions reachable by keyboard, mass actions bar, Delete… into the archive's trash (dry run, typed confirmation, progress, Undo), Rendered / Not rendered / Synced and Origin filters, and cards for server-only sequences whose Render and Analyse run on the server.
- Archive manager: tree by capture year, health with duplicate groups and Mark copies, statistics charts with values for screen readers, maintenance, Trash… with restore, mass rename and move behind a dry run; failures as one-sentence toasts with Retry, dialog errors inline, Cancel as the default button.
- Import: devices and card pool, camera profiles, plan with sessions (merge, split, titles), hash-verified copy into the archive, a folder or the server, verified delete, format behind a typed confirmation, eject, auto-import.
- Sequence editor: Frames, Exposure, Camera, Motion and Export tabs with the advisor's Auto values and reasons, Optimise, preview tools, section charts, curve editor (keyboard included), undo/redo and saving shortly after each change; Set hero updates the Library thumbnail; batch export with size and time estimates.
- Server sequences open in the editor with proxies: saved, analysed and rendered on the server, with cancel and retry of server jobs, a read-only mode for accounts without Edit, and an explicit prompt when the same setting changed on the server; Export Sync sends local renders to the server; Save both copies can be restored from the Export tab.
- Client sync (Server screen): sync table with filters, conflicts settled with Keep mine, Take server or Save both, uploads and downloads as resumable jobs that check the free space first, proxies kept offline, uploads paused on metered connections; this PC as a render node while signed in.
Localization and accessibility
- 38 cultures:
en,itand 36 machine translations with per-language glossaries and an independent review. - Right-to-left: windows mirror from startup and on every language switch (
ChronosWindow), directional icons mirror with them, photos, charts, numbers, paths and templates stay left-to-right islands, category charts lay out from the reading side. - Accessibility: automation peers for sliders, filmstrip, curve editor, preview, charts, split buttons and the job
bar; live regions for status lines; toasts announced (failures as errors);
Field.Errorfor inputs without validation; charts take the keyboard (arrows, Home/End, Enter) where an item can be activated; two-word names for icon-only toggles.
Distribution and CI
- Docker image (PUID/PGID, health check), compose file with PostgreSQL 17, Unraid template.
- CI on Gitea Actions (
.gitea/workflows/ci.yml): Linux build and tests, the Windows programs cross-compiled and checked (pe-check), PostgreSQL 16/17, Docker smoke test, i18n, XAML lint, format, package and YAML guards; the Windows tests, screenshots and installer test on a Windows runner onceWINDOWS_RUNNERis set. - Release workflow: tests, self-contained publish cross-compiled on Linux, optional Authenticode signing
(osslsigncode), installers, portable and server zips,
SHA256SUMS, release notes from Conventional Commits, the Gitea release (Chronos.Tools gitea-release), the server image in the Gitea container registry, and optionally a separate releases repository (README, EULA draft, SECURITY policy, issue forms, Unraid template, compose file,i18n/). Chronos.Toolscommands for the Linux runner:zip,gitea-release,postgres-ci(the wire tests' roles and TLS through SQL) andpe-check.- Performance gates (
perf.yml, weekly): 500,000-photo library and 100,000-frame rebuild from sidecars (every column compared), each on SQLite and PostgreSQL 17. Chronos.Tools.Tests: the fixtures command's warning annotations and exit codes.
Verification against the brief (2026-10-12)
- Settings › Import, Analysis and Formats pages (defaults of new cards, deep-analysis width, thresholds and auto-run, decode tier per format with Store links for missing codec extensions); Archive thumbnail size and rescan interval; Advanced › Restore (daily backups, dry-run comparison, staged for the next start) and Reset all; Archive › Maintenance › Restore database… opens it.
- Daily
VACUUM INTObackups of the SQLite index (newest three kept) on the desktop and on a SQLite server; maintenance vacuums the index when a tenth of it is free and its dry run reports the reclaimable size. - An archive's templates, proxy size and thumbnail size live in its archive.json. Settings › Archive and PUT /api/v1/archive/settings rewrite it atomically under a lease, and new desktop archives start from Settings › Archive.
- CI: pixel diff of the
--capturescreenshots againsttests/visual/baselines(Chronos.Tools screenshots diffandaccept; 8/255 per channel, at most 0.05 % of a screen; a screen without a baseline fails once any is committed); captures are reproducible (fixed sample clock, English formats, no animation). - CI: installer test (silent install, run, upgrade in place, Uploader-only install, uninstall, exit codes), now the
last step of the
windowsjob on a Windows runner. - CI: the PostgreSQL 16/17 jobs run the MD5, cleartext, trust and TLS (require, verify-full) tests; a server without TLS fails them.
- Windows tests: Media Foundation output opened by MediaPlayer (H.264, and HEVC Main10 where hardware allows) and its first frame decoded by a source reader.
- Proxies of originals the server cannot decode (HEIF, AVIF, WebP): manifests and render-node claims carry the
archive's proxy policy and, per frame, its flags and whether the server wants its proxy;
PUT /api/v1/frames/{id}/proxytakes them from clients that edit and from render nodes; desktop uploads and render nodes make and send them; renders, analyses and thumbnails of those frames use them. - Server: the archive is scanned incrementally at start and every ten minutes, so photos already in an adopted folder and sequences added by another writer are indexed without a manual rescan.
- Shell: the taskbar button mirrors the job bar and turns red while a failure waits on the Jobs screen. Toasts also appear as Windows notifications while the window is minimised or in the background; a click brings the window back and opens what the notification names. Ctrl+1…6 and Ctrl+, open the sections the rail tooltips list, and the editor's 1:1 view moves to Ctrl+Shift+1.
- Jobs: a toast when a long operation ends or fails, whichever screen started it, and one toast for a whole batch ("12 jobs finished"). Rail badges count running jobs and unseen failures, sync conflicts, Library sequences with warnings, and Archive health lines that need attention.
- Settings › General: Start with Windows (minimised, for the copy that set it; the uninstaller removes it) and Windows notifications.
- Server events:
cardEvent(BRIEF §14.3) tells every connected client about a card import another client streams into the server (started, progress, finished). Clients report it throughPOST /api/v1/uploads/cards. - Decode tiers (BRIEF §8.2): frames that decode only through an embedded preview are marked preview-only, with a Library chip showing the count, an Info finding and the output capped at the preview size. Frames nothing decodes are flagged undecodable, listed as a sequence warning and left out of renders. A frame that stops decoding during a render is shown as its neighbour instead of failing the job.
- MakerNotes: exposure mode (Canon, Olympus, Fujifilm, Panasonic, Sony), RAW size (Canon sRAW/mRAW, Nikon RAW M/S) and the Panasonic time-lapse hint. Sequences shot by the camera's own intervalometer get adaptive timing across their pauses.
- The SQLite compile options appear in the log and in the diagnostics bundle.
.chronosproject files. Save project file on the Export tab writes the sequence's reference and settings. Opening one (a double-click, orChronos.exe <file>) opens the sequence with those settings as one undoable step, with one-sentence toasts when the file cannot be read or its sequence is not in the library. One Chronos runs per data folder, and a later launch hands its file to the running one or, while that one is closing, waits for it and starts with the file.- Server:
PATCH /api/v1/sequences/{id}takesexpectedFramesVersionand answers 409frames_conflictwhen the sequence's frames changed since the settings' frame positions were written.GET /api/v1/sequences/{id}/manifestreturns frames, frames version and settings of one frames version.
Changed
- Chronos on Gitea (2026-10-23,
docs/requests/2026-10-23-chronos-gitea.md): the product is renamed from Titano to Chronos everywhere (programs, namespaces,CHRONOS_*variables,%LOCALAPPDATA%\Chronos,.chronosfiles, the imagechronos-server, every translation with its grammar); the repository, update check, licence, issue and support links, container registry and workflows move from GitHub to the self-hosted Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos); releases are published in that repository, withEULA.mdandSECURITY.mdat its root and the issue forms in.gitea/ISSUE_TEMPLATE. - Owner review 1 (2026-10-16, R2,
docs/requests/2026-10-15-owner-review-1.md):- jobs run one at a time, on the desktop and on the server. Settings › Rendering › Parallelism (server:
CHRONOS_PARALLELISM, admin panel › Settings › Jobs) is now how many photos the running job processes at once: thumbnail and proxy passes draw that many photos together, decode tiers are probed that many at a time, the deep analysis measures that many frames and a render decodes that many ahead (fewer wherever large originals are developed whole, within the memory budget); the server's renders get a frame window sized to the host (a quarter of the memory available) instead of 1 GiB; the running job has the whole memory budget; - a new job waits its turn, and pausing the running job lets the next one start. An optional priority queue
(Settings › Rendering, admin panel › Settings › Jobs,
CHRONOS_PRIORITY_QUEUE) gives each job kind a level; by default renders, imports and downloads are high and verifies and proxies low. A queued job of a higher level pauses the running one without asking, and that one resumes by itself afterwards from its checkpoint; - the Jobs screen shows "8 photos at once", and a Priority queue chip while the queue is on; the admin dashboard shows the parallelism;
Chronos.Tools i18n pruneremoves from the translations the keys English no longer has.
- jobs run one at a time, on the desktop and on the server. Settings › Rendering › Parallelism (server:
- Owner review 1 (2026-10-16, R1): the rail is 200 px wide, so section names fit in every language, and collapses to icons with ≡ or Ctrl+B; collapsed, an icon's tooltip names its section. The choice is saved at once and survives Settings › Reset all… and Import…. The admin panel's sidebar is 256 px and collapses to icons the same way (≡ or Ctrl+B in any keyboard layout, kept in the browser). Beside the wider rail at the 1200 px minimum no action is cut off in any language: the Jobs table, the Archive tree, the Import plan and result, the trusted certificates, the cache folder, the editor's header (a server job's Cancel always stays), preview tools (a second line when needed) and frame table share their width differently; headers, titles and cells that may be shortened end in an ellipsis and show their text in their tooltip.
- Owner review 1 (2026-10-16, R7): the Sequence section is now Edit (Ctrl+3) and edits one sequence at a time. Without an open sequence, or after Change sequence (the title's ▾, Ctrl+O, or Next sequence on the last step), it shows a picker of this PC's and the server's sequences, newest first, with a search; the open sequence (else the one edited last) is selected and in view. Enter, also right after typing, or a double-click opens one, and Esc goes back to the open one, which stays open behind the picker until another one has loaded: a server sequence whose proxies are still coming, or one that cannot open, leaves it open. Its last edit is saved first, or discarded on the user's word and then never written. The editor's tabs are now the steps of a guided path under the header, freely navigable: a new first step, Analysis, lists every finding of the analyses with a button to the step that deals with it, five measurements (light, flicker, exposure steps received, shake, flagged frames) and where each other step stands. Each step shows its status with its own glyph (to do, done, attention, running, waiting); its tooltip starts with its name, says why and names its shortcut. Previous · n / m · Next under the settings column, Alt+1…8, Ctrl+PgUp/PgDn and the arrow keys in the step bar move between steps, the keyboard following. The editor opens on the step last shown for that sequence in this run, else on Analysis while the sequence is not analysed or its analysis waits or runs, else on Frames, whose list is now the frame warnings.
Deprecated
CHRONOS_WORKERSand theWorkerskey ofserver.jsonset the parallelism (photos the running job processes at once, 1 to 64); the server logs a warning at start when the variable is set. UseCHRONOS_PARALLELISM.
Fixed
- Owner review 1 (2026-10-16,
docs/requests/2026-10-15-owner-review-1.md):- the App test program could crash on exit after every test had passed (WPF's binding cleanup racing the process's end);
- choosing Keep editing when the open sequence's last edit could not be saved left the other sequence as the one asked for, so every later visit to the section asked again (R7);
- choosing Discard change for an edit that could not be saved still wrote it when the archive answered again while the question was open (R7 review);
- a double-click on a row or card of the Library opened nothing (only one on the empty space under the list opened the selected sequence): the row took the mouse-down (R7 review);
- thumbnail and proxy jobs over several sequences failed after 10–20 minutes with "TimeSpan overflowed" and then stayed Running; their progress now counts frames, a stalled job shows no time left, and a job's end is always recorded (R10);
- the Jobs screen showed the speed of hash verification and card import, which count bytes, in fps;
- choosing presets quickly in the editor made the VS Code debugger stop in
WicDecoderProvider.cs: a cancelled preview decode left its background task (R4); - GoPro DNGs converted by Lightroom or DNG Converter were treated as GPR and read only through their 8-bit embedded preview, and DNGs Windows' preview-only DNG decoder read were reported as decoded natively. Videos now develop them natively at 16 bits, analyses and the editor preview use the embedded preview when it is large enough, and the archive's existing frames are reclassified by the next light analysis (R4);
- an upload or a card import could fail with "Access to the path is denied" (server: 503
commit_failed) when a thumbnail or proxy pass, an analysis or a scan was reading the sequence's sidecar at that moment: the write now waits a moment for the reader (found while testing phase 2); - taking a sequence's lease could fail with "Access to the path is denied" when the previous holder had just released it while another process was reading it (Windows keeps the file pending deletion meanwhile): the lease is now taken once the reader lets go (found while testing phase 2).
- Opening the repository in VS Code with C# Dev Kit before the first build listed MSB3073 for Chronos, the Uploader and Setup: design-time builds no longer generate the program icons, and log WPF's MC1000 about projects not built yet as a message.
- Server: downloading the current log while it was being written aborted the response (Content-Length mismatch); it now serves the bytes listed at request time.
- Mass rename and move: a dry run asked for right after typing was replaced by the pending debounced one, so Apply stayed disabled; the explicit dry run now cancels it.
- Radio groups leaked between windows not shown yet (the Setup's capture overflowed the stack); screenshots of right-to-left windows were mirrored twice.
- Switching the language left texts kept by view models in the old language until their next change: the job bar, the Jobs rows, the editor's chart legends and summaries, Auto chips and info line, the Archive figures and the Import session table now follow at once.
- Right-to-left: in meta lines a number after a Latin field ("Canon EOS R5 · 2 h") joined the Latin run and split its own field; fields are now separated with right-to-left marks (left-to-right ones in the preview's frame data). Charts no longer switch to Arabic-Indic digits after Arabic words. Desktop file sizes use the language's units; table cells holding a size, speed or time left read in the language's direction and fit their column.
- CI: a full artifact storage failed jobs whose checks had passed; uploads no longer fail a job, artifacts expire in days, and screenshots reach their branch through the cache.
- Release workflow: signing and the public-repository publish never ran (step conditions cannot read the step's own
secrets); the publish job lacked the .NET SDK for
make-icon; re-publishing an existing tag failed; the portable zip lackedportable.txt. - CI fixtures step reported missing RAW samples as a silent pass; it now emits a warning per missing sample.
- Release workflow: the server image and its
:latesttag were pushed before the Windows tests passed, and publishing an older tag again moved:latestback; the image now follows the tests and:latestthe newest stable release. Stable release notes started at the last release candidate instead of the previous stable tag. - Settings › Rendering quality, parallelism and background priority had no effect on jobs. Parallelism Auto is now half the logical cores (owner review 1 makes it the photos the running job processes at once; see Changed).
- A restore staged in Settings › Advanced now runs before the index opens, so it recovers an index that no longer opens. A copy failing quick_check is set aside before any backup is made, and a restored copy is never applied twice.
- Settings › Archive could not save archives with an empty name (made at a drive root), showed sizes outside the presets as 1920 or 320, and kept editing the previous archive after the archive folder changed. Reset all and Import settings rewrote the shared archive.json.
- Server archive settings were lost on restart and ignored by proxy jobs. A damaged archive.json returned 500, and a busy one reported a busy sequence.
- The naming preview's sample title follows the interface language.
- Server (Windows): the data folder, the temporary admin password and the TLS key were readable by every local user,
and any user could plant
server.json. The data folder is now private to SYSTEM, Administrators and the server's account. The server refuses to start when anything in it belongs to another account or is a link, readsserver.jsononly after checking its owner, and creates secrets anew with a private ACL. - Server (Windows): a new archive folder under
C:let every local user change it, including the folders where the service stages uploads. It now lets only administrators and the server change it (other users may read it), and the log reports an existing archive that others can change. - Server (Windows):
--install-serviceregistered a LocalSystem service from any folder. It now refuses outside a Program Files folder that only administrators can change. - Server: in TLS mode proxy, any client could set
X-Forwarded-Forto escape the sign-in rate limit and forge its audit address. Now only the proxies inCHRONOS_TRUSTED_PROXIES(default: loopback) may. The admin panel shows Not via proxy, and a refused sign-in names the setting. - Docker: a fresh, root-owned archive folder made the container crash-loop. An empty or root-owned archive root is now
given to PUID:PGID. Any other archive, or
.chronosfolder, that this user cannot write stops the container with a one-line error.CHRONOS_DATA_PATHis honoured, and Kestrel no longer warns about overridden addresses at every start. - Docker and Unraid: remapped host ports broke the admin panel's HTTPS redirect;
CHRONOS_PUBLIC_HTTPS_PORTandCHRONOS_PUBLIC_HTTP_PORTfix it, and the LAN beacon uses them too. The Unraid template's default database host could not resolve on the bridge network.--helpnow lists every variable, the TZ description is accurate, and the README explains host networking for LAN discovery (with PostgreSQL on loopback). - Tests: four tests switched the UI language outside a serial class and could break English assertions running beside them; such a switch now fails the test that made it, after English is restored. The frame window's unobserved-exception check runs alone and counts only its own exceptions.
- Test runner: a skip or failed assertion in a test class's constructor was reported as "Exception has been thrown by the target of an invocation"; it now keeps its own outcome and message.
- CI: a crashed screenshot capture passed once it had written one picture; the MediaPlayer playback check could end the whole Windows test program on an exception.
- Render nodes: frames missing, corrupt or excluded on the server, and originals it had not hashed yet, failed the whole job; they are now skipped or fetched with a size check, and damaged frames the server's own render skips are skipped too.
- Sync: a download whose partial file already held the whole original failed on every retry; an edit saved on this PC while an automatic comparison ran could be replaced by the server's version unseen.
- Sync: proxies the server asked for were neither counted nor sent for adopted (unverified) folders, and the count did not follow proxies sent from elsewhere.
- Mass rename and move: sequences inside a moved folder kept their old paths in the index; they now move with it (listed in the dry run, locked while it moves), and a target inside a sequence folder is refused.
- Archive maintenance: compacting a thumbnail pack could drop thumbnails a thumbnail pass was writing.
- Server: proxies of HEIF frames made from embedded previews by earlier versions are asked for again on the next proxy pass; a proxy sent for a frame the server decodes itself, or a preview-sized one, is refused.
- Exiting while signed in to a server no longer waits for the UI thread that the exit blocks. Closing the window stops the editor's player and runners before the index and the engine close. Cancelling or closing the sign-in dialog no longer leaves a half-signed-in session or crashes on a late answer.
- The usage counts consent, which promised a daily count that nothing sends, is offered only in builds with
ChronosAdsEnabled=true(BRIEF §21). - Error toasts say why an action failed in the app's language instead of showing .NET or OS text: a job posted to the server from the Library (including a server whose certificate changed since sign-in, which used to fail silently), the card check and delete after an import, and a failed editor save. The editor's own reasons (frames changed on the server, settings changed elsewhere at the same time, sequence gone, project unreadable or from a newer Chronos, account without edit rights) are no longer reported as 'The server does not answer'.
- Texts that count now agree with the number: advisor findings and reasons, the rendering cores and the upload-all
tooltip have singular and plural forms ('1 frame is black'), a single exposure change has its own finding, and
tallies and job log lines read as labels ('Copied: 40 · failed: 1', 'Missing: 2 · damaged: 1').
i18n checkfails on a text that puts a count before a counted noun without plural forms, or that tallies counts with participles. - Archive: picking another archive while the screen was reading no longer leaves the previous archive's tree, figures or search results actionable. Until the picked archive is read, Scan, Verify, Rebuild and the set actions wait and say so, and the rebuild dialog shows the picked archive's own state and count.
- Import: a job that ended before the screen recorded it (a destination gone offline) no longer leaves the screen copying forever, and a replaced import result is released.
- Library: the timeline's month readouts follow a language switch.
- Server: a sequence created with
POST /api/v1/sequences(the Uploader's "New sequence") could not take uploads. It now gets its folder with its first photo, named by the folder template like an upload-created sequence. - Server: "already on the server" was also answered for copies flagged missing or corrupt or whose file was gone, and
the Uploader then deleted its source. Only an intact copy answers now. An upload of the same content repairs the
damaged frame in place, and the damaged file is kept beside it as
<name>.damaged-<time>. The Uploader deletes a source only after a verified upload. - Archive: excluded frames, the hero frame and virtual-camera keyframes stayed at their positions when earlier photos were inserted (late uploads, sync downloads, scans of added photos), so renders dropped the wrong frames. They now move with their frames, also when a scan finds the photos while a project is being saved.
- Server: render outputs could be uploaded by upload-only accounts. Offering and completing a render upload now needs the Edit permission.
- Server: an upload resumed after the chunk size setting was lowered had its chunks refused (413). Chunks keep the size their upload started with.
- Server: the
render_existserror had no message.i18n checknow requires a message for every server error code. - Server: re-uploading a photo to repair its damaged copy counted against the uploader's quota again, and could be refused for quota. Repairs are free now. A copy in another sequence no longer stands in for the damaged one of the target sequence, neither at upload start nor after a crash.
- Server: one account's card import reports could push job and sequence events out of every client's event queue. They are now limited to one progress report a second and 120 events a minute per account. A card import into the server no longer waits up to 20 s for an unreachable server when it ends.
- GoPro GPR frames decode through the camera's JPEG even after an import or upload kept the JPEGs in a sequence of their own.
- A file locked by another program or a network hiccup during analysis or a render no longer flags the frame undecodable, and neither does a file deleted after indexing. A resumed deep analysis checks such frames again.
- A small render (720p, GIF) no longer lowers the output cap of preview-only sequences to the small preview it decoded.
- Thumbnails of RAWs whose embedded preview is smaller than 320 px are developed from the RAW.
- Frames both analyses could not decode are listed once, with the right count, including missing and corrupt ones.
- Render logs no longer name frames a speed-up skipped as shown by a neighbour.
- A failure while probing the SQLite compile options can no longer stop the index from opening.
- The PostgreSQL server writes decode tiers in batches instead of one statement per frame. The 0003 migration headers name the right mirror file.
- Upgrading or uninstalling while the Chronos Server service ran failed, and uninstalling left the LocalSystem service registered. Services of the installed programs are now stopped once the programs have closed, started again after the upgrade (or when it fails) and deleted on uninstall. Only services, sign-in entries and shortcuts that start a program setup installed are changed, so installing into a shared folder never touches other programs'.
- The Server component installs only for all users in a folder inside Program Files, where standard users cannot replace the program its service starts.
- Uninstalling left the Uploader's and the client's sign-in entries behind. 'Remove my data' deleted the whole data folder, also another installed Chronos product's index or upload queue, and now removes only the data of programs no other installed product uses. Uninstalling one product deleted the other's Uploader shortcuts; they now move to the copy that stays.
- The
.chronosfile type name is written in setup's language. - Titled notes with no listed changes now say 'Maintenance release.'.
- Server: HEIF frames whose proxies had arrived stayed preview-only, capped at the size of their Exif thumbnail (often 160 × 120); the advisor then chose the 720p preview preset and the Library showed the preview-only chip. A frame read from its proxy is no longer preview-only, an arriving proxy has the sequence analysed again, and a deep analysis or render that was running when the proxies came no longer flags the frames again.
- Proxies: renders, analyses, the server's manifests and proxy downloads used a proxy another photo had left at a frame's place after frames were inserted before it, or a thumbnail-sized one made by an earlier version. Proxies of frames whose capture time has a seventh sub-second digit (file-system times) were rejected. One rule now decides: the frame's own capture time, to the microsecond, and the policy's size for frames the host reads through proxies.
- Server: frames added to a sequence whose proxies had all arrived were not asked for their own until the next proxy pass. Manifests now read a proxy's header only when the file has changed.
- Deep analysis: a run resumed after proxies arrived kept its checkpoint's 'unreadable' verdicts, and a saved report kept listing frames that now decode from their proxies (warning badge, exclusion advice). Such checkpoints start over, such reports no longer count, and the server no longer sends them to remote editors. Checkpoints written by earlier versions still resume.
- Thumbnails drawn from proxies ignored the archive's thumbnail size. Below 320 px they were drawn again and appended to the pack on every pass; above 320 px they were never redrawn at the larger size.
- A proxy or thumbnail pass resumed after a pause, crash or retry could mark the sequence complete while frames before the resume point lacked them, so the server stopped asking for those proxies. The proxy pass log now counts frames waiting for a proxy apart from unreadable ones.
- Sync: exclusions, the hero frame and camera keyframes taken from the server, or sent to it, could land on other photos. This happened when the photos they were written against arrived later (a download or upload of earlier photos), when photos were imported or uploaded while the settings were compared or sent, or when a hero was chosen while another waited for its photo. Settings now move between copies translated to the receiving copy's frames, matched by photo and read as one state with those frames. Positions on photos that copy does not hold yet wait in the project until the photos arrive.
- Server (PostgreSQL): settings saved through the API while photos were being filed into the sequence could be silently undone.
- Sync: downloading a sequence the server adopted but never verified failed with 'did not arrive intact'. Its originals now download, are size-checked and hashed on this PC, and are matched to this PC's copies by size and capture time. They are not uploaded again, and their proxies are sent like the others. A photo the server's folder holds twice no longer leaves Download on offer forever.
- Sync: when the server's settings version moved without a change, the comparison failed while the local archive was offline or read-only. Identical settings are now agreed without touching the archive.
- Sync: thumbnails cached in place of proxies the server did not have yet were kept after the server got its proxies. The next proxy download replaces them, and offline caches refresh when the proxies arrive.
- Server: a sequence created with
POST /api/v1/sequencesthat was still waiting for its first photo could lend its id to loose photos at the archive root during a scan, also when the root's sidecar was damaged. The Uploader's uploads then went to the root. A rebuild could delete such a sequence, and maintenance compacted the root's thumbnails under its id. Scans, rebuilds, the orphans check, verify and maintenance now leave it alone until its first photo gives it a folder. A root sidecar the server may not read now fails that folder only, not the whole scan. - Server: sequences found by a scan now get thumbnails and proxies like uploaded ones. This covers photos already in an adopted folder, folders another writer adds and photos added to a folder. Each sequence gets its own background pass, so a folder renamed or deleted before its pass no longer leaves the others without images. Remote cards and proxy downloads no longer stay empty until an administrator queues the jobs.
- Mass rename and move: a folder that gained a sequence after the dry run (a scan of photos copied into a subfolder) no longer moves while that sequence's index row stays behind. Such a plan is refused as out of date.
- Server: sending a large chunk again after a lost answer, to an unknown or finished upload, or with a session that had signed out or lost the upload permission closed the connection instead of answering. The answer now reaches the client, including 401 and 403, so the Uploader asks the user to sign in instead of retrying.
- Server:
PUT /api/v1/archive/settingsanswered 500 when archive.json held a thumbnail size or proxy quality out of range. It now answers 409archive_policyand names the policy to correct. - Desktop archive polling started only at launch, for the archive folder known then. An archive created on the first run, chosen in Settings or relinked was never rescanned, and Rescan every had no effect, until a restart. Polling now follows the archive folder and survives a drive that is offline at start.
- When the server or another PC changed an archive's templates, proxy size or name in archive.json, imports, uploads and the admin panel kept the old values until a restart, and saving the admin panel's archive form wrote the old templates back. The index now follows the file whenever Settings › Archive opens and at every rescan, on the desktop and on the server, and the admin form reads the file when it opens. A poll no longer puts back values an administrator had just saved, and an archive.json written by a newer Chronos is no longer registered.
- Settings › Archive saved 320 as this PC's thumbnail size whenever the open archive was offline. With an empty archive folder it edited the first archive of the index. It silently dropped an edit made while a newly chosen archive was still opening, and an edit made just before a second folder change went to the archive of the later folder.
- Start with Windows (client and Uploader) stayed ticked after Task Manager disabled the entry, and ticking it again could not turn the entry back on. The Uploader now also reads it again when its settings open.
- A portable copy unpacked in a OneDrive folder, including a Desktop or Documents folder backed up by OneDrive, kept its SQLite index there. It now keeps its data in %LOCALAPPDATA%\Chronos, says so at start and names the data it kept beside it before, which it leaves untouched. A per-user data folder that OneDrive synchronises is now reported with a warning.
- Import: a photo that could not be copied, a card file the plan could not read, and every photo a stopped import never reached now say why in the app's language: destination full, access denied, card gone, the server's own reason, server not answering, untrusted certificate. The system's text no longer appears, on the Import screen or in the import job's log.
- Errors: a server behind a reverse proxy that answers with its own error page (for example 502 while the server restarts, or 413 for a large photo) now reads 'The server does not answer' or 'The request is larger than the server accepts' instead of the English 'Bad Gateway' or 'Request Entity Too Large'.
- Archive: picking another archive no longer leaves the previous archive's tiles, charts, last scan, recent runs and rail badge on screen, or its maintenance actions enabled, while the new one is read or after its read fails.
- Jobs: a render that ends while its sequence is open in the editor always gets exactly one completion toast, with Show in folder. It still gets one, without Show in folder, when the editor cannot read the sequence again or closes as the render ends, and a render the editor did not follow is announced too.
- Jobs: Open on a job over several sequences (a deep analysis of a Library selection), from its toast, its Windows notification or its row, shows all of them selected in the Library instead of opening only the first in the editor. A job over a whole archive opens the Library without freezing it.
- Server (Windows): a service that refused its data folder or
server.jsonstopped with error 1064 and gave no reason anywhere. Start and stop failures now go to the Application event log (sourceChronosServer) with the entry to check. The README gives the full steps to fix a data folder created by a console run. - Docker and Unraid: the
CHRONOS_TRUSTED_PROXIESguidance suggested trusting a whole Docker network (Unraid:172.17.0.0/16), whose gateway carries relayed IPv6 and host connections. It now names the proxy container's own fixed address and warns against subnets, the gateway and the default bridge. - Setup: an upgrade that renamed the client or the Uploader deleted its sign-in entry, which silently turned Start with Windows off. The entry now moves to the new program with its options, and is removed only when the component is dropped.
- Setup: uninstalling removed the client's and the Uploader's sign-in entries but left the on/off state Task Manager keeps for them. It now goes with the entry; an entry an upgrade moves keeps it.
- Server: when a desktop sharing the archive imported photos into an existing sequence, they got no thumbnails or proxies, and the frames they renumbered answered 404, until a pass was forced by hand. A scan now notices when the sidecar's frames changed behind the index and queues the analysis and both image passes. Analyses, image passes, verify, maintenance, rating and tag edits and renames no longer hide such a change, or a new title set on another PC, from the next scan.
- Server and desktop sharing an archive: each poll of the desktop after the server's uploads made the server analyse that sequence and draw its thumbnails and proxies again.
- Archive: a rating, tag or title edit, a mass rename, a decode tier recorded by an analysis, image pass or render, or a verify stamp wrote the whole sequence row back from what had been read earlier. Settings saved meanwhile (Auto values, a server PATCH) were lost, or the frame count went back. These writers now write only their own fields, under the sequence's lease.
- Server: a thumbnail or proxy pass that read the frames before a scan found photos added to the folder marked the sequence complete again, so no pass was queued for the new photos. A pass now marks it only while the sidecar still lists the photos it read, or while the next pass is already queued.
- Server: when a camera uploaded faster than a pass could finish, the sequence offered no thumbnails or proxies until uploads paused.
- Server: after a verify gave photos their first hash, their thumbnails answered 404 and the next pass drew them all again. They are served and reused again.
- Deep analysis: when the proxies of frames a run had found unreadable arrived during that run, it still recorded the deep status, its warnings and its advice, which every later reader discards. It now checks its report against the frames as they are when it records.
- Rebuild: a sequence that got its first photo, or was created by an upload session, while a rebuild ran lost its index row. The Uploader got 404 and the session continued in a second sequence. A row is now checked again under its lease before it is removed.
- Editor: an edit made while earlier photos were being added to an open sequence of this PC (a sync download, an import, a scan) was saved in the old frame order, so other photos were excluded and the hero and keyframes moved. The editor now reads the frames again before it saves and moves its positions with them, undo steps included.
- Editor: a render queued after earlier photos were added to an open sequence, without another edit, rendered the old frame order. Render now reads the frames again first. On a server sequence whose frames changed it is not queued, and the editor goes read-only with Get proxies.
- Editor: when earlier photos were added to an open sequence, the frame on screen became another photo, and Exclude, Set hero and keyframes applied to it. The frame on screen now stays on its photo.
- Editor (server sequences): a save made after the server's frames changed, before the editor heard of it (scans send no event; events are lost while reconnecting), overwrote the positions the server had moved. Saves now name their frames version, so the server refuses them and the editor goes read-only with Get proxies. Frames are compared again after a reconnect.
- Sync: when a server folder held the same photo twice, settings crossing to this PC put every exclusion, hero and keyframe of that photo on its first copy, and a later push changed the server's. Each copy now keeps its own positions, and a photo not hashed yet is never taken for another of the same size and capture time.
- Sync: with Keep proxies offline, thumbnails cached in place of proxies were never replaced when a server sequence could not get all its proxies (a missing or damaged frame). They are now downloaded again once the server offers their proxies, and again after a failed download.
- Server: a proxy upload above 1 MiB that the server answered without reading it closed the connection, and clients retried a network error. This happened when the session was signed out, the Edit role was lost, the frame was gone or the proxy was not wanted. The answer now reaches the client.
- Settings › Archive: a template, proxy size or thumbnail size committed while the archive's settings were being read could be shown reverted, together with this PC's default, while the archive kept the edit. This happened on a share that was waking up. Such a read now waits for the edit and is made again, so choosing another archive folder also finishes only once the rows show that folder's archive.
- Import: a server import that could not stage its copies on this PC said the destination was full or refused writing. It now names this PC's cache folder.
- Import: a failed archive import showed the job's raw system or database text as its line. It now shows the archive's own sentence or 'The import stopped before the end.', with the text in the tooltip.
- Portable copy: a SharePoint or Teams library synced with OneDrive's Sync button was not recognised as synchronised, so a portable copy unpacked there kept its index inside it. Its data now goes to %LOCALAPPDATA%\Chronos.
- Docs: the Windows README's recovery of a data folder created by an unelevated console run keeps the folder private. It no longer resets the permissions, which let every user read the TLS key and the temporary admin password, and it removes the account the service names, also when a standard user ran the console.
- Analysis: an analysis that read a sequence's frames before photos were added, removed or renumbered (an upload, an import, a scan) recorded its advice, warnings and analysed status for the old frames. Its Auto frame rate and warning count overwrote a newer light analysis, and the new photos were never analysed. It now records nothing in that case, unless a light analysis is already queued to replace what it records. It says so in the job log and queues a light analysis of the photos as they are. When another Chronos sharing the archive changed the photos and this PC has not indexed them yet, the analysis no longer writes its old results over that Chronos's in the shared project and sidecar. The next scan indexes the photos.
- Sync: with Keep proxies offline, a proxy download made while the server was still drawing newly uploaded photos cached thumbnails or nothing for them, and marked the cache up to date. The editor then kept those thumbnails or blank frames until the frames changed again. The cache now stays stale until every photo, missing or damaged ones aside, has its proxy. It is downloaded again once the server's sequence changes.
- Sync: a title, tags, rating or notes taken from the server could hide photos that another Chronos sharing this PC's archive had just added to the sequence. Scans then skipped the folder until it changed again. The next scan now indexes them.
- Server (PostgreSQL): an analysis, image pass or render could record decode tiers or light statistics while a scan or rebuild indexed the same sequence. The two could deadlock, and one of the jobs failed. Every writer now takes the sequence before its frames.
- Server and desktop sharing an archive: an upload could reach a sequence after the desktop had verified it or changed its tiers, duplicates or title. The upload indexed only the new photo and hid the rest from later scans. Until a full scan, the server kept those photos unhashed and counted missing or corrupt ones as healthy. Such an upload now indexes the whole sequence from its sidecar.
- Uploads, and photos a desktop downloads from its server: a photo copied by hand into the sequence's folder since the last scan stayed out of the index. Only a full scan or the orphans check found it, because later incremental scans skipped the folder. The next scan now indexes it.
- Scans and rebuilds: a scan could read a sidecar just before an upload or another writer committed, then write it over the newer index. That dropped the new photos or tier flags, and incremental scans then skipped the folder. The scan now reads the sidecar again under the sequence's lease. An older sidecar put back by hand or by a file-sync tool no longer takes the frames version back.
- Verify: flags recorded while a verify ran (a preview-only or undecodable photo, a duplicate) were undone by it. A photo an upload repaired during the run was flagged missing again, so the next copy moved the good file aside. A verify now writes only the missing and corrupt flags, and only for files still as it checked them.
- Tags: on PostgreSQL, two writers of sequences sharing tags could deadlock, and one of them failed. This happened when an edit through the API listed the tags in another order than an upload, a scan or another edit. Tags are now written in one order, and an unchanged set is not written again.
- Archive › Orphans: photos the fix indexed were never analysed, so the Auto values, warnings and preview-only count stayed those of the old frames. The fix now clears the analysis and image flags as a scan does, and queues the light analysis. When Settings › Analysis › After a scan is on, it also queues the background deep analysis, as a scan does.
- Deep analysis: a pass overtaken by new photos replaced the current
analysis.jsonthat a later pass had made. The report endpoint then answered 404, and the next light analysis dropped the deep status. The report is now saved under the sequence's lock, and never over a more current one. A pass that leaves the saved report in place records that report's summary and warnings, not its own. - Scans of an archive shared by two Chronos indexes (a desktop and its server): one index could write a sidecar at the frames version the other held for other frames. The other index then took the frames as unchanged. When the versions match, a scan now also compares the frames themselves and writes changed ones one version past its row.
- Orphans fix and scans: a photo that could not be read yet (held open by another program, no read permission, a OneDrive placeholder offline) made the folder count as changed, so every fix rewrote the sidecar, cleared the thumbnails, proxies and analysis status and queued the analyses again. It now changes nothing until the photo can be read.
- Deep analysis: a pass that started before a proxy arrived could overwrite the report a later pass made from the proxies and drop the sequence's deep status. It now leaves a report that describes the frames as they are in place.