Teenage Engineering OP-1: MIDI CC, NRPN and OSC map¶
The Teenage Engineering OP-1 as named OSC addresses — 4 CC — ready to use from Claude (MCP), SuperCollider, Sonic Pi, TouchDesigner or any OSC app via osc-bridge.
| Device | Teenage Engineering OP-1 |
|---|---|
| Vendor | Teenage Engineering |
| OSC prefix | /op_1 |
| Source | 📦 Derived from MIDI Guide (community CC/NRPN data) |
| Firmware | unknown |
| Revision | per pencilresearch canonical CSV |
| Upstream | pencilresearch |
| Data licence | CC-BY-SA-4.0 — MIDI Guide (https://midi.guide) by Pencil Research and contributors |
| Driver file | devices/teenage-engineering/op_1.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/teenage-engineering/op_1.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 op_1: ask “what can the Teenage Engineering OP-1 do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (4)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/op_1/midi_lfo/synth |
0 | 0–127 | continuous | MIDI LFO | |
/op_1/midi_lfo/envelope |
1 | 0–127 | continuous | MIDI LFO | |
/op_1/midi_lfo/fx |
2 | 0–127 | continuous | MIDI LFO | |
/op_1/midi_lfo/volume |
3 | 0–127 | continuous | MIDI LFO |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /op_1/note/on <note> <velocity>, /op_1/cc/<number> <value>, /op_1/pitchbend <0-16383>, /op_1/program_change <n>.
Limitations¶
CC/NRPN only. SysEx (preset management, display control, bulk dump/load, vendor-proprietary opcodes) is NOT covered by pencilresearch. To extend this device with SysEx, sniff the vendor editor, add `sysex.header/footer` + `commands` blocks, and use `update_device.md` PR template.