Publish

TunaCut Publisher

Everything you finish goes up with its transcript and its edit decisions, not just its bytes — so the library knows what a video says, which angle was on screen when it said it, and why.

Uploads that survive the connection

Video is pushed in 8 MiB chunks, and the server owns the offset. Close the lid, lose the network or reimage the machine, and the next attempt asks where to carry on from — the desktop keeps no bookkeeping that could be wrong.

Files are stored by the hash of their contents, so pushing the same cut twice transfers nothing at all and answers immediately.

Manifests first, bytes second

The description of a session — its sources, their sync offsets, its markers and chapters, every Cut and the reason each camera change was made — is small, so it goes first. The portal can show you the whole shape of an edit while the video is still climbing.

Those manifests are kept exactly as they were sent, which means a bug in how they are read is a code fix and a replay rather than a re-upload.

The library

Search what was said, across everything

Full-text transcript search

Every sentence of every session is indexed. Find the take where somebody said the thing, across projects, and land on the second it happens.

Watch it in the browser

Cuts arrive as a thumbnail grid you can play in place. Video is streamed by the web server with proper range requests, so scrubbing is instant.

A state for every project

Open, postponed, edited, uploaded — with legal transitions and an audit trail, so a shoot that was set aside on purpose is distinguishable from one that was forgotten.

Separated by organisation

Tenant isolation is enforced by the database itself, under a role that has no power to bypass it — not by remembering to add a filter to every query.

Scheduling

A queue that survives a restart

Choose destinations for a cut, set a title and a visibility, pick now, in an hour or tomorrow morning, and it goes on the board.

The schedule is a table, not a worker's memory. Jobs carry the time they may run and are picked up by a poll — so deploying, restarting or killing the machine cannot lose next Tuesday's publish.
A killed worker is not a failed job. Work is leased and heartbeated; a lease that expires is reclaimed without burning a retry.
Quota is reserved before the work runs, not counted after it, so two workers can never both decide there was room.
The rules are re-run server-side on every request. A stale desktop cannot schedule something the routing rules would refuse, and refusals come back with reasons instead of being dropped.

What ships today: the queue, the scheduler, the wizard and a manual destination — it prepares everything, hands you the file and the copy, and records the URL once you have posted it. Direct posting to YouTube is built up to but not switched on: the quota model, the resumable upload design and the account plumbing are in place, the platform adapter is not. It is the next thing.

The control surface is in the app too

You do not have to open a browser to publish. The editor has a Cloud button that lists what is on the server, uploads what is missing, and schedules a cut without leaving the timeline.