split
Split a timeline into shorts as new projects, reporting overlaps and unassigned spans, with a planning mode that writes nothing.
Instructions
Cut this timeline into shorts, each a new project beside this one.
For a footage dump: seed every recording (seed_timeline takes a list),
clean it once (cut_by_transcript, verify), then split. Which shorts
there are and where each starts is your reading of the transcripts. Each
short is reel over its span, so everything reel reports comes back
per short, and each also leaves out the recordings it does not use
(clips_dropped).
overlaps (two shorts sharing material) and unassigned (timeline spans
no short holds — a take missed stays in the dump) are reported, never
refused: read both. This server cannot reach a short once it exists, by
design; proofcut web --root <the dump's parent> lists them. plan=True
resolves every short and creates nothing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| into | No | The directory the shorts are created in. Unset, the dump's own parent, so they sit beside it. A bound server takes no other. | |
| path | No | The project directory to act on. Omit it — the usual case — when this server is bound to a project (started as `proofcut -C DIR mcp`, or inside a project; `ping` says which): it then resolves to that one bound project, a relative path resolves against it, and a path outside it is refused by name. Unbound, `path` is the whole address and omitting it refuses rather than guessing. | |
| plan | No | Resolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it. | |
| canvas | No | The shape to set on every short, e.g. `1080x1920` — one delivery shape for the batch. The dump keeps its own. | |
| shorts | Yes | Every short, in order: `{name, from, to}` where `from` is its first word and `to` its last, each `{clip_id, word_index}` or `{clip_id, phrase}` (plus `occurrence` for a repeated phrase); or `{name, start, end}` in the render seconds `reel` takes. `name` is one directory name, created beside the dump, and must not exist. | |
| confirm_suspect | No | Go ahead even though a boundary word claims a suspect duration. Read the echoed words first — a suspect duration usually means whisper hid a retake inside that word, so the edge is not where it reads. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||