Back to corpus
working paperpreprint structure candidatescore 76

Computational Choreography: A Dense Manuscript for the LUME Stack

Computational choreography is the name for the layer of LUME that interprets a performer's body as a live compositional instrument. It is not a synonym for motion capture, gesture recognition, depth rendering, or visual reactivity, although it depends on all of them. It is the discipline of deciding what the machine believes about the body, how that belief changes over time, how movement becomes intention, and how intention becomes a bounded visual or musical event. The current LUME stack already contains the physi

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Computational choreography is the name for the layer of LUME that interprets a performer's body as a live compositional instrument. It is not a synonym for motion capture, gesture recognition, depth rendering, or visual reactivity, although it depends on all of them. It is the discipline of deciding what the machine believes about the body, how that belief changes over time, how movement becomes intention, and how intention becomes a bounded visual or musical event. The current LUME stack already contains the physical and computational materials for such a system: Femto/Mega depth gives the real visible body, Sony mocopi gives a motion backbone, MotionMix gives a distributed body-state and camera mesh, Unity DYK gives the live pCloud performance host, the web fluid lab gives a fast experimental surface, rehearsal capture gives the training archive, and K11 AirDeck gives a separate safety-gated DJ control path. The task now is to bind these parts into a choreographic stack whose behavior is stable enough for performance, expressive enough to approach the Duncan reference direction, and introspective enough to learn Mo's movement vocabulary over time.

Promotion decision

What has to happen next

Convert into the standard paper schema, add citations, and render a draft PDF.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.