Skip to content

Conductive Labs NDLR v1 MIDI CC chart, NRPN and OSC map

The Conductive Labs NDLR v1 MIDI implementation: 37 CC, each named, for Claude (MCP), SuperCollider or any OSC app.

Device Conductive Labs NDLR v1
Vendor Conductive Labs
OSC prefix /ndlr_v1
Source πŸŽ›οΈ Derived from an Electra One community preset
Revision per Electra preset
Upstream electra-preset
Driver file devices/conductive-labs/ndlr_v1.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/conductive-labs/ndlr_v1.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /ndlr_v1/position 50

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

MIDI CC and NRPN parameters (37)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/ndlr_v1/position 28 1–100 continuous
/ndlr_v1/strum 29 0–127 continuous
/ndlr_v1/range 30 1–100 continuous
/ndlr_v1/spread 31 0–127 continuous
/ndlr_v1/velocity 63 1–127 continuous
/ndlr_v1/r_s_pad 85 0–127 continuous
/ndlr_v1/position 32 0–127 continuous
/ndlr_v1/type 33 0–127 continuous
/ndlr_v1/trigger 34 0–127 continuous
/ndlr_v1/r_s_drone 86 0–127 continuous
/ndlr_v1/octave_pos 35 1–10 continuous
/ndlr_v1/pattern_len 36 1–16 continuous
/ndlr_v1/play_dir 37 0–127 continuous
/ndlr_v1/pattern 38 1–40 continuous
/ndlr_v1/clock_division 39 0–127 continuous
/ndlr_v1/r_s_motif_1 87 0–127 continuous
/ndlr_v1/rhythm_len 40 4–32 continuous
/ndlr_v1/accent 41 0–127 continuous
/ndlr_v1/rhythm 42 1–40 continuous
/ndlr_v1/velocity 80 1–127 continuous
/ndlr_v1/low_velocity 66 1–100 continuous
/ndlr_v1/octave_pos 43 1–10 continuous
/ndlr_v1/pattern_len 44 1–16 continuous
/ndlr_v1/play_dir 45 0–127 continuous
/ndlr_v1/pattern 46 1–40 continuous
/ndlr_v1/clock_division 47 0–127 continuous
/ndlr_v1/r_s_motif_2 88 0–127 continuous
/ndlr_v1/rhythm_len 48 4–32 continuous
/ndlr_v1/accent 49 0–127 continuous
/ndlr_v1/rhythm 50 1–40 continuous
/ndlr_v1/velocity 65 1–127 continuous
/ndlr_v1/r_s_all 90 0–127 continuous
/ndlr_v1/degree 26 0–127 continuous
/ndlr_v1/type 27 0–127 continuous
/ndlr_v1/key 73 0–127 continuous
/ndlr_v1/mode_scale 74 0–127 continuous
/ndlr_v1/tempo 72 5–127 continuous

Performance MIDI

Notes, pitch bend and any CC are also available: /ndlr_v1/note/on <note> <velocity>, /ndlr_v1/cc/<number> <value>, /ndlr_v1/pitchbend <0-16383>, /ndlr_v1/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 Conductive Labs NDLR v1 can be controlled over MIDI?

SynthHub's map of the Conductive Labs NDLR v1 lists 37 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 Conductive Labs NDLR v1?

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