devices/korg/padkontrol.vendor.fw-unknown.jsonEdit on GitHubJSONKORG padKONTROL MIDI CC chart, NRPN and OSC map
The KORG padKONTROL MIDI implementation: 10 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- real unitnot yet checked
Not checked on a real KORG padKONTROL yet. Own one? Load a sound or send a control, and tell us whether it worked.
- Maker
- KORG
- Version
- padKONTROL MIDI Implementation (Native Mode), 2005.08.25
- Source
- maker's documentation
- OSC prefix
/padkontrol
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/korg/padkontrol.vendor.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 padkontrol: ask “what can the KORG padKONTROL do?” and it reads this map with list_routes. See the MCP guide.
MIDI controls
10 controls, each with its number, its range and the name to send
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| Identity request | /padkontrol/identity/request |
|
| Native enter | /padkontrol/native/enter |
|
| Native exit | /padkontrol/native/exit |
|
| Native led | led: u7, state: enum, timer: u7 | /padkontrol/native/led |
| Native display | blink: u7, c1: u7, c2: u7, c3: u7 | /padkontrol/native/display |
| Dump current scene request | /padkontrol/dump/current_scene/request |
|
| Dump global request | /padkontrol/dump/global/request |
|
| Scene write | scene: u7 | /padkontrol/scene/write |
| Scene change | scene: u7 | /padkontrol/scene/change |
| Port detect request | port: u7 | /padkontrol/port_detect/request |
Performance MIDI
Notes, pitch bend and any CC are also available: /padkontrol/note/on <note> <velocity>, /padkontrol/cc/<number> <value>, /padkontrol/pitchbend <0-16383>, /padkontrol/program_change <n>.
Limitations
Source: padKONTROL MIDI Implementation (Native Mode), 2005. Outside native mode the padKONTROL sends what its scene assigns (notes, CCs, bend, aftertouch per TABLE 1); those arrive through the performance routes. Native-mode Packet Communication 1 and 2 (command 3F, 38 and 17 data bytes, TABLES 3-4) and sending scene or global dumps back (func 40/51, packed data) are not exposed: their payloads are whole tables. Dumps are requested only and arrive as /sysex/raw. The document does not name the switches behind numbers 00-12 nor the LEDs 10-22 and 30-47 one by one. Untested on hardware.
Frequently asked questions
Can an AI agent like Claude control the KORG padKONTROL?
Yes: SynthHub's hosted MCP server knows the KORG padKONTROL's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.