Behringer PRO VS m MIDI CC chart, NRPN and OSC map¶
The Behringer PRO VS m MIDI implementation: 30 CC, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | Behringer PRO VS m |
|---|---|
| Vendor | Behringer |
| OSC prefix | /pro_vs_m |
| Source | 🎛️ Derived from an Electra One community preset |
| Revision | per Electra preset |
| Upstream | electra-preset |
| Driver file | devices/behringer/pro_vs_m.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/behringer/pro_vs_m.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 pro_vs_m: ask “what can the Behringer PRO VS m do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (30)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/pro_vs_m/corse_tuning |
115 | 0–99 | continuous | ||
/pro_vs_m/corse_tuning |
116 | 0–99 | continuous | ||
/pro_vs_m/corse_tuning |
117 | 0–99 | continuous | ||
/pro_vs_m/corse_tuning |
118 | 0–99 | continuous | ||
/pro_vs_m/wave |
24 | 0–127 | continuous | ||
/pro_vs_m/wave |
25 | 0–127 | continuous | ||
/pro_vs_m/fine_tuning |
111 | 0–99 | continuous | ||
/pro_vs_m/fine_tuning |
112 | 0–99 | continuous | ||
/pro_vs_m/fine_tuning |
113 | 0–99 | continuous | ||
/pro_vs_m/fine_tuning |
114 | 0–99 | continuous | ||
/pro_vs_m/wave |
26 | 0–127 | continuous | ||
/pro_vs_m/wave |
27 | 0–127 | continuous | ||
/pro_vs_m/rate |
72 | 0–99 | continuous | ||
/pro_vs_m/amount |
80 | 0–99 | continuous | ||
/pro_vs_m/rate |
73 | 0–99 | continuous | ||
/pro_vs_m/amount |
28 | 0–99 | continuous | ||
/pro_vs_m/modulation |
1 | 0–100 | continuous | ||
/pro_vs_m/get_preset |
124 | 0–127 | continuous | ||
/pro_vs_m/attack |
85 | 0–99 | continuous | ||
/pro_vs_m/attack |
86 | 0–99 | continuous | ||
/pro_vs_m/attack |
87 | 0–99 | continuous | ||
/pro_vs_m/attack |
88 | 0–99 | continuous | ||
/pro_vs_m/resonance |
71 | 0–99 | continuous | ||
/pro_vs_m/cutoff |
74 | 0–99 | continuous | ||
/pro_vs_m/attack |
81 | 0–99 | continuous | ||
/pro_vs_m/attack |
82 | 0–99 | continuous | ||
/pro_vs_m/attack |
83 | 0–99 | continuous | ||
/pro_vs_m/attack |
84 | 0–99 | continuous | ||
/pro_vs_m/depth |
91 | 0–99 | continuous | ||
/pro_vs_m/rate |
92 | 0–99 | continuous |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /pro_vs_m/note/on <note> <velocity>, /pro_vs_m/cc/<number> <value>, /pro_vs_m/pitchbend <0-16383>, /pro_vs_m/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¶
Which MIDI CC controls the filter cutoff on the Behringer PRO VS m?
CC 74 (0–99), named /pro_vs_m/cutoff in SynthHub's map.
How many parameters of the Behringer PRO VS m can be controlled over MIDI?
SynthHub's map of the Behringer PRO VS m lists 30 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 Behringer PRO VS m?
Yes: SynthHub's hosted MCP server knows the Behringer PRO VS m's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.