Made by AI, Directed by David Stein

Search
Music Technology

Behringer Just Published a Music Production Center's Full Source Code Under the AGPL

Music Tribe has opened a GitHub organisation with the complete application, audio engine and hardware protocol for the unreleased Behringer KICK, plus a custom-firmware packer and schematics for the Pro-800 that is already in people's hands.

5 min read

A GitHub organisation called Music Tribe Open Source appeared on 14 October 2026. Thirteen days later it holds three public repositories, and one of them is the complete source code for a Behringer product that has not been released.

What is actually in the repository

The repository is named 0700-AAM, after the internal model number, and describes the Behringer KICK: a standalone production centre with a 7-inch touchscreen, 16 RGB pads in eight banks, a sampler with editing, a step sequencer, a looper, over 300 effects, four assignable knobs, a jog wheel and an AI camera for gesture control. Connections include MIDI in and out on 5-pin DIN, USB-A and USB-C, stereo in and out, an SD card slot and four CV/Gate jacks.

The code is split into four directories, and the README states a licence for each:

FolderContentsLicence
Kick/The applicationAGPL-3.0-or-later
AudIO/Audio engine libraryAGPL-3.0-or-later
ComProtocol/Hardware communication protocolAGPL-3.0-or-later
Linux/Buildroot Linux imageGPL-2.0 (Buildroot)

The audio engine and the protocol that talks to the hardware are the two pieces a manufacturer normally keeps. Publishing ComProtocol is what makes third-party firmware possible rather than merely imaginable: it is the documentation of how the application addresses the panel, the pads and the converters.

As of this morning, by GitHub’s own numbers, the repository has 168 stars and 24 forks, with its last push on 23 October.

The licence choice is not purely philosophical

The organisation’s LICENSING.md explains the AGPL in plain terms — change it, sell it, and if you ship a changed version you publish your changes under the same licence — and then adds a detail worth noticing: “It’s also what the JUCE framework requires for open-source use.”

JUCE, the C++ audio framework a large share of commercial plugins and instruments are built on, is dual-licensed: pay for a commercial licence, or release under the AGPL. If the KICK’s application is built on JUCE, the AGPL is not a gesture. It is the cheaper of two obligations. That does not make the release less useful to anyone forking it, but it does explain why the licence is the AGPL rather than something more permissive, and why AudIO and ComProtocol carry it too.

The other repositories take Apache-2.0 for tools and libraries, and GPL-2.0 where they patch Linux or U-Boot.

The second repository matters more today

The KICK has no announced price and no shipping date. The other new repository is for a product that has been on desks since 2022.

PRO800-Firmware-Packer is a tool for building firmware update files for the Behringer Pro-800, the Sequential Prophet-600-inspired polysynth. It ships with the schematics of the main PCB, and documents the target precisely: an STMicroelectronics STM32F446, reset handler linked to 0x08010000, maximum firmware size 128 kB, 128 kB of RAM, 180 MHz. Updates are packaged as SysEx and sent at about 9.64 kB/s, roughly 3.2 times the MIDI baud rate.

Two ways in: hold buttons 0 and 7 during power-up, or send F0 00 20 32 00 01 24 00 03 30 F7.

And then the part that decides whether a firmware community actually forms:

“Because the bootloader is fixed and not affected by the update process, the unit can always be recovered via SynthTribe. In addition, the bootloader flash area is write-protected.”

A failed flash leaves the unit in update mode rather than dead. That is the precondition every durable modding scene has had and every dead one lacked — the same reason the Canon hacking community grew around a tool that boots from the memory card and never touches the camera’s own firmware. Ten stars and two forks so far, against the KICK’s 168, which is the inverse of where the attention should probably be.

How the organisation says it will work

The governance document is short and unusually specific for a corporate repository. Anyone can contribute, with no account, membership or payment. Maintainers are community members nominated by existing maintainers and confirmed by owners. Owners are “a small group from the Foundation.”

That last phrase corroborates the other half of the story. Synthtopia reports founder Uli Behringer saying he has “transferred ownership of Music Tribe to the Uli Behringer Foundation,” that the company is pursuing formal nonprofit recognition, and that “the biggest threat to business isn’t AI. It’s abundance.” We could not find a primary publication of those statements, so treat the quotes as Synthtopia’s reporting rather than as a document you can read; the Foundation’s role in the GitHub organisation is independently visible in GOVERNANCE.md.

The organisation’s profile adds a promise about what the community may publish: “Study your own device, share only what you wrote yourself. No one else’s firmware, leaked code or license keys, ever.”

Why this lands now

Nothing here is unprecedented on its own. Mutable Instruments published its module firmware for years. Synthstrom’s Deluge was opened in 2021 and its community has shipped substantial releases since. What is new is the sequence: a $75 pocket synth acquired a firmware scene large enough that the community’s own board support package out-starred the manufacturer’s official SDK, and within weeks the largest-volume manufacturer in the industry published an unreleased flagship’s source code and a custom-firmware path for an existing product.

The honest caveat is that a repository is not a product. There is no KICK to buy, no price, and no date. The Pro-800 packer, by contrast, works on hardware that already exists — which is why the ten-star repository is the one to watch.

Sources

Related Reading