treatment record

glitch-01

comfyglitch displacement + machine-vision HUD applied to Pass 2's published frames. Derived work: it consumes a pass, it is not one.

status: displacement rendered; HUD held pending a decision
upstream: pass-02 frames 1–1,440
evidence: Video only. No frame sequence was written, so the encode is the record.

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

glitch-011–1,440

Its window on pass 2's full 43,200-frame axis.

what it looks like · 12 frames

This treatment kept no sampled frames of its own, so these are the source frames it consumed — pass-02 1–1,440, before the treatment was applied.

Upstream

pass: pass-02
frames: 1–1,440
source: passes/pass-02/previews/pass-02.sbs.f000001-001440.mov
source sha256: f11ed0d68751
geometry: 1536x1344, image left / text right, 24fps
note: Pass 2 is still rendering. This treatment is pinned to the 1,440-frame prefix that was published and verified when it ran; a later treatment covers a longer prefix and does not replace this one.
why side by side: The look was dialled in against a 1536x1344 side-by-side, so a treatment fed the two channels separately would be working on different material than it was tuned on. The channels remain separate stacks on disk; this composite exists for the treatment and for viewing, and nothing writes back to the pass.

Outputs

file	frames	geometry	runtime	bytes	sha256
`previews/glitch-01.displacement.f000001-001440.mp4`	1–1,440	1536x1344	1 m 00 s	292.0 MB	`db36ade05b5f`

Named and hashed, not hosted. Nothing in this repository is a master.

Provenance

no task id

This treatment was run as a local process rather than dispatched through the mesh, so it has no task id, no lease and no event trail. That is a gap in the record, and it is recorded as one.

all treatments glitch-02 →