AKAI S-3000i MIDI CC chart, NRPN and OSC map¶
The AKAI S-3000i MIDI implementation: 39 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | AKAI S-3000i |
|---|---|
| Vendor | Akai |
| OSC prefix | /akai_s_3000i |
| Source | ποΈ Derived from an Electra One community preset |
| Revision | per Electra preset |
| Upstream | electra-preset |
| Driver file | devices/akai/akai_s_3000i.json |
Not tested on the device yet
This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone β see CONTRIBUTING.
How do you control 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/akai/akai_s_3000i.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 akai_s_3000i: ask βwhat can the AKAI S-3000i do?β and it reads this map with list_routes. See the MCP guide.
SysEx commands (39)¶
| OSC address | Arguments |
|---|---|
/akai_s_3000i/semi_tone |
val: u7 |
/akai_s_3000i/tune |
val: u7 |
/akai_s_3000i/volume |
val: u7 |
/akai_s_3000i/filter_offset |
val: u7 |
/akai_s_3000i/pan |
val: u7 |
/akai_s_3000i/sysex_message |
val: u7 |
/akai_s_3000i/cutoff |
val: u7 |
/akai_s_3000i/resonance |
val: u7 |
/akai_s_3000i/key_follow |
val: u7 |
/akai_s_3000i/mod_1_source |
val: u7 |
/akai_s_3000i/mod_2_source |
val: u7 |
/akai_s_3000i/mod_3_source |
val: u7 |
/akai_s_3000i/env_2_vcf |
val: u7 |
/akai_s_3000i/env_key_follow |
val: u7 |
/akai_s_3000i/mod_1_amount |
val: u7 |
/akai_s_3000i/mod_2_amount |
val: u7 |
/akai_s_3000i/mod_3_amount |
val: u7 |
/akai_s_3000i/program_level |
val: u7 |
/akai_s_3000i/indiv_out |
val: u7 |
/akai_s_3000i/indiv_send |
val: u7 |
/akai_s_3000i/velocity |
val: u7 |
/akai_s_3000i/mod_source |
val: u7 |
/akai_s_3000i/mod_amount |
val: u7 |
/akai_s_3000i/waveform |
val: u7 |
/akai_s_3000i/speed |
val: u7 |
/akai_s_3000i/depth_overall |
val: u7 |
/akai_s_3000i/delay |
val: u7 |
/akai_s_3000i/desync |
val: u7 |
/akai_s_3000i/retrigger |
val: u7 |
/akai_s_3000i/env_1_vca |
val: u7 |
/akai_s_3000i/lfo_1_amount |
val: u7 |
/akai_s_3000i/attack |
val: u7 |
/akai_s_3000i/time_1_2 |
val: u7 |
/akai_s_3000i/time_2_sustain |
val: u7 |
/akai_s_3000i/release |
val: u7 |
/akai_s_3000i/level_1 |
val: u7 |
/akai_s_3000i/level_2 |
val: u7 |
/akai_s_3000i/sustain |
val: u7 |
/akai_s_3000i/level_4 |
val: u7 |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /akai_s_3000i/note/on <note> <velocity>, /akai_s_3000i/cc/<number> <value>, /akai_s_3000i/pitchbend <0-16383>, /akai_s_3000i/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 AKAI S-3000i?
Yes: SynthHub's hosted MCP server knows the AKAI S-3000i's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.