Docs

FrameLathe is built as a queue, not a single-clip click-and-wait tab.

Drop files or a folder. Answer what is wrong, where it is going, and how long it can take. Start the batch. The GPU can work overnight. In the morning you review a wipe and keep the take you want.

Intent budgets

The rail talks about time in three chips. They are planning hints, not SLAs:

• Quick — about 40 minutes
• Full — about 4 hours
• Best possible — the best pass for this source

Actual duration depends on resolution, preset, and the card. Clean 8K is in a different league — read the row estimate before you start one.

The door picks a preset from those answers. Show the recipe opens the rest of the rail — the catalog, Also fix, delivery — on exactly what the door just said.

Compose vs delivered

The rail is a compose door for pending and paused clips, and for All pending / Future imports. Those two scopes live on the recipe rail, next to the door they aim. A delivered clip is a receipt: what ran, not three questions. Change the recipe from Review if you want another pass.

Interrupted runs

If you quit while a row is running, the next launch pauses that row at a checkpoint. Start / Resume continues it. Cancel / Remove can drop it. You do not lose the overnight because the window closed.

History

Finished clips — delivered, failed, or cancelled — show in History as soon as they finish. That list is the recipe (preset, extras, where it wrote), not a second copy of the video. Clear done on the queue files them off the live list; they stay in History for 90 days.

Tray and recap

Overnight runs are meant to outlive a focused session. The app can sit in the tray and surface a morning recap of what finished. Exact chrome depends on the build you installed; the contract is local files in, local files out.