nothing but datacenters the record

treatment record

glitch-02

The CV layer composited onto the source FIRST, then torn by the glitch matrix. comfyglitch order 'under': HUD drawn before displacement, so it tears with the image rather than sitting cleanly on top of it.

status
test pass
upstream
pass-02 frames 1–1,440
evidence
A lossless frame sequence was written and manifested; the video is derived from it.
frame 1 · 0:0021,600 · 15:0043,200 · 30:00
glitch-021–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.

departs from the baseline

The kept dial-in used order 'reproject' (HUD read through the image's offset map). This is a deliberate departure, not a correction of it - glitch-01 and the kept baseline are untouched.

Upstream

pass
pass-02
frames
1–1,440
source
passes/pass-02/previews/pass-02.sbs.f000001-001440.mov
source sha256
f11ed0d68751

Render

composite
under
device
cpu
frames
1,440
clip length
7 m 02 s

Displacement layers

gridmax offsetanglesparsityjitterholdstaggerseedenvelope
4×33290°0.50.880.65none
8×7220.80.860.59none
20×18140.930.840.813none

What the detector found

model
yolo11n-seg.pt
confidence floor
0.15
detections
675
per frame
0.469
labeldetections
bench150
train62
person62
refrigerator37
umbrella32
airplane32
car31
suitcase25
boat24
kite23

Outputs

fileframesgeometryruntimebytessha256
previews/glitch-02.hud-under.f000001-001440.mp41–1,4401536x13441 m 00 s294.2 MBbe9ba4340173

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

Frame sequence

directory
frames/
files
1,440
bytes
2.0 GB
geometry
1536x1344
lossless
yes
manifest
frames-manifest.json

The treatment's record, the same way a pass's frames are its record. preview.mp4 is derived from these, not the other way round — extracting frames back out of it returns the codec's opinion of the pixels.

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.