Skip to content

KORG opsix (per pencilresearch canonical CSV) MIDI CC chart, NRPN and OSC map

The KORG opsix MIDI implementation: 39 CC, each named, for Claude (MCP), SuperCollider or any OSC app.

Device KORG opsix
Vendor KORG
OSC prefix /opsix
Source πŸ“¦ Derived from MIDI Guide (community CC/NRPN data)
Firmware unknown
Revision per pencilresearch canonical CSV
Upstream pencilresearch
Data licence CC-BY-SA-4.0 β€” MIDI Guide (https://midi.guide) by Pencil Research and contributors
Driver file devices/korg/opsix.pencilresearch.fw-unknown.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.

Other versions of the KORG opsix (1)

per Electra preset

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/korg/opsix.pencilresearch.fw-unknown.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /opsix/algorithm 63

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as opsix: ask β€œwhat can the KORG opsix do?” and it reads this map with list_routes. See the MCP guide.

MIDI CC and NRPN parameters (39)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/opsix/algorithm 70 0–127 continuous
/opsix/op1_lvl 102 0–127 continuous
/opsix/op2_lvl 103 0–127 continuous
/opsix/op3_lvl 104 0–127 continuous
/opsix/op4_lvl 105 0–127 continuous
/opsix/op5_lvl 106 0–127 continuous
/opsix/op6_lvl 107 0–127 continuous
/opsix/op1_ratio 108 0–127 continuous
/opsix/op2_ratio 109 0–127 continuous
/opsix/op3_ratio 110 0–127 continuous
/opsix/op4_ratio 111 0–127 continuous
/opsix/op5_ratio 112 0–127 continuous
/opsix/op6_ratio 113 0–127 continuous
/opsix/attack 73 0–127 continuous
/opsix/decay_release 79 0–127 continuous
/opsix/filter_cutofff 74 0–127 continuous
/opsix/resonance 71 0–127 continuous
/opsix/fx1 81 0–127 continuous
/opsix/fx2 82 0–127 continuous
/opsix/fx3 83 0–127 continuous
/opsix/uni_cc12 12 0–127 continuous
/opsix/uni_cc13 13 0–127 continuous
/opsix/uni_cc14 14 0–127 continuous
/opsix/uni_cc15 15 0–127 continuous
/opsix/uni_cc16 16 0–127 continuous
/opsix/bip_cc17 17 0–127 continuous
/opsix/bip_cc18 18 0–127 continuous
/opsix/bip_cc19 19 0–127 continuous
/opsix/bip_cc20 20 0–127 continuous
/opsix/bip_cc21 21 0–127 continuous
/opsix/modwheel 1 0–127 continuous
/opsix/gldetime 5 0–127 continuous
/opsix/volume 7 0–127 continuous
/opsix/pan 10 0–127 continuous
/opsix/expression 11 0–127 continuous
/opsix/damper 64 0–127 continuous
/opsix/glide_mode 65 0–127 continuous
/opsix/sostenuto 66 0–127 continuous
/opsix/soft 67 0–127 continuous

Performance MIDI

Notes, pitch bend and any CC are also available: /opsix/note/on <note> <velocity>, /opsix/cc/<number> <value>, /opsix/pitchbend <0-16383>, /opsix/program_change <n>.

Limitations

CC/NRPN only. SysEx (preset management, display control, bulk dump/load, vendor-proprietary opcodes) is NOT covered by pencilresearch. To extend this device with SysEx, sniff the vendor editor, add `sysex.header/footer` + `commands` blocks, and use `update_device.md` PR template.

Frequently asked questions

Which MIDI CC controls the filter cutoff on the KORG opsix?

CC 74 (0–127), named /opsix/filter_cutofff in SynthHub's map.

How many parameters of the KORG opsix can be controlled over MIDI?

SynthHub's map of the KORG opsix lists 39 MIDI CC parameters, each with its number, range and a readable name; the full chart is on this page.

Can an AI agent like Claude control the KORG opsix?

Yes: SynthHub's hosted MCP server knows the KORG opsix's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.