devices/examples/test_synth.json, updated 2026-10-23Edit on GitHubJSONCSVMIDNAMOSCQueryosc-bridge Test Synth running 1.0
The osc-bridge Test Synth MIDI implementation: 5 CC, 1 NRPN, 3 drum sounds, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcetest device
- firmware1.0
- Maker
- osc-bridge
- Firmware
- 1.0
- Source
- test device
Test Synth (virtual)
Not a real instrument: the synth that osc-bridge connect --test-synth and
the connect page can simulate,
so the whole chain — relay, detection, sending, listening, reports, learned
mappings, contributions — can be tested without hardware.
- Answers the MIDI Identity Request as manufacturer
7D(the ID MIDI reserves for non-commercial use), family 1, model 1, firmware01 00 00 00. - Sends back every channel message it receives, as if the control had been
moved on the device:
relay_sendthenrelay_listensees it. - Keeps one sound — cutoff, resonance, attack, release, waveform, set by
their CC — like a real synth's edit buffer: the dump request
F0 7D 01 10 F7makes it send the sound as a patch,F0 7D 01 20 <cutoff> <resonance> <attack> <release> <waveform> F7, and receiving such a patch replaces the sound. For trying shared presets: capture, share, load. - Controls:
/filter/cutoff(CC 74),/filter/resonance(CC 71),/amp/attack(CC 73),/amp/release(CC 72),/osc/waveform(CC 70, 0-3),/lfo/rate(NRPN 0/1, 14-bit); drums/drum/kick,/drum/snare,/drum/hat(notes 36, 38, 42 on channel 10); notes and pitch bend.
Communities
MIDI controls
9 controls, from the source at 1.0
| Control | CC | NRPN (MSB/LSB) | Range | Name to send |
|---|---|---|---|---|
| Filter cutoff | 74 | 0–127 | /test_synth/filter/cutoff |
|
| Filter resonance | 71 | 0–127 | /test_synth/filter/resonance |
|
| Amp attack | 73 | 0–127 | /test_synth/amp/attack |
|
| Amp release | 72 | 0–127 | /test_synth/amp/release |
|
| Osc waveform | 70 | discrete | /test_synth/osc/waveform |
|
| Lfo rate | 0 / 1 | 0–16383 | /test_synth/lfo/rate |
Drum sounds
Send <name> [velocity] [note] [channel] to fire the sound (Note On).
| Sound | Note(s) | Channel | Velocity | Name to send |
|---|---|---|---|---|
| Kick | 36 | 10 | /test_synth/drum/kick |
|
| Snare | 38 | 10 | /test_synth/drum/snare |
|
| Closed hat | 42 | 10 | /test_synth/drum/hat |
Performance MIDI
Notes, pitch bend and any CC are also available: /test_synth/note/on <note> <velocity>, /test_synth/cc/<number> <value>, /test_synth/pitchbend <0-16383>, /test_synth/program_change <n>.
Use 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 examples/test_synth --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 test_synth: ask “what can the osc-bridge Test Synth do?” and it reads this map with list_routes. See the MCP guide.
Frequently asked questions
Which MIDI CC controls the filter cutoff on the osc-bridge Test Synth?
CC 74 (0–127), named /test_synth/filter/cutoff in SynthHub's map.
How many parameters of the osc-bridge Test Synth can be controlled over MIDI?
SynthHub's map of the osc-bridge Test Synth lists 5 MIDI CC and 1 NRPN 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 osc-bridge Test Synth?
Yes: SynthHub's hosted MCP server knows the osc-bridge Test Synth's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.