feat(pipeline): automate picture-lock trimming in the preview build
Deploy / deploy (push) Successful in 10m37s

Previews used to ship the full padded (handle-included) render to
clients, with an artist manually pulling picture lock and hand-trimming
the comp to match. The automated preview stage now trims the client
comp to the picture-lock edit itself (a fixed handle count off each
end, per the studio's existing convention) and separately builds an
ungraded, full-duration picture-lock reference MP4 as a diagnostic
sidecar to check back against. A new "No Picture Lock" panel checkbox
is the single override for shots where picture lock is missing or
wrong, falling back to today's untrimmed behavior.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
twotalesanimation
2026-08-22 12:59:05 +02:00
parent 82dfaee56f
commit 86962eb4bd
14 changed files with 328 additions and 14 deletions
+3 -1
View File
@@ -5,7 +5,7 @@ import { createExport } from "@/lib/render-pipeline/exports";
// ── POST /api/ext/exports (E1 — Queue Export) ────────────────────────────────
//
// Body: { manifest: RenderManifest, submittedByEmail?, priority?, force?, skipPreview? }
// Body: { manifest: RenderManifest, submittedByEmail?, priority?, force?, skipPreview?, noPictureLock? }
// The server decides the new version number, updates Shot.shotVersion/exrOutput,
// supersedes older non-terminal exports, and creates Export(QUEUED) + RenderJob.
@@ -21,6 +21,7 @@ export async function POST(req: NextRequest) {
vfxScope?: string | null;
submissionNote?: string | null;
skipPreview?: boolean;
noPictureLock?: boolean;
};
try {
body = await req.json();
@@ -40,6 +41,7 @@ export async function POST(req: NextRequest) {
vfxScope: body.vfxScope,
submissionNote: body.submissionNote,
skipPreview: body.skipPreview === true,
noPictureLock: body.noPictureLock === true,
});
return NextResponse.json(result, { status: 201 });
} catch (err) {