devices/motu/midi_timepiece_av.electra-martin-wip.fw-unknown.jsonEdit on GitHubJSONMOTU MIDI Timepiece AV MIDI CC chart, NRPN and OSC map
The MOTU MIDI Timepiece AV MIDI implementation: 2 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourceElectra One preset
- real unitnot yet checked
Not checked on a real MOTU MIDI Timepiece AV yet. Own one? Load a sound or send a control, and tell us whether it worked.
- Maker
- MOTU
- Version
- per Electra preset
- Source
- Electra One preset
- OSC prefix
/midi_timepiece_av
Use it
Find the MIDI ports, then start the bridge with this driver:
osc-bridge detect # prints the ready-to-run line for what is plugged in
osc-bridge run --device devices/motu/midi_timepiece_av.electra-martin-wip.fw-unknown.json --out-port <N> --in-port <M>
Then send OSC to 127.0.0.1:7777, for example:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as midi_timepiece_av: ask “what can the MOTU MIDI Timepiece AV do?” and it reads this map with list_routes. See the MCP guide.
MIDI controls
2 controls, each with its number, its range and the name to send
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| Remap | val: u7 | /midi_timepiece_av/remap |
| Mute | val: u7 | /midi_timepiece_av/mute |
Performance MIDI
Notes, pitch bend and any CC are also available: /midi_timepiece_av/note/on <note> <velocity>, /midi_timepiece_av/cc/<number> <value>, /midi_timepiece_av/pitchbend <0-16383>, /midi_timepiece_av/program_change <n>.
Limitations
Imported from an Electra One community preset. The mapping reflects the preset author's editorial choices: parameter naming, ranges, and which params are exposed. Untested on hardware in this repo.
Frequently asked questions
Can an AI agent like Claude control the MOTU MIDI Timepiece AV?
Yes: SynthHub's hosted MCP server knows the MOTU MIDI Timepiece AV's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.