Single-pass final and finishing post-steps #54

Closed
opened 2026-10-07 07:34:49 +00:00 by crowmaki · 0 comments
Owner

Parent

#24

What to build

A filmmaker can render a final straight away and get a real ProRes master. See User Stories 120, 135, 141 and 142.

Acceptance criteria

  • A Single-pass final runs h3.final at final size with no latent saved
  • Finals are a ProRes 422 HQ .mov written by the workflow; a CPU post-step stamps 01:00:00:00 and PCM audio and makes an H.264 proxy at short side 768 (h264_nvenc if a startup check finds it, else libopenh264)
  • A CPU post-step lane runs 1–2 at a time; preparation for the next job overlaps the current render; a Take shows Finishing until post-steps are done
  • A failed post-step keeps the GPU output with a "proxy missing" marker and a retry action
  • Tests cover the final graph, timecode and proxy outputs (real ffmpeg with libopenh264) and post-step failure

Blocked by

## Parent #24 ## What to build A filmmaker can render a final straight away and get a real ProRes master. See User Stories 120, 135, 141 and 142. ## Acceptance criteria - [ ] A Single-pass final runs `h3.final` at final size with no latent saved - [ ] Finals are a ProRes 422 HQ `.mov` written by the workflow; a CPU post-step stamps `01:00:00:00` and PCM audio and makes an H.264 proxy at short side 768 (`h264_nvenc` if a startup check finds it, else `libopenh264`) - [ ] A CPU post-step lane runs 1–2 at a time; preparation for the next job overlaps the current render; a Take shows Finishing until post-steps are done - [ ] A failed post-step keeps the GPU output with a "proxy missing" marker and a retry action - [ ] Tests cover the final graph, timecode and proxy outputs (real ffmpeg with `libopenh264`) and post-step failure ## Blocked by - #51
Sign in to join this conversation.
No description provided.