Skip to content
Filippo Galbo

Creative technology / active

AI-BletonGuy

Translate musical instructions into typed Ableton Live actions that can be checked before execution.

Back to work

The problem

A musical instruction can refer to several tracks, devices, or edits. Acting on an ambiguous interpretation can change the wrong part of a live set.

My role

Desktop interface, language-to-action planning, and Ableton bridge engineering.

What I built

  • Desktop musical-command interface
  • Typed action plans and execution checks
  • Ableton bridge controls

The result

A local Ableton-control implementation with tested components for interpreting and checking actions before they reach the session.

Control-flow illustration of musical intent, typed action plans, validation, and the Ableton bridge. Not a captured Ableton interface.
Control-flow illustration of musical intent, typed action plans, validation, and the Ableton bridge. Not a captured Ableton interface.

Statusactive

Evidencetested

Record reviewed

Implementation

How it works

The desktop application parses natural-language input into a typed action plan, applies execution checks, and sends accepted actions through an Ableton bridge. Local-model routing and bridge failures remain visible to the operator.

Technical context and methods

The implementation includes desktop controls, bridge layers, safety rules, and operator documentation. Camera-to-MIDI and pose controls are separate experiments within the project.

  • Python
  • PySide6
  • AbletonOSC
  • Local-model routing
  • Voice input
  • Preview-diff execution
  • Session snapshots