production record

Production record

f000001a lone rooftop HVAC unit on a vast flat roof, aerial, minimal

What the facility logged of its own production: every sequence, every run, every stop. Kept for reference. None of it is required reading.

A sample render, not the delivery encode. The finished encode comes from pass-08, which is still rendering.

1536×1344side-by-side, image left / text right24 fps768×1344 per channel

Vertical, two channels side by side, 1536×1344.

pass 2 · sampled evenly, 0:00 to 30:00

Thirty stills sampled evenly across pass 2’s image channel. The full gallery holds 4,090, across every pass and treatment. Open any one in place — arrow keys step through, escape closes.

every pass on one axis · frame 1 to 43,200 · 0:00 to 30:00

frame 1 · 0:0021,600 · 15:0043,200 · 30:00

pass-011–6,319

pass-021–43,200

pass-03-rehearsal1–3,600

pass-04-rehearsal2–2,417

pass-05-rehearsal2–616

pass-06-rehearsal1 file

pass-07-rehearsal1–3,600

pass-082–12,884

verified by manifestobserved in the logno record

Vertical ticks mark chain breaks: single frames rendered from the written instruction alone, discarding the frame before. The chain restarts there.

Pass 2, measured

43,200frames, pass 2

30:00runtime

2channels

768×1344per channel

70 h 22 mgpu logged

5.87 sper frame

One GPU, one continuous feedback chain, roughly 5.9 seconds a frame. The pass 2 record holds every run and every render driver hash.

The record

Sequences8 recorded · frames, runs, render drivers, and what is verified Treatments12 recorded · derived from pass 2 Recipes9 recorded · schedule and vocabulary Design systemhow the record is drawn

How it was made

43,200frames

30:00runtime

2channels

768×1344per channel

70 h 22 mgpu logged

1gpu

One GPU — NVIDIA GeForce RTX 3090 Ti — running a continuous img2img feedback chain, roughly 5.9 seconds a frame across 43,200 frames. Every frame is the input to the next. Nothing is composited and nothing is re-timed.

The schedule is written before the render starts: one prompt line per frame, on a viewpoint axis that cycles aerial, front, side and three-quarter. The image channel was conditioned on each line plus a suffix the text channel never shows. You can read the whole schedule, frame by frame.

The second channel is that prompt rendered as text, frame-locked to the image by being produced in the same render driver iteration. Two independent stacks — separate sequences, directories, hashes and manifests — never composited.

It took three runs. Two ended badly: a Windows Update restart at frame 2,651, and a socket exhaustion bug at frame 10,636. Both are in the record, with what each cost and what was recovered. So is the fact that the render driver binary changed mid-pass. The sequence record holds all of it.

What this site is

A record, not a portfolio. Two systems with one boundary: the project record knows what the work means and emits a structured file; this site knows what that file looks like. Change the record and the exporter changes. Restyle the site and the record never notices.

Every figure here is generated from the record. When the render moves, one command refreshes every page.

record generated: 2026-09-16 02:24-07:00
project created: 2026-09-09 02:15-07:00 by the render node
passes updated: 2026-09-15 01:19-07:00

The same file is published as record.json. The render environment is withheld from it, and the file names the omission.

Gallery4,090 sampled stills, each named for its source frame Instruction logevery prompt, frame by frame, with the still beside it Sequenceswhat each render produced, and what verifies it Treatments12 derived works Design systemhow the record is drawn

Not published

per-frame sampler seeds

The render log holds the prompt, sampler seed and applied denoise of every frame. That is a complete reproduction recipe, so the schedule and the summary statistics are here and the seeds are not. Available on request.

the masters

The project is 244 GB and the 30-minute ProRes master is 32 GB. Frames and masters are named, sized and hashed throughout this site, never copied into it.

previews are not deliverables

Each pass carries review encodes in passes/<pass>/previews, ProRes 4444 (yuv444p10le), intra-only. They are not the delivery encode.