Skip to content

Telepathic Instruments Orchid: MIDI CC, NRPN and OSC map

The Telepathic Instruments Orchid as named OSC addresses — 3 CC — ready to use from Claude (MCP), SuperCollider, Sonic Pi, TouchDesigner or any OSC app via osc-bridge.

Device Telepathic Instruments Orchid
Vendor Telepathic Instruments
OSC prefix /orchid
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/telepathic-instruments/orchid.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/telepathic-instruments/orchid.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /orchid/general/sustain_pedal 63

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as orchid: ask “what can the Telepathic Instruments Orchid do?” and it reads this map with list_routes. See the MCP guide.

MIDI CC and NRPN parameters (3)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/orchid/general/sustain_pedal 64 0–127 continuous General
/orchid/general/all_sounds_off 120 0–127 continuous General
/orchid/general/all_notes_off 123 0–127 continuous General

Performance MIDI

Notes, pitch bend and any CC are also available: /orchid/note/on <note> <velocity>, /orchid/cc/<number> <value>, /orchid/pitchbend <0-16383>, /orchid/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.