docs/reference/Troubleshooting
troubleshooting:
when something goes wrong.
Common issues and how to fix them. If something isn't here, ask tonee directly. It knows its own limits.
01 /Connection problems
?tonee says "not connected"
Open Live's Settings → Link, Tempo & MIDI (Preferences in Live 11). Check that AbletonOSC is selected in one of the Control Surface slots. Use an empty slot, not one your controller is in. The status bar at the bottom of Live should read: "AbletonOSC: Listening for OSC on port 11000". If it's missing, remove and re-add the control surface.
?My controller stopped working after I set up tonee
AbletonOSC probably took over your controller's Control Surface slot. In Live's Settings → Link, Tempo & MIDI, choose your controller again in that slot and set its Input and Output back to your controller. Then put AbletonOSC in an empty slot with Input and Output set to None. Live runs both at once.
?Connected but tonee can't see my set
Make sure you have a set open in Live. AbletonOSC reads from the active document, so a blank or unopened project returns empty state.
?Was working, now disconnected mid-session
Live's remote scripts can deactivate if the app goes into the background for a long time or if Live is stressed. Re-select AbletonOSC in preferences (remove it, re-add it) without restarting Live. Send a test message after.
?Port conflict: 11000 or 11001 in use
Another application is using AbletonOSC's fixed ports. Identify it with "lsof -i :11000" (Mac) or Resource Monitor (Windows) and close it. The ports can't be changed.
02 /Commands not working
?I renamed a track in Live but tonee still uses the old name
tonee reads your set fresh on every message, so just send another message and it will see the new name. The snapshot is per-message, not continuous.
?tonee targeted the wrong track
Track names that are very similar (KICK vs KICK 808) can get confused, especially over voice. Use more specific names or reference by position: "the third track from the top".
?A change was confirmed but nothing happened in Live
This usually means the OSC message timed out because Live was busy (bouncing, loading a plugin). Try the command again. If it keeps failing, check that AbletonOSC is still active in preferences.
?tonee added notes but they're outside the clip and won't play
Notes can be written past the end of a clip's loop length. Extend the clip in Live (drag the clip end handle) to include them, or ask tonee to rewrite the pattern within the correct length.
03 /Undo issues
?"Undo" in tonee doesn't restore a deleted track or device
Track and device deletions are DESTRUCTIVE HEAVY: tonee can't reconstruct internal state (clips, presets, automation). Use ⌘Z in Live directly, immediately after the deletion, before making any other changes.
?Can't undo something from earlier in the session
tonee keeps the last 25 commits per session. Older ones fall off. If the commit you need is gone, ⌘Z in Live may still have it in its own history.
?Undo reverted more than I expected
Each tonee commit is atomic: everything in one agent execution is one undo unit. If the AI made 8 changes in one step, one undo reverts all 8. To undo part of it, redo (say "redo") and then make the specific change you want to keep.
04 /Voice issues
?Voice input doesn't activate
On Mac, check System Settings → Privacy & Security → Microphone, where tonee must be toggled on. On Windows, check Settings → Privacy → Microphone. Restart tonee after granting access.
?Transcription keeps mishearing track names or music terms
Abbreviations and producer shorthand are common misrecognitions. Spell out the full word when speaking, or edit the transcription in the input field before sending. It lands in the text box and you can correct it before hitting ⌘ Enter.
?Voice works in the app but not from the floating orb
The orb needs system-wide microphone permission. On Mac this is separate from app-level permission, so check System Settings → Privacy & Security → Microphone and verify the Electron app (not just the browser) has access.
?Wrong microphone being used
Go to Settings → Voice → Input device and select your preferred device. If your audio interface isn't listed, make sure it's set as the input device in your OS sound settings first.
05 /Known API limits
These aren't bugs. They're things Ableton's Python API doesn't expose. tonee will tell you when it hits one of these, rather than silently failing.
Send pre/post fader
Ableton's Python API doesn't expose this toggle. Set it manually in the mixer.
Per-track crossfader assign
A/B/none assignment per track isn't accessible via API. Use Live's UI.
Create group track
No Python API for group track creation. Use ⌘G in Live; tonee can read and fold groups once they exist.
Rack macro controls
Macro knobs on Instrument Racks, Audio Effect Racks, and Drum Racks are not accessible.
Rack chain contents
Individual chains inside racks can't be read or modified, only the top-level rack device.
Audio clip content
Sample data, waveforms, and file paths are not readable. Only clip name and type are exposed.
Device enable/disable
No bypass toggle. Devices are always active once added.
Not sure if something is supported? Just ask: "can you set the pre-fader on this send?" tonee knows what it can and can't do and will tell you directly.