Purpose
Creative control tools often feel either too brittle for real performance work or too vague to trust when a command has real musical consequences.
creative code · active
AI-BletonGuy
Operator-first desktop copilot for Ableton Live. Translates natural-language intent into structured actions, safety checks, and performance-aware control instead of brittle automation hacks.
activePython + PySide6 + AbletonOSCNatural-language Ableton control with typed plans, execution checks, and live-session discipline.
My role
Designer and engineer
Status
active
Methods
- Python
- PySide6
- AbletonOSC
- Local-model routing
- Voice input
- Preview-diff execution
- Session snapshots
Outputs
- AI-BletonGuy parses natural language into typed action plans, validates them, and routes execution through bridge layers for Ableton-focused control. It also supports popup control, camera-to-MIDI experimentation, pose/visual modes, and safer local execution patterns.
Result
This is a serious machine-control project with real operator constraints: ambiguity handling, safety validation, local-model routing, and live creative control.
Implementation
How it works
AI-BletonGuy parses natural language into typed action plans, validates them, and routes execution through bridge layers for Ableton-focused control. It also supports popup control, camera-to-MIDI experimentation, pose/visual modes, and safer local execution patterns.
The working code lives in the ableton-language-agent workspace as a desktop control system with bridge layers, safety rules, packaging notes, and operator docs. This dossier narrows that surface to the part that matters publicly: turning vague musical intent into structured actions that can be reviewed before they touch a live set.