OSC bridge:
how tonee talks to Live.
tonee controls Ableton Live through AbletonOSC, a MIDI Remote Script that runs inside Live and exposes its full Python API over UDP. This page explains how it works and what to check if something breaks.
01 /What it is
AbletonOSC is a MIDI Remote Script: a Python script that runs inside Ableton Live as a control surface. It listens for Open Sound Control (OSC) messages over UDP and translates them into calls on Ableton's Live Object Model. That's how tonee can rename a track, add a compressor, or write MIDI notes without any screen automation.
tonee ships with AbletonOSC bundled and installs it for you. You don't need to download or configure it separately. Just point Live at it in preferences.
02 /Installation
tonee installs AbletonOSC automatically on first launch, into your Ableton User Library. It also checks for updates on every launch: if the bundled version is newer than what's installed, it updates silently.
03 /Enabling in Live
AbletonOSC needs to be selected as a control surface in Live's preferences. This is a one-time step.
04 /Ports & networking
All OSC traffic stays on localhost, so nothing is exposed to your network. No firewall rules needed.
Ports 11000 and 11001 are fixed: they're hardcoded in AbletonOSC and can't be changed without rebuilding the script. If another application is using those ports, it will conflict.
05 /How it all connects
When you send a message, here's the full path from your words to a change in Live:
What goes to the cloud is the structured snapshot of your set (track names, device chains, levels, and the notes inside your MIDI clips) plus the text of your message. Your project file and your samples stay put, and voice transcription runs entirely on-device. Audio only leaves when you start a capture yourself; see Listening.