Skip to content

Bitwig Drop Controller MIDI CC chart, NRPN and OSC map

The Bitwig Drop Controller MIDI implementation: 58 CC, each named, for Claude (MCP), SuperCollider or any OSC app.

Device Bitwig Drop Controller
Vendor Bitwig
OSC prefix /bitwig_drop_controller
Source πŸŽ›οΈ Derived from an Electra One community preset
Revision per Electra preset
Upstream electra-preset
Driver file devices/bitwig/bitwig_drop_controller.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/bitwig/bitwig_drop_controller.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /bitwig_drop_controller/manual 63

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

MIDI CC and NRPN parameters (58)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/bitwig_drop_controller/manual 31 0–127 continuous
/bitwig_drop_controller/drop_count 30 0–127 continuous
/bitwig_drop_controller/mute 70 0–127 continuous
/bitwig_drop_controller/mute 71 0–127 continuous
/bitwig_drop_controller/mute 72 0–127 continuous
/bitwig_drop_controller/mute 73 0–127 continuous
/bitwig_drop_controller/jump 28 0–127 continuous
/bitwig_drop_controller/drop 29 0–127 continuous
/bitwig_drop_controller/param_1 50 0–127 continuous
/bitwig_drop_controller/param_1 58 0–127 continuous
/bitwig_drop_controller/param_1 66 0–127 continuous
/bitwig_drop_controller/param_1 74 0–127 continuous
/bitwig_drop_controller/bank 25 0–127 continuous
/bitwig_drop_controller/save 27 0–127 continuous
/bitwig_drop_controller/param_2 51 0–127 continuous
/bitwig_drop_controller/param_2 59 0–127 continuous
/bitwig_drop_controller/param_2 67 0–127 continuous
/bitwig_drop_controller/param_2 75 0–127 continuous
/bitwig_drop_controller/1 26 0–127 continuous
/bitwig_drop_controller/param_3 52 0–127 continuous
/bitwig_drop_controller/param_3 60 0–127 continuous
/bitwig_drop_controller/param_3 68 0–127 continuous
/bitwig_drop_controller/param_3 76 0–127 continuous
/bitwig_drop_controller/param_4 53 0–127 continuous
/bitwig_drop_controller/param_4 61 0–127 continuous
/bitwig_drop_controller/param_4 69 0–127 continuous
/bitwig_drop_controller/param_4 77 0–127 continuous
/bitwig_drop_controller/device 82 0–127 continuous
/bitwig_drop_controller/parameter_1 3 0–127 continuous
/bitwig_drop_controller/parameter_2 14 0–127 continuous
/bitwig_drop_controller/parameter_3 16 0–127 continuous
/bitwig_drop_controller/parameter_4 18 0–127 continuous
/bitwig_drop_controller/prev_device 83 0–127 continuous
/bitwig_drop_controller/on_off 87 0–127 continuous
/bitwig_drop_controller/parameter_5 9 0–127 continuous
/bitwig_drop_controller/parameter_6 15 0–127 continuous
/bitwig_drop_controller/parameter_7 17 0–127 continuous
/bitwig_drop_controller/parameter_8 19 0–127 continuous
/bitwig_drop_controller/next_device 84 0–127 continuous
/bitwig_drop_controller/page_1 102 0–127 continuous
/bitwig_drop_controller/page_2 103 0–127 continuous
/bitwig_drop_controller/page_3 104 0–127 continuous
/bitwig_drop_controller/page_4 105 0–127 continuous
/bitwig_drop_controller/page_5 106 0–127 continuous
/bitwig_drop_controller/prev_page 80 0–127 continuous
/bitwig_drop_controller/page_6 107 0–127 continuous
/bitwig_drop_controller/page_7 108 0–127 continuous
/bitwig_drop_controller/page_8 109 0–127 continuous
/bitwig_drop_controller/page_9 110 0–127 continuous
/bitwig_drop_controller/page_10 111 0–127 continuous
/bitwig_drop_controller/next_page 81 0–127 continuous
/bitwig_drop_controller/send_1 20 0–127 continuous
/bitwig_drop_controller/send_2 21 0–127 continuous
/bitwig_drop_controller/send_3 22 0–127 continuous
/bitwig_drop_controller/send_4 23 0–127 continuous
/bitwig_drop_controller/send_5 24 0–127 continuous
/bitwig_drop_controller/prev_track 85 0–127 continuous
/bitwig_drop_controller/next_track 86 0–127 continuous

Performance MIDI

Notes, pitch bend and any CC are also available: /bitwig_drop_controller/note/on <note> <velocity>, /bitwig_drop_controller/cc/<number> <value>, /bitwig_drop_controller/pitchbend <0-16383>, /bitwig_drop_controller/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 Bitwig Drop Controller can be controlled over MIDI?

SynthHub's map of the Bitwig Drop Controller lists 58 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 Bitwig Drop Controller?

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