With P1's geometry merged, the render follows the chosen proportions, so
the server's managed fallback now writes the advised 16:9 inside the 96x64
box (96x54) instead of the preset's ratio; the test expected the old size.
A new Data test renders a turned, straightened 9:16 project with a sepia
look through the job engine and checks that every output (fixed box and
source-sized) has the size the job was routed with, which P5 could not
check before P1's RenderGeometry was in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 4 (P5). A render job now carries the output size its
settings give (RenderSize, proportions win) and the settings format it needs,
resolved on the server before the job is split, so only nodes that read that
format and whose encoder takes the frame claim it, and a job no online node
can read no longer waits for one. Nodes and the server announce the format
they read; settings of a newer Chronos fail saying so.
Encoder size limits are read as long edge x short edge: Media Foundation's
software H.264 encoder, announced as 4096x2304, accepts portrait 2160x3840
(probed on this PC), so EncoderSelector and the provider take either
orientation and cap a portrait frame against the turned limit.
On the desktop, Sync and Send-and-render are disabled with the
NeedsNewerServer tooltip while the server reads an older format than the
working settings need.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 4, package P1: the Core geometry behind the visual
crop (R5) and the orientation controls (R6).
- RenderGeometry: one warp stab⁻¹ · O⁻¹ · V with the crop and the keyframe
centres in the view frame T (turned, mirrored, flipped, straightened);
the output size comes from RenderSize, so a fixed preset adapts to the
aspect (4K at 9:16 = 2160×3840) and AspectFromPreset is gone; the decode
grows by the straighten cover zoom; ViewFor, ViewToFrame, EditableCrop
and FootprintInView get their real bodies; a rotation that is not a
quarter turn and an out-of-range straighten render as none or clamped,
with their warnings.
- FrameOrientation: the cover zoom is taken on the pixel-centre extents,
so every output pixel samples inside the frame (full alpha coverage at
±15°, never a smeared border).
- CropFrame: crops are written on the 12-decimal grid OrientationEdit
remaps on, so four turns or two mirrors give back the same text; a
stored crop is read value by value as the render reads it.
- Advisor: the aspect (and the horizon framing) is advised on the view
turned by the camera (SequenceContext.Rotate/Flip, ForCamera); the
analyser passes the project's camera.
- Self-test: proc.orient, proc.straighten, proc.portrait.
- Tests: exact pixel permutations for turns, mirror and flip, the
orientation algebra, straighten against an analytic ramp and its full
coverage, Create sizes, a crop keeping its content through every press,
CropFrame move/resize/refit/rows, OrientationEdit round trips and its
agreement with FrameOrientation, the turned-view advice, determinism.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Groundwork for owner review 1, phase 4, so the parallel packages build on
fixed contracts and strings.
- Settings: camera rotate/mirror/flip/straighten and a look, declared after
the existing members and omitted at default. ToJson writes the lowest
format that renders the same (2 only while a transform or look is used),
so projects without them keep byte-identical text and hash; an old-build
simulation test proves the order survives an older build's round trip.
- RenderSize and RenderRules: proportions win over a fixed preset box, and
the routing format a job needs.
- FrameOrientation, CropFrame, OrientationEdit, LookFilter (identity) and
FrameFinish (look, then knee) wired into the render pipeline and preview;
RenderGeometry gains view-frame members equivalent to today.
- Protocol trailing members for node, job and server formats; SyncText keys;
EditPath counts transforms and the look as hand values.
- New en/it strings and tooltips, five icons, test fixtures moved to v3 as
the first unread format, and the 18 DECISIONS rows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Originals are now judged by their bytes, never by the media index: a removal
or clean-up hashes every file under media/originals and deletes it only when
the home holds that SHA-256; every other file, named or not, goes to the
workspace trash. Trash entries are filled under a staging name that Empty
never lists. A ledger can only name files inside exports/.
Jobs follow the workspace: a copy, render or send resolves the folder that
holds its project now (a moved workspace, a retry after a move) and waits
while a move has not switched yet. A clean-up failure after the switch is a
warning that keeps the journal for a later resume; entries that changed
since they were copied are kept, and a same-volume rename refused across
volumes falls back to copy and verify.
Sends map a replayed version by content hash, or go with the project only,
and note an old server that drops provenance. The media index (format 2) and
project file (format 3) refuse older readers while they hold originals.
Metered connections also hold sync downloads and server copies. The editor
gains Send again, the Settings page can resume a stopped move, the disabled
tooltips say why, and unused strings are pruned.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The local render, the send home, the clean-up, the settings page and the
folder move were built apart; together they left gaps:
- A local render to an image sequence writes a folder, which the send
took for a missing file. The archive home now files the folder whole
(checked by its listing hash, as the render recorded it) and the
clean-up removes a sent folder; a server, which takes one file per
render, refuses it with Errors.Workspace.SendSequence.
- Rename, delete and Remove local copy are refused while the folder is
being moved, so no project folder changes under the move.
- Settings > Workspace shows the folder, usage, Move... and Change...
again when a move ends (WorkspaceHost.MoveEnded).
- Empty... uses the Settings typed confirmation; the separate trash
dialog, never shown, is removed. The move plan counts unsent renders
with the clean-up's helper.
- Tests: the follow-up send now runs in the render tests; an end-to-end
archive-home test (originals, version on render, local render, send
with project and version, clean-up) and an image-sequence send test.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A workspace project that holds its originals now renders locally
(JobKind.WorkspaceRender), so the full-resolution render no longer
waits on the home. This holds also when the home is a server.
- The handler reads its inputs under the project's lease. It refuses
proxies-only media, and it refuses frames without an original,
saying how many lack one. It renders into exports/ with unique
names and a resumable checkpoint.
- Each output gets a ledger entry: SHA-256, the render id from
RenderJobHandler.RenderId, and the version, recorded only when
versions/ holds it and its hash verifies.
- After rendering, the handler queues a WorkspaceSend follow-up for
the outputs it recorded. A cancel leaves no partial file.
- The editor routes Originals media to the local engine even for a
server home, and lists those jobs beside the server's. It treats
WorkspaceRender like Render for the toast and the reload, says
"Sent home" when a send ends, and shows unsent ledger renders as
"Not sent".
- Version on render saves a changed project as a version noted
"Render" before it renders, and sends it with Sync automatically.
With the setting off, the render behaves as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c P1. A workspace copy of kind "originals" now copies each frame's
original beside its proxy, so a later local render has full-quality input:
streamed into a .part file, hashed as written, checked against the home's
SHA-256, renamed and read back. Archive and server homes both work, a stopped
copy resumes (originals: checkpoint), and the space check counts the
originals. A frame whose original is gone, damaged or refused keeps its proxy
and the job says how many; the copy does not fail. Stale originals are
deleted only when the home holds the same SHA-256, otherwise moved to the
workspace's trash.
Proxies only... plans first (every original hashed against the home's
frames), asks for an explicit confirmation, rewrites the media to proxies
before it touches a file, refuses a plan that changed since, and trashes what
the home no longer holds instead of deleting it.
Edit: Open in workspace offers Originals (the settings' default, disabled
when the drive lacks room) with the originals' size for archive and server
homes; Settings > Workspace > Open project picks Last used, Main or asks
which; each open is recorded for the clean-up. The project menu gains Copy
originals... and Proxies only..., refused while changes are unsaved or jobs
of the sequence run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c P4. The workspace no longer grows without bound: a daily
workspace-cleanup system schedule (04:30, catch-up) removes the media of
projects in step with their home that were not opened for Clean after,
and the size limit removes the least recently used after each copy.
Each project kept is logged with its reason (open in Edit, not in step,
home offline, jobs pending, renders not sent, unreadable, just copied).
- WorkspaceCleaner: cleans under the project's lease, re-checking every
condition; the originals the home no longer holds go to the workspace
trash, never away. The media index is marked Cleaned, so the project
reads as MediaRemoved and opening it copies the media again.
- WorkspaceTrash: lists entries with a fingerprint, and empties only the
plan the user confirmed (refused when the trash changed since).
- Trash dialog view model and view: Erase is enabled only after the user
types the number of entries.
- Removing a copy counts the unsent renders and the last originals. Send
first queues the renders' sending and refuses the removal until they
are sent.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings › Workspace › Change only pointed Edit at another folder and left
every project behind. Moving a workspace to a bigger or faster disk now
carries its projects along, without ever putting work at risk:
- a plan first: projects, files, bytes, free space at the target, whether
folders are renamed (one volume) or copied (another), projects with work
not at their home as a warning; refused for the folder itself or one
inside it, a target holding a workspace or a same-id folder, a target
inside a library, too little room, or a workspace job still pending
- the WorkspaceMove job checks the plan's fingerprint again, journals the
move in <from>/.move.json, renames each entry on one volume, and across
volumes copies each file to a .part, hashes both sides and only then
renames it into place; the source goes only after every entry is
verified and the desktop switched to the target
- a failure before the switch is undone (renamed entries go back, copies
are removed) so the source stays the workspace; a pause or a closed
program goes on from the journal; a user cancel undoes it
- while a move waits, runs or its journal is in the folder in use, opens,
checkouts, copies, saves, syncs and another folder are refused, and a
journal left at start is offered again with Resume
- the setting names the new folder only once the move verified everything
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c P3. A render made in a workspace must reach its home with the project
and version it was rendered from, and transfers with a server must respect a
metered connection, downloads into the workspace included.
- WorkspaceSendJobHandler: per unsent ledger entry, hash the file again
(missing or changed: marked failed, file left in place), push the named
version first when the home lacks it (failure fails the job, entry pending),
then file it in this PC's archive (staged copy read back against its SHA-256,
project and version checked against the sequence) or upload it to the server
with ProjectId/ProjectVersionId; mark it sent. Idempotent by render id. A send
to a server waits while HoldTransfers says so.
- SyncTransfers: extract FileRenderAsync, the lease-held filing of a staged
render into a sequence's exports, shared by GetExportsAsync and the send.
- ISyncConnector.ProjectHome (default null; SyncHost already implements it) so
the send can push a version to a server home.
- Server: RenderUploads checks the project fields at start and completion
(422 project_mismatch) and records them; RenderDto carries them.
- UploadHold also pauses WorkspaceCopy and WorkspaceSend jobs naming a server;
Server screen checkbox reads "Pause metered transfers".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c (owner review 2, R8) is built by six packages in parallel. This
commit settles everything they share, so each one touches its own files:
- job kinds WorkspaceRender (21), WorkspaceSend (22) and WorkspaceMove (23)
with their wire names, default priorities, notices and parameter records;
their handlers are registered as skeletons that throw until their
package lands
- WorkspaceJobOptions and a new CreateHandlers overload; the earlier ones
stay and default the options
- originals in the media index (an index of phase 5b reads as proxies
only), their file names, and the exports/renders.json ledger of local
renders, written atomically
- the optional project and version of an uploaded render
- the workspace settings (size limit, default media, version on render,
clean-up age, project to open) and when each project was opened, which
Reset and Import keep and Export leaves out
- WorkspaceHost split into partial files, with stubs for usage, trash and
the folder move, removal hooks for unsent renders and last originals,
and a guard that holds work while the workspace moves
- every new string of the phase in English and Italian, with tooltips
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The name follow after a pull caught only the home's own exceptions, so a 403
or any other error from the home's list (or a bundle in use) made a pull that
had already pulled and replayed report a failure. It is now logged as a
warning and the name is followed at the next pull; a cancellation still passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Before phase 5b the server's settings PATCH wrote the index alone, and every
desktop edit of a linked sequence arrives as one, so an upgraded server holds
sequences whose index settings are newer than their project.json. Main's birth
read project.json first and mirrored it over the index; sequenceChanged then
carried the loss to the desktops' linked copies.
ArchiveServiceOptions.IndexSettingsMayLead, set by the server, keeps both: Main
is born with project.json's settings as version 1 and the index's as version 2,
in force and mirrored (on a read-only archive both go to the index only). A Main
the sidecars already hold, met with no mirror known, keeps index settings that
none of its versions hold as an External version below what project.json gives
(the head again as a Restore, a merge, or the file's). The desktop is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each behavioural fix of the previous commit gets a test that fails without it:
an empty sequence writes nothing and refuses projects, a 24 MiB version is
stored and one over the limit is too_large, a page of large versions stops
short and a server home pages on, a reused username deletes nothing, a PATCH
made after project.json stays Main's head, HoldsAsync is false for a missing
file or a deleted project, and a full rescan tells the rename it found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The agent told "changes may have been missed" as soon as the stream dropped,
so a workspace re-read before the server's events could reach it again and
missed changes made in between. The signal now waits for the reconnected
stream and the refresh that follows it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R8, phase 5b (client part), ported onto the final phase 5a.
A Chronos Server with the "projects" capability is now the home of
workspace projects. A server sequence is edited in the workspace like a
local one, not inside the library, and its versions sync with the server
"like git".
- Data: ServerProjectHome is an IProjectHome over ChronosClient.
- These are HomeUnavailableException, so the workspace shows Offline: a
server out of reach, an expired sign-in, a 503 (lease, offline archive,
projects_unreadable), a 409 folder_in_use, and a server without projects.
- 404 sequence/project/version and refused names are ProjectException;
other refusals keep their meaning.
- A deleted project's head is 404 project, so final 5a's HeadAsync NotFound
rule reads it as Gone. The original 5b's IsLiveAsync and
WorkspaceStatus.Gone are dropped. IProjectHome gains rename and delete.
- Data: WorkspaceJobs.CopyFromServer downloads into the workspace, through
the desktop's session, the proxies of one frames version (or the
thumbnails standing in for them), with the aliases of the server's
conversions. It is rebuilt on final 5a's copy handler:
- the copy:frame:fv:folder checkpoint, EnsureSpace (from the server's proxy
sizes), WritingMedia, and the cancelled-copy clean-up;
- the editor's current file is never overwritten;
- each file is hashed as it arrives and checked on disk, four at a time.
It never writes this PC's archive. Originals are still refused until 5c.
- Data: SyncAgent passes on the server's projectChanged events, and after a
lost event stream it reports that changes may have been missed.
- App: SyncHost gives the server home over one session client. The Server
screen offers Open in workspace, disabled with its reason on older
servers, whose sequences keep opening with proxies.
- App: Edit opens or checks out server projects with final 5a's refusals:
unreadable copies, a disabled damaged or newer Main, a refused folder. The
"sequence left the index" refusal now applies only to projects of this
PC's archive.
- App: the picker and the chip follow projectChanged (Server newer, Not on
server). Every state, conflict, delete, remove and failure text uses its
".Server" form when one exists (WorkspaceText.ForHome). That includes 5a's
newer-format conflict, the save conflict, the taken-values toast, Gone and
version-too-large.
- App: a render of a server project first offers to send what is not on the
server, then renders the version the server holds. Offline, Gone, Damaged
and missing media hold the render. Analyses and renders run as server jobs
(ServerJobs, shared with RemoteSequenceSource).
- Pruning keeps final 5a's rule: a version is pruned only after HoldsAsync
reads it back.
- Strings in en and it; ARCHITECTURE, DECISIONS and CHANGELOG.
Tests:
- ServerProjectHome error mapping, using a fake handler.
- Against the in-process server:
- two workspaces on one project: fast-forward, replay and merge, keep mine,
take server, save both, restore;
- the copy job verifying, resuming and following new frames;
- a project deleted on the server (Gone from its head; a push sends
nothing);
- an offline server.
- SyncAgent project events.
- App tests for the host, the project menu and renders of a server home.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The read-ahead starts on the thread pool, so the demand loads could run before it developed a frame and the test failed at random on the shared runner (rc.8's release build and main's CI). The test now waits, within a scaled budget, until the read-ahead has developed a frame of its own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
Edit opens a sequence as a project of a workspace folder outside the library. Projects have linear version histories kept as sidecars in .chronos/projects/, Main mirrors the sequence's settings, and sync merges setting by setting. Migration 0009, JobKind.WorkspaceCopy = 20, Settings › Workspace, and 241 new strings in 38 languages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
Convert photos already in the archive to JPEG, TIFF-16 or Linear DNG, from the panel's Library and the desktop's Archive and Library. Each run asks Replace (same frames, originals to the trash, recoverable) or New sequence. A dry run lists what converts, what is skipped and why, size before and after, and free space; the job converts exactly the confirmed photos, resumes, and commits all or nothing per sequence. A conversion never changes what Chronos reads from a photo. Replaced originals are erased only on the archive's own word that their conversion is gone. Desktop TIFFs that WIC showed black or as noise now go to the managed reader; the Edit picker no longer spins a core.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Reorganize… on the web panel and the desktop: folder, file and title templates applied to existing sequences, with a dry run and an explicit Apply that runs as a job.
- One naming rule (FrameNaming) for import, upload and Reorganize.
- Crash-safe plan and file journals, held plans, stale-plan refusal; exports move with their folder.
- Writers refuse a folder another program moved or gave to another sequence.
- Server: POST /api/v1/archive/reorganize with a bounded plan cache; template rules.
- Phase 3 docs and translations merged; strings in all 38 languages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Web panel Library: browse, view, delete sequences and photos, mass operations (analyse, proxies, thumbnails, verify, retag, delete, CSV). It never edits the video.
- Photo trash with tombstones (migration 0008): crash-safe delete and restore, hash-checked restore with reasons, and emptying only by an explicit fingerprinted job. Sync and uploads keep deleted photos deleted; an explicit "Upload again" brings one back.
- Upload from the web panel: in-house SHA-256 in a worker with a fail-closed self-test, capture time from EXIF, chunked, resumable; no folders.
- Desktop trash dialog with photo entries and Empty.
- Admin files are revalidated (no-cache + ETag).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Jobs > Scheduled on the desktop and the admin panel. Every timer that queued work is now a visible system schedule: archive scan, upload clean-up, index backup, job-history and audit clean-ups, desktop housekeeping. New actions: verify, thumbnails, proxies, analysis, maintenance, backup, clean-ups, reports.
- The scheduler: migration 0007, in-house recurrence, compare-and-set claim, catch-up, scan at start.
- Log settings: levels, retention, size parts, total limit, daily or hourly rotation, audit retention, diagnostics share; the server writes Debug/Trace to its files again; logging never fails a job.
Upgrade: CHRONOS_LOG_LEVEL set in an existing container locks both levels; migration 0007 is one-way.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- :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>
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).
- Chronos everywhere: a byte-exact rename of contents and paths, then a
per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
links read ChronosReleasesUrl; the update check takes the highest stable
version, offers a pre-release build its final release and reports a
repository it cannot see as a failed check. EULA, security policy and
Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
nightly image and performance gates in the .NET SDK container with git
checkout and the system SQLite. The release cross-compiles the Windows
programs, checks their icon, version and DPI manifest, packs installers
and zips, publishes the Gitea release and pushes the server image
(REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
docker-exec script, which Gitea's service containers do not allow; the
throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
3 on the shared runner; the weekly performance gates keep theirs).
BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>