feat(render-pipeline): validation, QC and delivery builder
Completes RenderPipeline2 phases 3-5. Additive throughout: with validation.enabled=false the pipeline behaves exactly as before. Validation (§8) runs on the worker straight after a render, while it still holds the job and the files are local. Everything is read from the EXR header — one 64 KB read per sampled frame, no pixel decode — so the engine needs no oiiotool. The render job deliberately stays open through the stage, so a worker that dies there is reaped and retried instead of stranding the export in VALIDATING. Timecode is the primary check and is anchored on the plate, never the API: measured on the live show, Shot.timecodeStart is the editorial in-point and sits one handle-length (8f) ahead of the plate, so checking against it would pass the defective exports and fail the correct ones. Reference precedence is manifest timing plate -> plate found on disk -> API value, and the API rank is WARN-only. The panel now resolves plate provenance by walking the comp's own footage layers, so the worker never guesses which element carries the comp's timing. Verified against real studio renders via the new --validate mode: it catches both defect classes seen in shipped work — the +8 handle offset and frame-derived timecode (00:00:41:17 = frame 1001 at 24fps). QC (§10) is one service behind two front doors, API-key for the panel and session for the web. PASS means ready to upload and nothing else; FAIL sets the comp task to CHANGES. The panel gains a QC section that imports the real EXR sequence at full res rather than the H.264. Delivery (§11) rides the existing queue as a DELIVERY_BUILD job: hard links with a copy fallback, verification by re-hashing delivered bytes against the validation-time digest, manifest.json and the CSV report. fsutil hardlink list is unavailable over SMB, so link identity is never queried — reading the bytes back covers links and copies alike. Also fixes ApiClient.ProgressAsync throwing on transport failure, which would have aborted work in flight during a brief server outage; progress reporting is best-effort by contract. Removes the stale RenderWorker/ rule from the root .gitignore. The worker's source is tracked like the rest of the repo and its own .gitignore already covers bin/, obj/ and publish/; the rule silently excluded new files while the existing 20 stayed tracked. Not yet applied: migration 20260813000000 was hand-written because the dev database was unavailable — run prisma migrate deploy and verify before relying on it. None of this has run against a live server. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
+91
-5
@@ -123,13 +123,15 @@ Same applies to `footageRoot`: change `V:/_FOOTAGE/UNG` → `V:/_FOOTAGE`.
|
||||
|
||||
## Panel Layout
|
||||
|
||||
The panel is divided into five sections:
|
||||
The panel is divided into seven sections:
|
||||
|
||||
1. **Shot Builder** — Episode/shot selection and comp creation
|
||||
2. **Actions** — Per-shot and batch operations
|
||||
3. **Workspace** — One-time project initialisation
|
||||
4. **Color Space** — OCIO effect management
|
||||
5. **Status** — Live feedback on selected comps and last action
|
||||
2. **Render Pipeline** — Queue Export, status polling, retry, regenerate previews
|
||||
3. **QC** — Technical QC queue for rendered exports
|
||||
4. **Actions** — Per-shot and batch operations
|
||||
5. **Workspace** — One-time project initialisation
|
||||
6. **Color Space** — OCIO effect management
|
||||
7. **Status** — Live feedback, plus Diagnostics and the last report
|
||||
|
||||
---
|
||||
|
||||
@@ -154,6 +156,28 @@ Constructs a full shot composite in the open AE project from the episode and sho
|
||||
7. Calls **Add Overlay** logic to attach the `UNG_VFX_OVERLAY` comp.
|
||||
8. Organises items into `__SHOTS/{episodeCode}`, `_FOOTAGE_4K`, and `_PRECOMPS` project folders.
|
||||
|
||||
If any step fails, the status line names the stage and a copyable report opens —
|
||||
see [Diagnostics and logging](#diagnostics-and-logging).
|
||||
|
||||
---
|
||||
|
||||
## QC
|
||||
|
||||
Technical QC on the **rendered EXRs**, not the H.264 preview — the point is
|
||||
catching mask slips, export glitches and metadata faults at full resolution.
|
||||
QC is per-export: a new export always needs new QC.
|
||||
|
||||
| Control | Behaviour |
|
||||
|---|---|
|
||||
| **Load QC Queue** | Lists every export in `READY_FOR_QC` for the selected project, oldest first. Entries flagged with a warning count had a non-blocking validation warning worth a closer look. |
|
||||
| **Open Render** (or double-click) | Imports that export's actual EXR sequence into a `QC_{shot}_{version}` comp at full res and opens it. Re-selecting an already-imported shot just reopens the comp. |
|
||||
| **Notes** | Sent with the decision. Optional on pass; a fail with no notes asks for confirmation, because the artist only sees what you write here. |
|
||||
| **QC Pass** | Marks the version **ready for delivery** and nothing else — nothing is shared to the client, no approval state changes, no task moves. |
|
||||
| **QC Fail** | Sets the export to `QC_FAILED` and the comp task to **CHANGES**. The artist fixes and queues a new version; the old export is superseded. |
|
||||
|
||||
Passing an export is what makes it eligible for a delivery package on the web
|
||||
app's **Pipeline → Deliveries** page.
|
||||
|
||||
---
|
||||
|
||||
## Actions
|
||||
@@ -402,3 +426,65 @@ The **Status** panel at the bottom of the UI shows two lines:
|
||||
- **Line 2** — Result or progress message from the last operation.
|
||||
|
||||
Both lines are updated throughout batch operations so progress is visible in real time.
|
||||
|
||||
Below them are two buttons:
|
||||
|
||||
- **Diagnostics** — runs the environment self-test described below.
|
||||
- **Show Last Report** — re-opens the trace from the last button pressed.
|
||||
|
||||
---
|
||||
|
||||
## Diagnostics and logging
|
||||
|
||||
Every button press is traced: what it tried, in what order, with the paths and
|
||||
HTTP codes it was working with. The trace goes to an in-memory buffer and to a
|
||||
log file, and it is shown automatically when something fails.
|
||||
|
||||
**Log file:** `%APPDATA%/VFXReviewConnector/connector.log` (next to `config.json`).
|
||||
It is truncated once it passes 1 MB, so it can always be pasted into a message.
|
||||
The API token is never written to it — only whether one is set.
|
||||
|
||||
### When Build Shot fails
|
||||
|
||||
The status line now names the stage it failed at, and a scrollable report opens
|
||||
with the whole trace. The stages, and what each one means:
|
||||
|
||||
| Stage | Meaning | Usual fix |
|
||||
|---|---|---|
|
||||
| `project` | No project selected in the panel | The project dropdown is empty because the server URL or token is wrong |
|
||||
| `shot lookup` | The server returned no shot record | Report shows the HTTP code: `0` = server unreachable, `401/403` = bad token, `404` = shot not in that project |
|
||||
| `configuration` | Footage Root is blank in Settings | Settings are **per-machine**; a fresh workstation starts blank |
|
||||
| `footage folder` | The show/episode folder does not exist here | Report names the deepest folder that *does* exist — usually an unmapped drive or a different drive letter/UNC on that machine |
|
||||
| `plate folders` | Folder exists, no plates for that shot code | Report lists the folders that *are* there, so a naming mismatch is visible |
|
||||
| `plate import` | Plate folders matched but held no importable EXRs | Report lists each folder's contents (`n .exr, n other files`) |
|
||||
| `comp creation` | After Effects threw while building the comps | Not a path or server problem — the AE error text is in the report |
|
||||
| `unexpected error` | Anything thrown that was not anticipated | Report carries the error text, line number and stack |
|
||||
|
||||
Non-fatal conditions are traced too rather than passing silently: a missing
|
||||
`_SHOW LUT`, an overlay that could not be applied, a missing `__SHOTS/{group}`
|
||||
folder.
|
||||
|
||||
### Diagnostics button
|
||||
|
||||
Checks everything Build Shot depends on **without building anything**, so a
|
||||
workstation can be cleared before an artist is blocked. It verifies:
|
||||
|
||||
1. `curl.exe` is present and runnable (every server call goes through it).
|
||||
2. Server URL and API token are set, and `GET /api/ext/projects` succeeds.
|
||||
3. Footage Root resolves to a folder that exists, and lists the plate folders
|
||||
found for the currently selected shot.
|
||||
4. Export Root resolves to a folder that exists.
|
||||
5. The shot lookup succeeds for the currently selected shot.
|
||||
6. The open AE project has `UNG_VFX_OVERLAY`, `UNG_EXPORT_TEMPLATE`,
|
||||
`_SHOW LUT`, and the `__SHOTS` / `_FOOTAGE_4K` / `_PRECOMPS` / `_PREVIEWS`
|
||||
folders.
|
||||
|
||||
Each failure is reported as a `PROBLEM` line with the offending path or HTTP
|
||||
response, and the report ends with a problem count.
|
||||
|
||||
### Errors that used to be invisible
|
||||
|
||||
ScriptUI silently swallows exceptions thrown inside a button handler, so a hard
|
||||
failure looked like a button that did nothing at all. Every handler is now
|
||||
wrapped: anything thrown is caught, logged with its line number and stack, shown
|
||||
in the status line, and surfaced in the report dialog.
|
||||
|
||||
Reference in New Issue
Block a user