Back to corpus
research noteexperiment writeup candidatescore 20
How to Run the Voice Control System
```bash # Make sure you're in the project root (studio/) cd "[home]/Desktop/Computational Choreography/computational-studio/studio"
Full HTML reader
Read the full artifact
Extracted abstract or opening context
### Basic Commands - `"play left"` - Play left deck - `"pause right"` - Pause right deck - `"cue 1"` - Jump to cue point 1 - `"censor left"` - Apply censor effect
### Higher-Order Commands - `"play next"` - Load and play next track - `"continuous mode"` - Enable auto-play mode - `"transition left"` - Smooth transition to next track
### New Expressive Commands (with Intent Processor) - `"loop the vocal and fade it out slowly"` - Complex loop with fade - `"give me a long buildup"` - Transition with buildup - `"play something funky"` - Semantic search
### Semantic Search (with Library Indexer) - `"play some 90s hip hop"` - Find and play matching tracks - `"find something chill"` - Search by vibe - `"search for house music"` - Genre-based search
**Microphone Access:** - System Settings → Privacy & Security → Microphone - Enable access for Terminal (or your Python interpreter)
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
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.