Chapter 9
Gotchas & fact-check
What trips owners up, the claims that don’t hold up, and the slips in Behringer’s manual.
0/6
9.1Basics
Connection problems
Most connection trouble comes down to the port, the operation mode or Windows. Start at the top.
| Symptom | Cause and fix |
|---|---|
| Lights up, computer can’t see it | Check the cable is in USB POWER/DATA, then that the operation mode isn’t STDL (Check the operation mode). Source: Official Owners’ fixes vary: a USB 3 port (worked for one owner’s DAW, but not ControlTribe), Repair Driver in ControlTribe’s Help menu, or rolling Windows 11 updates back or forward. Microsoft lists a known issue since the 8 Sep 2026 Windows 11 update (KB5124008) that shows some USB Audio Class 1.0 devices as Code 10; no source ties it to the BCR32. Source: Press / owners |
| Random bugs or shutdowns | One owner traced these to running power and data over one cable. Put a strong supply on USB POWER and keep POWER/DATA for MIDI. Source: Press / owners |
| No notes from DIN MIDI OUT | The operation mode is USB, which turns DIN off. Set MIXED in Settings. Source: Official Source: Press / owners |
| DAW sees notes, not knobs (or the reverse) | Wrong virtual port: BCR-32 CTRL is the controller, BCR-32 ZAQ is the sequencer (Find the two USB MIDI ports). Source: Official |
| QR code in the box leads nowhere | Early boxes linked to a 404. Go to the product page. Source: Press / owners |
9.2Basics
Lost work
The BCR32 saves in two stages, and its export and erase procedures look alike. Both catch people out.
| Symptom | Cause and fix |
|---|---|
| Patterns or presets gone after power-off | 61STORE alone saves to temporary memory. Confirm with 60EXIT, then hold SELECT and press 61STORE (Storing patterns — and making them stick). Source: Official |
| Wiped memory while making a backup | SysEx export and Erase both start with 61STORE + hold SELECT + an encoder, and both use encoders 31 and 32. Export starts from encoder 25, the first encoder. Erase asks for a second press, so read the display before confirming (Back up before you experiment). Source: Official |
| Global settings didn’t stick | On the BCR2000, 60EXIT left Global without saving. Try leaving with 59EDIT/GLOBAL instead. Source: BCR2000 Zaq |
9.3Basics
Sequencer surprises
When the sequencer stays silent, it’s usually the clock source, the operation mode or a mute.
| Symptom | Cause and fix |
|---|---|
| Nothing plays after power-up | No stored pattern loads by itself, so you start on the working pattern. Source: Official Check that the clock source is Internal, that the operation mode isn’t USB (which turns the internal clock off), and that the track isn’t muted. |
| 68PLAY/STOP does nothing | The clock source is MIDI, USB or Sync. PLAY/STOP only drives the internal clock. In USB mode the internal clock is off entirely. Source: Official Source: BCR2000 Zaq |
| Only track 1 sounds | Tracks 2–4 muted (the BCR2000 default) or on unexpected channels. Check 66MIXER and Global encoders 42/44/46/48. Source: BCR2000 Zaq |
| 66MIXER won’t open | It only opens while the sequencer is stopped. Source: Official |
| Scale doesn’t change the drums | By design: drum tracks ignore the global scale (Scales). Source: BCR2000 Zaq |
| Ratchets cost an automation lane | Ratcheting is a MIDI CTRL α/β lane type, so a ratcheted track has one CC lane left (Ratchets and note delays). Source: BCR2000 Zaq |
9.4Intermediate
Hardware and firmware quirks
Several of these were fixed, or partly fixed, by the near-weekly updates after launch. Update first.
| Symptom | Cause and fix |
|---|---|
| LED rings ignore the DAW | Update to firmware 1.0.3+ with ControlTribe 1.12.3+, set encoders to Absolute, and make sure the DAW sends to BCR-32 CTRL (Two-way control with LED feedback). Source: Press / owners |
| Knobs feel slow | Early firmware felt slow, and its acceleration wasn’t adjustable. One owner says acceleration was added later, and a forum post says the speed can now be changed. Source: Press / owners |
| Encoders wobble | One owner estimates about 1.5 mm of play, and another notes the encoders aren’t screwed to the panel. Other owners report knobs that sit firmly. If yours wobble, don’t lean on them. Source: Press / owners |
| “Controller Overload” on the display | The message is real. One owner saw it once (30 Oct) with no obvious trigger, and separately says turning several encoders at once can outpace the processors. Nothing ties it to clock or SysEx load. Source: Press / owners The BCR2000 Zaquencer had its own PrOC (processor overload) warning. Its manual puts the stable limit at about 150 BPM with all four tracks at 32nd-note division, each step sending a note and two CCs. Source: BCR2000 Zaq |
9.5Intermediate
Common claims, checked
Much of what circulates about the BCR32 comes from pre-release spec sheets, AI-generated summaries and early forum posts. Some details that sound invented are true, such as the 404 QR code and the “Controller Overload” message. Others don’t hold up. Here is how the common claims compare with the sources.
| Claim | What the sources show |
|---|---|
| The panel has one push-encoder row plus three 8-knob rows, with sequencer keys along the bottom and right | Four identical rows of 8 encoders, all of which push. The 16 function keys sit in two rows of 8 along the top, the track keys in a 2×2 block beside them, and the menu/transport keys down the right-hand side. Source: Official |
| The product page offers a Quick Start guide and user manual | Only the multi-language user manual. The filename says Rev1 of 2026-04-06 and the cover says V 2.0. The file was re-uploaded on 20 Oct 2026, but the PDF itself is still dated 6 Apr. Source: Official |
docs.behringer.com is where guides are being migrated | It has no BCR32 content. The site lists only WING, FLOW 4V, SC I/O, SC-ADAT and DICE. Source: Official |
| ControlTribe handles firmware, preset management and visual encoder assignment | The manual explicitly names only firmware updates, and says many functions can also be done in the app. We couldn’t confirm preset editing or visual assignment. An owner reports it can’t save sequencer patterns. Source: Official Source: Press / owners |
| Users mistakenly tried SynthTribe | No source mentions this. Source: Unverified |
| The QR code in the box pointed to a dead URL | True. Owners report a 404 (Elektronauts #190 and several Thomann reviews, late September). Source: Press / owners |
| Plugging into the power-only port lights the unit, but it isn’t recognised | This follows from the port labels, but no owner has reported it. The recognition failures owners did report were USB-port, driver and Windows 11 problems. Source: Official Source: Unverified |
| Repo has USB bootloader update utilities; build with CMake + Ninja + GCC | The update tools are binaries only, and the image-transfer protocol isn’t documented. Keil MDK is the primary build; CMake/GCC is the alternative. No releases or tags. Source: Official |
| The sequencer is a direct port of the BCR2000 Zaquencer, plus 4× CV/Gate | No source calls it a direct port, and it runs on a different processor. Beyond CV/Gate it adds analogue sync, USB with two ports, the OLED, USB/STDL/MIXED modes, CV calibration and the two-stage store. Source: Official |
| Official partnership with Christian Stöcklmeier (ZAQ Audio) | The name is spelled right. Behringer announced a collaboration in 2021 and the press credits ZAQ Audio, but the BCR32 manual names neither ZAQ Audio nor Stöcklmeier, and zaqaudio.com doesn’t mention the BCR32. Source: Press / owners |
| ZAQ Audio hosts a SynMag “masterclass” on the Zaquencer | It’s a magazine review followed by an interview, written by David Thiehoff, in English translation on ZAQ Audio’s site. Source: Press / owners |
| Mono vs polyphonic tracks | Track Mode is Chord or Drum. A Chord track plays single notes wherever Chord = 0. Source: Official |
| Ratchets are a per-step parameter | They’re a lane type for MIDI CTRL α or β, alongside Delay. Source: Official |
| Directions: Forward, Backward, Pendulum, Random | Five: Forward, Backward, Pip 0, Random, Pendulum. Source: Official |
| Global scale constrains all outgoing notes | Drum tracks are exempt, and the scale is non-destructive until you apply it. Source: BCR2000 Zaq |
| Two automation lanes per track | Correct, but each lane holds one value per step (Off or 1–127 on the BCR32), not a continuous curve. Source: Official Source: BCR2000 Zaq |
| GD32F405RE at 120 MHz | Correct per the repo README and the demo firmware’s clock setting, although GigaDevice rates the chip at 168 MHz. The factory firmware isn’t public, so its clock can’t be confirmed. Source: Official |
| LED-ring feedback fixed by an autumn firmware update | It took several near-weekly updates. Owners say it works on firmware 1.0.3 with ControlTribe 1.12.3 (late October). Source: Press / owners |
| Map the 4×8 encoders as a 32-parameter remote page with row-1 pushes as device bypass | No owner describes one 32-parameter page. The idea assumes only the top row pushes, which was the pre-release spec; all 32 encoders push. A Bitwig owner uses one row per plug-in, with each row’s first push as bypass. Source: Press / owners |
| A firmware update enabled SysEx; copy BCR2000 SysEx TX strings | Partly. An owner’s review, updated after a firmware update, says SysEx now works, currently only by copying BCR2000 SysEx TX messages. Another owner confirms SysEx in and out. The “no SysEx” worry started before units shipped. Source: Press / owners |
| “Controller Overload” when turning 3+ encoders during heavy clock/SysEx traffic | The message is real. One owner saw it once, with no obvious trigger. Nothing links it to clock or SysEx load. Source: Press / owners |
| Gate 5/10 V, CV 0–10 V; CV/Gate pairs must be assigned to tracks 1–4 first | The voltages are in the manual and on the product page. No source mentions an assignment step, and the manual doesn’t document which track drives which output. Source: Official Source: Unverified |
| Reddit threads “Received BCR32, nice LED show” and “The Absolute Sequencer Powerhouse” | The first wasn’t found anywhere. The second is Behringer’s own promo video, presented by Bartek. Source: Press / owners |
| Elektronauts thread, from post #165 | Real. #165 (21 Aug) is about pre-orders, hands-on reports start around #182 (24 Sep), and the thread runs to #223. Source: Press / owners |
| Thomann owner reviews with mini-guides | Real, mostly on thomann.de and in German. They cover firmware fixes, Bitwig LED feedback and the SysEx workaround. Source: Press / owners |
| Music Supremacy guide | It exists (27 Aug 2026), but it was written before release and repeats the outdated 8-push-encoder spec. Treat it as unreliable. Source: Press / owners |
9.6Intermediate
Errors in Behringer’s manual
The English manual still has editing slips. Where it contradicts itself, test on the unit. Source: Official
- The SYNC IN START description still contains an editor’s placeholder, “<CHECK?>”.
- The LOAD instructions say “buttons 63 & 63”. The page keys are 63 and 64, as in STORE.
- The MIDI CTRL α lane types list “CC0–27”. The matching β list says CC0–127, which is what’s meant.
- Both Erase procedures say “25th encoder (50)”. Step 25 is item 49 and item 50 is step 26, so one of the two numbers is wrong. Read the display before confirming.
- Key 1 is called both ZAQ/CTRL and CTRL/ZAQ in the text. The panel legend itself reads ZQR/CTRL.
- The odd-step shuffle values are printed as 0, 16, 33, 60, 66 and 83. The even list has 50 where this one has 60.
- Two sections disagree on moving all steps at once: one says hold EDIT/GLOBAL (59), the programming hints say hold Note Pitch (5).
- The note range is given as “C2 to G8”. With C3 = MIDI 60, the full MIDI range is C−2 to G8.
- The filename says Rev1, the cover says V 2.0.