Written from devices/air-music-tech/drumsynth_500.electra-community-v01.fw-unknown.jsonEdit on GitHubJSON

AIR Music Tech DrumSynth 500 MIDI CC chart, NRPN and OSC map

The AIR Music Tech DrumSynth 500 MIDI implementation: 92 CC, each named, for Claude (MCP), SuperCollider or any OSC app.

  • sourceElectra One preset
  • real unitnot yet checked

Not checked on a real AIR Music Tech DrumSynth 500 yet. Own one? Load a sound or send a control, and tell us whether it worked.

Maker
AIR Music Tech
Version
per Electra preset
Source
Electra One preset
OSC prefix
/drumsynth_500

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/air-music-tech/drumsynth_500.electra-community-v01.fw-unknown.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /drumsynth_500/tune 63

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as drumsynth_500: ask “what can the AIR Music Tech DrumSynth 500 do?” and it reads this map with list_routes. See the MCP guide.

MIDI controls

92 controls, each with its number, its range and the name to send
Control CC Range Name to send
Tune 3 0–127 /drumsynth_500/tune
Decay 9 0–127 /drumsynth_500/decay
Curve 14 0–127 /drumsynth_500/curve
Amount 15 0–127 /drumsynth_500/amount
Decay 20 0–127 /drumsynth_500/decay
Curve 31 0–127 /drumsynth_500/curve
Click 35 0–127 /drumsynth_500/click
Noise 41 0–127 /drumsynth_500/noise
Drive 46 0–127 /drumsynth_500/drive
Mute 106 0–127 /drumsynth_500/mute
Solo 107 0–127 /drumsynth_500/solo
Tune 47 0–127 /drumsynth_500/tune
Decay 52 0–127 /drumsynth_500/decay
Bend 53 0–127 /drumsynth_500/bend
Noise 54 0–127 /drumsynth_500/noise
Decay 55 0–127 /drumsynth_500/decay
Color 56 0–127 /drumsynth_500/color
Diode 57 0–127 /drumsynth_500/diode
Hpf 58 0–127 /drumsynth_500/hpf
Reso 59 0–127 /drumsynth_500/reso
Mute 108 0–127 /drumsynth_500/mute
Solo 109 0–127 /drumsynth_500/solo
Gate 60 0–127 /drumsynth_500/gate
Level 61 0–127 /drumsynth_500/level
Time 62 0–127 /drumsynth_500/time
Claps 63 0–127 /drumsynth_500/claps
Noise 85 0–127 /drumsynth_500/noise
Color 86 0–127 /drumsynth_500/color
Low 87 0–127 /drumsynth_500/low
Mid 88 0–127 /drumsynth_500/mid
High 89 0–127 /drumsynth_500/high
Mute 111 0–127 /drumsynth_500/mute
Solo 112 0–127 /drumsynth_500/solo
Color 90 0–127 /drumsynth_500/color
Mix 102 0–127 /drumsynth_500/mix
Pitch 103 0–127 /drumsynth_500/pitch
Ch decay 104 0–127 /drumsynth_500/ch_decay
Oh decay 105 0–127 /drumsynth_500/oh_decay
Curve 106 0–127 /drumsynth_500/curve
Hpf 107 0–127 /drumsynth_500/hpf
Freq 108 0–127 /drumsynth_500/freq
Mix 109 0–127 /drumsynth_500/mix
Mute 113 0–127 /drumsynth_500/mute
Solo 114 0–127 /drumsynth_500/solo
Tune 110 0–127 /drumsynth_500/tune
Decay 1 111 0–127 /drumsynth_500/decay_1
Decay 2 112 0–127 /drumsynth_500/decay_2
Tune 2 113 0–127 /drumsynth_500/tune_2
Level 2 114 0–127 /drumsynth_500/level_2
Fdbck 2 115 0–127 /drumsynth_500/fdbck_2
Amount 116 0–127 /drumsynth_500/amount
Decay 117 0–127 /drumsynth_500/decay
Curve 118 0–127 /drumsynth_500/curve
Op1 op2 119 0–127 /drumsynth_500/op1_op2
Mute 115 0–127 /drumsynth_500/mute
Solo 116 0–127 /drumsynth_500/solo
Tune 3 0–127 /drumsynth_500/tune
Decay 1 9 0–127 /drumsynth_500/decay_1
Decay 2 14 0–127 /drumsynth_500/decay_2
Tune 2 15 0–127 /drumsynth_500/tune_2
Level 2 20 0–127 /drumsynth_500/level_2
Fdbck 2 31 0–127 /drumsynth_500/fdbck_2
Amount 35 0–127 /drumsynth_500/amount
Decay 41 0–127 /drumsynth_500/decay
Curve 46 0–127 /drumsynth_500/curve
Op1 op2 47 0–127 /drumsynth_500/op1_op2
Mute 117 0–127 /drumsynth_500/mute
Solo 118 0–127 /drumsynth_500/solo
Loop 52 0–127 /drumsynth_500/loop
Pitch 53 0–127 /drumsynth_500/pitch
Fine 54 0–127 /drumsynth_500/fine
Attack 55 0–127 /drumsynth_500/attack
Hold 56 0–127 /drumsynth_500/hold
Decay 57 0–127 /drumsynth_500/decay
Amount 58 0–127 /drumsynth_500/amount
Decay 59 0–127 /drumsynth_500/decay
Curve 60 0–127 /drumsynth_500/curve
Sample select 61 0–127 /drumsynth_500/sample_select
Mute 119 0–127 /drumsynth_500/mute
Solo 3 0–127 /drumsynth_500/solo
Loop 85 0–127 /drumsynth_500/loop
Pitch 86 0–127 /drumsynth_500/pitch
Fine 87 0–127 /drumsynth_500/fine
Attack 88 0–127 /drumsynth_500/attack
Hold 89 0–127 /drumsynth_500/hold
Decay 90 0–127 /drumsynth_500/decay
Amount 102 0–127 /drumsynth_500/amount
Decay 103 0–127 /drumsynth_500/decay
Curve 104 0–127 /drumsynth_500/curve
Sample select 105 0–127 /drumsynth_500/sample_select
Mute 9 0–127 /drumsynth_500/mute
Solo 14 0–127 /drumsynth_500/solo

Performance MIDI

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

JSON

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 AIR Music Tech DrumSynth 500 can be controlled over MIDI?

SynthHub's map of the AIR Music Tech DrumSynth 500 lists 92 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 AIR Music Tech DrumSynth 500?

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