treatment record

glitch-envelope-01

The first treatment whose intensity VARIES over time. All three displacement layers run envelope=cut, so max_offset is scaled per frame by proximity to a cut and settles to a 0.06 floor inside a shot — long stretches carry the CV overlay (contours, skeletons, id boxes) over an essentially clean image, and bursts of full displacement rise and decay over about 1.5s (cut-half-life 30).

status: test pass
upstream: pass-02 frames 1–3,600
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-envelope-011–3,600

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–3,600, before the treatment was applied.

departs from the baseline

Every earlier glitch treatment applied one constant effect for its whole runtime. The cuts here are not a metronome: pass-07's chain breaks — frames rendered at denoise 1.0, where the feedback chain is severed — register as frame-diff spikes of 36.9 to 75.6 against a median of 15.1, so threshold 32 puts the bursts on the compositional breaks. 96 cuts were found; shot lengths run 350 frames early and 3-7 frames late, which gives a natural intensity ramp matching the render's own arc.

Upstream

pass: pass-02
frames: 1–3,600
source: regenerable: hstack of passes/pass-07-rehearsal/{frames,text} 1-3600 (image left, text right)
source sha256: be311e6eb26b

Regenerating the source

ffmpeg -framerate 24 -start_number 1 -i frames/frame_%06d.png -framerate 24 -start_number 1 -i text/frame_%06d.png -frames:v 3600 -filter_complex '[0:v][1:v]hstack=inputs=2' -c:v prores_ks -profile:v 4 -pix_fmt yuv444p10le source.mov

Render

composite: under
device: cpu
frames: 3,600
clip length: 2 m 30 s
time to render it: 22 m 26 s
chunking: 160-frame windows, 23 of them, 124-frame lead-in discarded
overlay draws: box, mask, skeleton, face_mesh
overlay hold: 1 frame
stroke / bracket / label floor: 5 / 56 / 4,800 px²

Displacement layers

grid	max offset	angle	sparsity	jitter	hold	stagger	seed	envelope
4×3	32	90°	0.5	0.8	8	0.6	5	cut
8×7	22	0°	0.8	0.8	6	0.5	9	cut
20×18	14	0°	0.93	0.8	4	0.8	13	cut

What the detector found

model: yolo11n-seg.pt + yolo11n-pose.pt
confidence floor: 0.15
detections: 5,361
per frame: 1.489

label	detections
person	3,524
train	485
refrigerator	367
car	168
bench	149
suitcase	90
clock	65
potted plant	65
oven	57
tv	48

Outputs

file	frames	geometry	runtime	bytes	sha256
`previews/glitch-envelope-01.envelope-cut.f000001-003600.mp4`	1–3,600	1536x1344	2 m 30 s	741.9 MB	`4f0eafdff4ba`

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.

Note

Rendered LOCALLY, not through glitch_treatment, and deliberately: the render node was hours into the 53-hour pass-08 and the capability does not expose envelope flags, so adding them would have needed a node restart that killed the render. It therefore has no task id or lease. The capability should grow --cut-* and env= support before the next one.

← glitch-12 all treatments glitch-envelope-02 →