Skip to content

KORG M3R V1.1 MIDI CC chart, NRPN and OSC map

The KORG M3R V1.1 MIDI implementation: 6 CC, 58 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.

Device KORG M3R V1.1
Vendor KORG
OSC prefix /m3r_v1_1
Source πŸŽ›οΈ Derived from an Electra One community preset
Revision per Electra preset
Upstream electra-preset
Driver file devices/korg/m3r_v1_1.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/korg/m3r_v1_1.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /m3r_v1_1/hold 63

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

MIDI CC and NRPN parameters (6)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/m3r_v1_1/hold 64 0–127 continuous
/m3r_v1_1/modwh_js_up_1 1 0–127 continuous
/m3r_v1_1/js_down_2 2 0–127 continuous
/m3r_v1_1/volume_7 7 0–127 continuous
/m3r_v1_1/rotary_sp_80 80 0–127 continuous
/m3r_v1_1/all_notes_off 127 0–127 continuous

SysEx commands (58)

OSC address Arguments
/m3r_v1_1/multisound val: u7
/m3r_v1_1/drum_kit val: u7
/m3r_v1_1/octave val: u7
/m3r_v1_1/assign val: u7
/m3r_v1_1/hold val: u7
/m3r_v1_1/osc_level val: u7
/m3r_v1_1/osc_type val: u7
/m3r_v1_1/mg1_wave val: u7
/m3r_v1_1/frequency val: u7
/m3r_v1_1/delay val: u7
/m3r_v1_1/mg1_intensity val: u7
/m3r_v1_1/key_sync val: u7
/m3r_v1_1/eg_lvl_v_sens val: u7
/m3r_v1_1/eg_time_v_sens val: u7
/m3r_v1_1/delay_start val: u7
/m3r_v1_1/attack_time val: u7
/m3r_v1_1/decay_time val: u7
/m3r_v1_1/release_time val: u7
/m3r_v1_1/start_level val: u7
/m3r_v1_1/attack_level val: u7
/m3r_v1_1/release_level val: u7
/m3r_v1_1/pb_pitch val: u7
/m3r_v1_1/at_pitch val: u7
/m3r_v1_1/pitch_mg val: u7
/m3r_v1_1/mg_freq val: u7
/m3r_v1_1/cutoff val: u7
/m3r_v1_1/attack val: u7
/m3r_v1_1/decay val: u7
/m3r_v1_1/slope_time val: u7
/m3r_v1_1/release val: u7
/m3r_v1_1/eg_intensity val: u7
/m3r_v1_1/breakpoint val: u7
/m3r_v1_1/sustain val: u7
/m3r_v1_1/cutoff_kbd_trk val: u7
/m3r_v1_1/eg_time_kb_trk val: u7
/m3r_v1_1/center_key val: u7
/m3r_v1_1/mg2_wave val: u7
/m3r_v1_1/mg2_intensity val: u7
/m3r_v1_1/pb_cutoff val: u7
/m3r_v1_1/at_cutoff val: u7
/m3r_v1_1/cutoff_mg val: u7
/m3r_v1_1/amp_lvl_v_sens val: u7
/m3r_v1_1/amp_kbd_trk val: u7
/m3r_v1_1/at_amp val: u7
/m3r_v1_1/vdf_eg_int val: u7
/m3r_v1_1/combi_type val: u7
/m3r_v1_1/program val: u7
/m3r_v1_1/pan val: u7
/m3r_v1_1/damper_filter val: u7
/m3r_v1_1/split_point val: u7
/m3r_v1_1/velocity_sw val: u7
/m3r_v1_1/level val: u7
/m3r_v1_1/interval val: u7
/m3r_v1_1/detune val: u7
/m3r_v1_1/keyzone_top val: u7
/m3r_v1_1/keyzone_bottom val: u7
/m3r_v1_1/velocity_high val: u7
/m3r_v1_1/velocity_low val: u7

Performance MIDI

Notes, pitch bend and any CC are also available: /m3r_v1_1/note/on <note> <velocity>, /m3r_v1_1/cc/<number> <value>, /m3r_v1_1/pitchbend <0-16383>, /m3r_v1_1/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

How many parameters of the KORG M3R V1.1 can be controlled over MIDI?

SynthHub's map of the KORG M3R V1.1 lists 6 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 M3R V1.1?

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