devices/behringer/fcb1010.vendor.fw-unknown.json, updated 2026-10-26Edit on GitHubJSONMIDNAMOSCQueryBehringer FCB1010
The Behringer FCB1010 MIDI implementation: its MIDI messages, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- Maker
- Behringer
- Firmware
- FCB1010 User Manual (MIDI Implementation Chart, Tab. 5.1)
- Source
- maker's documentation
Communities
Share and load its sounds
Plug the Behringer FCB1010 into your computer, open shared presets in Chrome, Edge or Opera and press Connect my synth: SynthHub finds it, takes the sound it plays and names it. Sounds others shared for it load from their page the same way.
https://el34world.com/Misc/Music/files/FCB1010_manual.pdf
MIDI controls
0 controls, from the source at FCB1010 User Manual (MIDI Implementation Chart, Tab. 5.1)
Performance MIDI
Notes, pitch bend and any CC are also available: /fcb1010/note/on <note> <velocity>, /fcb1010/cc/<number> <value>, /fcb1010/pitchbend <0-16383>, /fcb1010/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 behringer/fcb1010.vendor.fw-unknown --out-port <N> --in-port <M>
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as fcb1010: ask “what can the Behringer FCB1010 do?” and it reads this map with list_routes. See the MCP guide.
Limitations
Source: FCB1010 User Manual. The FCB1010 is a foot controller: it transmits notes (velocity 0 or 64), control changes 0-127 and program changes 1-128 as each preset is programmed, which arrive through the bridge's input routes (/note/on, /cc/{num}, /program_change). It recognizes nothing on MIDI IN but its own SysEx memory dump (after footswitch 7 'SYSEX RCV' in Global Configuration), whose format the manual does not give, plus Soft Thru / Merge of the incoming data; so this driver has no command to send. The manual names the stock firmware only through its expression-pedal calibration (versions 1.4 and newer). Untested on hardware.
Firmwares
The Behringer FCB1010 runs 4 firmwares SynthHub maps, each with its own MIDI or another's it shares. All the devices with several: firmwares.
| Firmware | From | Licence | MIDI | Sounds |
|---|---|---|---|---|
| FCB-505 firmware sheet | fcb1010.eu | same as behringer/fcb1010.vendor.fw-unknown | ||
| FCB/UnO User Guide v1.0.4 and uno_changelog.txt | fcb1010.eu | same as behringer/fcb1010.vendor.fw-unknown | ||
| UnO for Kemper manual and uno4kemper_changelog.txt | fcb1010.eu | same as behringer/fcb1010.vendor.fw-unknown | ||
| UnO2 User Manual and uno2_changelog.txt | fcb1010.eu | adds to behringer/fcb1010.vendor.fw-unknown |
Frequently asked questions
Can an AI agent like Claude control the Behringer FCB1010?
Yes: SynthHub's hosted MCP server knows the Behringer FCB1010's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.