News · launches — By WATMM Desk —

Behringer opens its AQ64L pad controller to custom firmware

Behringer has published a developer kit for the AQ64L, a new 8x8 RGB clip-launch controller, with example firmware, a schematic and the USB tools to install your own builds. It also ships the private signing key the bootloader trusts, which is what makes owner firmware possible and also means a signature proves nothing about who made a package.

Key facts

  • What happened: Synthtopia reported on 13 Nov 2026 that Behringer is opening the AQ64L to custom firmware. Music Tribe has posted a developer kit on GitHub with example firmware, a main-board schematic and USB flashing tools; the factory firmware itself stays closed.
  • The hardware: 64 RGB velocity pads in an 8x8 grid, 16 RGB function keys, a GD32F350 Cortex-M4 chip with 128 KB flash and 16 KB RAM, and USB-C bus power with two USB MIDI ports. Behringer offers Ableton Live and FL Studio scripts and lists no price.
  • Why it matters: the bootloader trusts one signing key, and Behringer has published it. Owners can install their own firmware over USB without a debug probe, but any program on a connected computer can do the same, so a valid signature does not prove where a package came from.

Behringer's new AQ64L, a 64-pad grid controller for launching clips in a DAW, comes with a developer kit that lets owners write and install their own firmware. Synthtopia reported it on 13 Nov 2026. The kit lives in a public GitHub repository from MUSIC Tribe, Behringer's parent company.

What is the AQ64L?

Behringer's product page calls it a "clip launch controller for triggering audio clips and MIDI events", with an 8x8 grid, navigation, mix and track buttons, multi-colour LEDs and class-compliant USB MIDI. It says the controller works with an iPad through a USB camera adapter (not included) and as a universal MIDI controller. The downloads include Ableton Live and FL Studio scripts. The page shows no price, only a "Where to buy" link, and Synthtopia says Behringer has not announced pricing or a release date.

The developer kit fills in the hardware:

  • 64 RGB velocity pads in an 8 × 8 grid, plus 16 RGB function keys
  • a GD32F350 Cortex-M4 microcontroller with 128 KB of flash and 16 KB of RAM
  • USB-C, bus powered, with two USB MIDI ports and a USB HID keyboard interface
  • a factory bootloader that takes firmware upgrades over USB

What is in the developer kit?

According to the README, the repository holds example firmware (LED chain, key matrix, USB MIDI), a schematic of the main board's digital section, and two Python tools: one turns a build into an upgrade package and one uploads it over USB. The example builds with Keil or the free GCC toolchain.

What it leaves out matters as much. "The factory firmware is not open source," the README says. The bootloader source and the factory firmware's Ableton Live and FL Studio integration are not included either. So you can replace what the controller does, but you start from a demo, not from the shipping firmware.

The code is licensed AGPL-3.0-or-later, and firmware derived from the example that you distribute must be released under the same licence with complete source. The schematic is CC BY-NC-SA 4.0, which rules out commercial reuse. The README also warns that "flashing custom firmware may affect your warranty" and asks anyone who distributes firmware to use their own USB vendor and product IDs.

Why does the signing key matter?

The bootloader only installs packages with a valid Ed25519 signature, and Behringer has published the key it trusts. The key notes say the bootloader on devices already sold cannot be updated over USB and trusts exactly this one key, so shipping the key "is the only way to let owners install firmware they built themselves without a debug probe". They call it a deliberate decision "made knowing that it cannot be reversed for devices already shipped".

The same notes spell out the cost. A signature proves only that the bootloader will accept a package, not that Behringer made it, and "any program on a computer the device is plugged into can push firmware to it without pressing any key on the device." The advice is to check the SHA-256 on the official release page before flashing anything you did not build, and not to plug the controller into computers you do not trust. If a build fails, holding USER1 and USER2 while plugging in keeps the device in the bootloader; the README says it cannot be bricked while the bootloader region is intact.

What we think

This is the most interesting part of an otherwise familiar box. An 8x8 RGB grid with Ableton scripts is a well-worn format, and Behringer's own page names Launchpad in its compatibility line. What sets the AQ64L apart on paper is not the pads but the permission: a major hardware brand handing owners the means to reflash a current product, with a schematic and a build that runs on a free toolchain.

Publishing the key is a real trade, and Behringer says so. Most companies would have hidden that choice or shipped a locked bootloader. Here the notes state the risk in plain words. For a studio controller the risk is modest, since it has no network connection of its own, but it is real: treat the AQ64L like any USB device and only flash packages whose hash you have checked.

Expect the first community firmware to be grid tools, not DAW replacements. The factory DAW integration stays closed and the chip has 16 KB of RAM, so the realistic early builds are things like step sequencers, custom note layouts and generative patterns running on the controller itself. That is our inference from the specs and the demo, not anything Behringer has promised.

Watch the price and the licence. Without a price we cannot say whether it competes on cost, as most Behringer hardware does. The AGPL means anyone selling modified firmware must publish its source, which should keep community work open, and the non-commercial schematic licence rules out selling hardware copied from it.

If you build controller tools, the repository is worth a look now. If you just want a clip launcher, wait for the price.

Sources

  1. Behringer AQ64L (BE 0715-AAX) developer kit, MUSIC Tribe (GitHub) (primary source). Accessed 14 Nov 2026.
  2. AQ64L firmware signing key, MUSIC Tribe (GitHub) (primary source). Accessed 14 Nov 2026.
  3. AQ64L product page, Behringer (primary source). Accessed 14 Nov 2026.
  4. Behringer Opens New AQ64L 64-Pad MIDI Controller To Custom Firmware, Synthtopia. Accessed 14 Nov 2026.

Researched with AI assistance, written and checked by WATMM Desk.

Subscribe to We are the music makers

One email a week: the music-tech and AI-in-music news that mattered, and what we think about it.

Sign-ups open soon.