Meris Ottobit Jr MIDI CC chart, NRPN and OSC map¶
The Meris Ottobit Jr MIDI implementation: 18 CC, each named, for Claude (MCP), SuperCollider or any OSC app.
| Device | Meris Ottobit Jr |
|---|---|
| Vendor | Meris |
| OSC prefix | /ottobit_jr |
| 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/meris/ottobit_jr.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/meris/ottobit_jr.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 ottobit_jr: ask “what can the Meris Ottobit Jr do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (18)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/ottobit_jr/expr_pedal |
4 | 0–127 | continuous | ||
/ottobit_jr/bypass |
14 | 0–127 | continuous | ||
/ottobit_jr/tempo |
15 | 0–127 | continuous | ||
/ottobit_jr/smpl_rate |
16 | 0–127 | continuous | ||
/ottobit_jr/filter |
17 | 0–127 | continuous | ||
/ottobit_jr/bits |
18 | 0–127 | continuous | ||
/ottobit_jr/stutter |
19 | 0–127 | continuous | ||
/ottobit_jr/stutter_hold |
31 | 0–127 | continuous | ||
/ottobit_jr/sequencer |
20 | 0–127 | continuous | ||
/ottobit_jr/seq_mult |
21 | 0–127 | continuous | ||
/ottobit_jr/seq_type |
29 | 0–127 | continuous | ||
/ottobit_jr/step1 |
22 | 0–127 | continuous | ||
/ottobit_jr/step2 |
23 | 0–127 | continuous | ||
/ottobit_jr/step3 |
24 | 0–127 | continuous | ||
/ottobit_jr/step4 |
25 | 0–127 | continuous | ||
/ottobit_jr/step5 |
26 | 0–127 | continuous | ||
/ottobit_jr/step6 |
27 | 0–127 | continuous | ||
/ottobit_jr/tap |
28 | 0–127 | continuous |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /ottobit_jr/note/on <note> <velocity>, /ottobit_jr/cc/<number> <value>, /ottobit_jr/pitchbend <0-16383>, /ottobit_jr/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.
Frequently asked questions¶
Which MIDI CC controls the filter cutoff on the Meris Ottobit Jr?
CC 17 (0–127), named /ottobit_jr/filter in SynthHub's map.
How many parameters of the Meris Ottobit Jr can be controlled over MIDI?
SynthHub's map of the Meris Ottobit Jr lists 18 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 Meris Ottobit Jr?
Yes: SynthHub's hosted MCP server knows the Meris Ottobit Jr's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.