LPZW Tram8: MIDI CC, NRPN and OSC map¶
The LPZW Tram8 as named OSC addresses — 8 CC — ready to use from Claude (MCP), SuperCollider, Sonic Pi, TouchDesigner or any OSC app via osc-bridge.
| Device | LPZW Tram8 |
|---|---|
| Vendor | LPZW |
| OSC prefix | /tram8 |
| 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/lpzw/tram8.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/lpzw/tram8.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 tram8: ask “what can the LPZW Tram8 do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (8)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/tram8/cc1 |
69 | 0–127 | continuous | ||
/tram8/cc2 |
70 | 0–127 | continuous | ||
/tram8/cc3 |
71 | 0–127 | continuous | ||
/tram8/cc4 |
72 | 0–127 | continuous | ||
/tram8/cc5 |
73 | 0–127 | continuous | ||
/tram8/cc6 |
74 | 0–127 | continuous | ||
/tram8/cc7 |
75 | 0–127 | continuous | ||
/tram8/cc8 |
76 | 0–127 | continuous |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /tram8/note/on <note> <velocity>, /tram8/cc/<number> <value>, /tram8/pitchbend <0-16383>, /tram8/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.