Crumar Bit01 (Tauntek) MIDI CC chart, NRPN and OSC map¶
The Crumar Bit01 (Tauntek) MIDI implementation: 55 CC, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | Crumar Bit01 (Tauntek) |
|---|---|
| Vendor | Crumar |
| OSC prefix | /crumar_bit01_tauntek |
| Source | 🎛️ Derived from an Electra One community preset |
| Revision | per Electra preset |
| Upstream | electra-preset |
| Driver file | devices/crumar/crumar_bit01_tauntek.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/crumar/crumar_bit01_tauntek.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 crumar_bit01_tauntek: ask “what can the Crumar Bit01 (Tauntek) do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (55)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/crumar_bit01_tauntek/dco1_octave |
14 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco1_saw |
17 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco1_triangle |
16 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco1_pulse |
18 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco1_pw |
19 | 0–30 | continuous | ||
/crumar_bit01_tauntek/dco1_dyn_pwm |
20 | 0–63 | continuous | ||
/crumar_bit01_tauntek/dco2_octave |
21 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco2_saw |
24 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco2_triangle |
23 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco2_pulse |
25 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dco2_pw |
26 | 0–30 | continuous | ||
/crumar_bit01_tauntek/dco2_dyn_pwm |
27 | 0–63 | continuous | ||
/crumar_bit01_tauntek/dco1_freq |
15 | 0–11 | continuous | ||
/crumar_bit01_tauntek/dco1_noise |
29 | 0–63 | continuous | ||
/crumar_bit01_tauntek/dco2_freq |
22 | 0–11 | continuous | ||
/crumar_bit01_tauntek/dco2_detune |
28 | 0–63 | continuous | ||
/crumar_bit01_tauntek/all_notes_off |
123 | 0–127 | continuous | ||
/crumar_bit01_tauntek/mod_wheel_amt |
1 | 0–63 | continuous | ||
/crumar_bit01_tauntek/cutoff |
74 | 0–63 | continuous | ||
/crumar_bit01_tauntek/resonance |
71 | 0–63 | continuous | ||
/crumar_bit01_tauntek/invert |
37 | 0–127 | continuous | ||
/crumar_bit01_tauntek/env_amount |
35 | 0–63 | continuous | ||
/crumar_bit01_tauntek/key_track |
38 | 0–63 | continuous | ||
/crumar_bit01_tauntek/patch_volume |
7 | 0–63 | continuous | ||
/crumar_bit01_tauntek/vcf_attack |
30 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vcf_attack |
32 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vcf_attack |
33 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vcf_attack |
34 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dyn_attack |
31 | 0–63 | continuous | ||
/crumar_bit01_tauntek/dyn_envelope |
36 | 0–63 | continuous | ||
/crumar_bit01_tauntek/vca_attack |
73 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vca_attack |
40 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vca_attack |
41 | 0–127 | continuous | ||
/crumar_bit01_tauntek/vca_attack |
72 | 0–127 | continuous | ||
/crumar_bit01_tauntek/dyn_attack |
39 | 0–63 | continuous | ||
/crumar_bit01_tauntek/dyn_envelope |
42 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo1_waveform |
47 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo1_vca |
46 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo1_vcf |
45 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo1_dco1 |
43 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo1_dco2 |
44 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo_wheel_amt |
61 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo1_rate |
48 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo1_delay |
50 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo1_dyn_rate |
49 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo1_depth |
51 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo2_waveform |
56 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo2_vca |
55 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo2_vcf |
54 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo2_dco1 |
52 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo2_dco2 |
53 | 0–127 | continuous | ||
/crumar_bit01_tauntek/lfo2_rate |
57 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo2_delay |
59 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo2_dyn_rate |
58 | 0–63 | continuous | ||
/crumar_bit01_tauntek/lfo2_depth |
60 | 0–63 | continuous |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /crumar_bit01_tauntek/note/on <note> <velocity>, /crumar_bit01_tauntek/cc/<number> <value>, /crumar_bit01_tauntek/pitchbend <0-16383>, /crumar_bit01_tauntek/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 Crumar Bit01 (Tauntek)?
CC 74 (0–63), named /crumar_bit01_tauntek/cutoff in SynthHub's map.
How many parameters of the Crumar Bit01 (Tauntek) can be controlled over MIDI?
SynthHub's map of the Crumar Bit01 (Tauntek) lists 55 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 Crumar Bit01 (Tauntek)?
Yes: SynthHub's hosted MCP server knows the Crumar Bit01 (Tauntek)'s MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.