Help & documentation

Getting started

MidiQ is a browser-based MIDI editor for Behringer BCR2000 and BCF2000 controllers. It uses the Web MIDI API to communicate directly with your hardware — no drivers or plugins required.

1. Open MidiQ in a supported browser (Chrome, Edge, or Opera).
2. Connect your BCR2000 or BCF2000 via USB.
3. Click the Settings icon (gear) in the left rail to open the Settings panel. Select your MIDI In and Out ports, then click Connect.
4. Click any encoder, button, or fader on the virtual hardware to configure it.
5. Use the STORE function key to send your preset to the device.

No account is required to use the editor. Create a free account to connect your device, save up to 3 presets to the cloud, and publish to the community library. Unlock the Studio License (€24, one‑time) for unlimited cloud saves, bulk bank export, private presets, and a verified‑author signature badge.

MIDI connection

Click the Settings icon (gear) in the left rail to open the Settings panel.

• In port / Out port — Select the MIDI ports matching your BCR/BCF device.
• Connect — Opens the selected ports. The status indicator in the toolbar turns green when connected.
• SysEx Delay — Optional delay (ms) between SysEx messages. Increase this if transfers fail on Apple Silicon Macs over USB.
• Model / Firmware / Dev / Mode / Channel / FootSwitch — Read-only fields showing device info received after connecting.

MIDI port preferences are saved automatically when you are logged in.

BCR2000 & BCF2000

Use the ROTARY / FADER toggle on the right side panel to switch between device models. This changes the virtual layout without affecting the preset data.

Both models share the same preset format. Faders on the BCF2000 are internally mapped to encoders 33–40.

Element editor

Click any encoder, fader, or button on the virtual hardware to select it and open the editor panel on the right.

Common fields

• Name — A label displayed on the virtual element (up to 24 characters).
• Type — The MIDI message type. See MIDI types below.
• Channel — MIDI channel 1–16.
• Min / Max — Output value range. For CC and NRPN this supports 14-bit values (0–16383) when used with 14-bit modes.
• Default — Value sent when the element is reset (CC only).
• Show value — Display the current value numerically on the element.
• Color — A color dot for visual grouping.
• Reset — Resets all parameters on this element to default.

Encoder-specific fields

• Mode — Absolute or Relative, in 7-bit or 14-bit resolution. Relative variants: 1 (signed bit), 2 (two's complement), 3 (sign-magnitude).
• LED — How the LED ring visualizes the value. See LED ring modes below.
• Resolution — Encoder steps per rotation (1–65535).

Button-specific fields

• Mode — Momentary: sends value on press and release. Toggle: latches on/off. Increment: each press adds or subtracts a step value.
• Step — Step size for Increment mode (-127–127, excluding 0).

BCL code view

Click the </> button in the editor header to toggle the BCL code view, which shows the raw BCL lines that will be sent to the device for the selected element.

Changes are saved automatically. Use Ctrl+Z to undo and Ctrl+Y / Ctrl+Shift+Z to redo.

MIDI types

Encoder groups

The top row of 8 push encoders supports up to 4 independent groups, effectively giving you 32 configurable encoders in the same physical row. Click the 1 / 2 / 3 / 4 buttons on the right side panel to switch the active group. The LED display shows the active group.

Each group stores its own MIDI assignments independently. The dedicated encoders and buttons (rows below) are not affected by group switching.

LED ring modes

Push encoders and dedicated encoders have a 15-segment LED ring. The LED field in the element editor controls how it displays the current value:

Drag & drop

Rearrange element assignments by dragging them on the virtual hardware:

• Swap — Drag one element onto another to swap their configurations.
• Insert — Hold Shift while dropping to insert and shift subsequent elements down by one position.
• Copy — Hold Alt (or Ctrl) while dropping to copy the source element instead of moving it.
• Multi-element drag — Select multiple elements first (Ctrl+click or Shift+click range), then drag the group.

Banks & presets

Presets are organized into banks. Click the Banks icon (folder) in the left rail to open the banks panel.

• Each bank holds up to 32 numbered preset slots.
• Click a preset slot to load it into the editor.
• The active preset name is shown next to the bank name at the top of the slot list.
• Right-click a slot for options: rename, duplicate, delete, copy, paste.
• Click the export icon on a slot to download that preset as a file.
• Click the export icon next to a bank name to download all presets in that bank as a single file.
• Create a new bank with the + button in the banks panel header.

Import & export

• Import — Click the import icon in the banks panel header to load a preset file. Supported formats: .syx, .bcr, .bcf, .bc2, .txt (BCL text).
• Export preset — Click the export icon on a preset slot to save it as a file. BCR2000 presets export as .bcr, BCF2000 presets as .syx.
• Export bank — Click the export icon next to a bank name to save all presets in that bank as a single file.

Imported files are automatically detected as BCR2000 or BCF2000 from the file header. The model can be overridden after import.

SysEx transfer

MidiQ uses the BCL (B-CONTROL Language) protocol over SysEx to read from and write to the device. The four function keys on the right side panel control transfers:

• STORE — Sends the current editor preset to a memory slot on the device. You will be prompted for the target slot (1–32).
• LEARN — Reads the preset currently active on the device into the editor.
• EDIT — Activates edit mode on the device (equivalent to pressing Edit on the hardware).
• EXIT — Exits edit mode on the device.

Transfer progress and any BCL responses are shown in the Log tab of the bottom panel.

Tip: If transfers fail on Apple Silicon Macs over USB, increase the SysEx Delay in settings, or use an external USB-MIDI interface with DIN cables and set the device to S-1 mode.

MIDI monitor

The bottom panel can be expanded by clicking or dragging its top edge. It has two tabs:

• Log — Shows application events and BCL transfer output.
• MIDI Monitor — Shows all incoming and outgoing MIDI messages in real time. Each row shows: timestamp, port, direction, channel, type, parameter, and value.

Use the Filter button (funnel icon) in the MIDI Monitor tab to show/hide specific message types or directions. Use the Copy button to copy the current tab content to the clipboard.

Community presets

The community preset library lets you discover and share presets with other MidiQ users. Click the Library icon in the left rail to open it.

• Browse & search — Search the library by name or tag. Available to all users, no account required.
• Download & use — Load a community preset directly into your editor or save it to a bank slot. Requires a Pro account.
• Rate presets — Give a thumbs up or down to help surface the best presets. Requires a Pro account.
• Publish — Share your own preset to the library. Add a description and tags so others can find it. Requires a Pro account.

Keyboard shortcuts

Troubleshooting

Web MIDI troubleshooting

MidiQ talks to your hardware through the Web MIDI API. Most issues come down to browser support, page security context, or the OS holding the MIDI port open. Work through the checks below in order.

1. Use a supported browser

• Supported: Chrome, Edge, Opera, Brave (Chromium‑based, current versions).
• Not supported: Firefox and Safari do not implement Web MIDI — ports will simply not appear.
• On Chromebooks, Web MIDI works in Chrome on ChromeOS but not inside the Linux container.

2. Use HTTPS (or localhost)

Browsers only expose Web MIDI on a secure context. The MidiQ app is served over HTTPS, so this normally just works. If you self‑host or run a local copy, use https:// or http://localhost — plain http:// on a LAN address will silently fail.

3. Allow MIDI access when prompted

The first time you click Connect, your browser asks for permission to access MIDI devices (with SysEx). If you previously denied it, click the lock / tune icon in the address bar and reset the MIDI permission for this site, then reload.

4. Make sure no other app is holding the port

• macOS: Quit the legacy BC Manager, any DAW, and any standalone synth that may have grabbed the BCR/BCF port. Most macOS MIDI ports are exclusive.
• Windows: The classic WinMM driver is exclusive per‑port — close DAWs, BC Manager, and the Behringer USB control panel before connecting.
• Linux: If you use ALSA directly, only one client can own the port; consider routing through JACK or pipewire‑jack.

5. Check the device's USB mode

Hold EDIT while powering on the BCR2000 / BCF2000 to enter the global menu and pick a USB mode: U-1 is the safest default for editing. Avoid S-4, which loops MIDI back through USB and causes ghost messages.

6. Refresh the port list

If you plug the device in after opening MidiQ, open the Settings panel and click Connect again — ports are re‑enumerated on each connect. As a last resort, reload the page.

Why upgrade?

MidiQ is fully usable without an account, and a free account already covers everyday editing, sending presets to the device, and publishing to the community library. The Studio License is a one‑time €24 purchase that unlocks the heavier “studio” workflows and helps fund continued development.

Ready? See pricing →