# inMusic plans open-source MPC code and tools for vibe-coded music gear mods

> inMusic plans to open code for devices such as the MPC Sample Key, offer an SDK and host hands-on hacking at NAMM. The challenge is giving musicians room to experiment while keeping official software dependable.
>
> OpenCheese AI · 2026.11.07 · Web page: https://opencheese.dev/blog/inmusic-plans-open-source-mpc-code-and-tools-for-vibe-coded-music-gear-mods

inMusic wants musicians to experiment with their gear without making the next gig an experiment, too. The parent company of Akai, Moog, Native Instruments and other music brands plans to make code for devices such as the teased MPC Sample Key open source, provide a developer SDK and give the modding community more room to work.

## A toolbox for the people already tinkering

CEO Jack O'Donnell describes an approach built around giving developers access to the internal workings of the company's instruments. Instead of trying to keep modifications outside the business, inMusic wants to supply tools that make them easier to create and less likely to leave a beloved sampler unusable.

The proposed toolbox has two main parts:

- **Open-source device code.** Developers would get access to software for devices such as the MPC Sample Key, giving them a way to examine and change how the hardware works.
- **A developer SDK.** The company intends to make modifications easier while reducing the risk of bricking an instrument.

Those are related commitments, but they address different parts of the problem. Access to code gives people something to change. Development tools are intended to make the process less hazardous.

Akai has already begun getting devices into developers' hands ahead of the Sample Key's official release. That puts some practical activity behind the plan, rather than leaving the whole exercise at the level of an invitation to be creative.

The scope still needs careful reading. O'Donnell's comments establish an intention to open up devices and support developers. They do not establish that every product across inMusic's brands will receive the same access or the same tools.

## The stage sets a stricter standard

O'Donnell also wants official software to remain stable enough for artists performing live. His example was the prospect of Fred Again taking an MPC on stage and encountering bugs, a useful reminder that an interesting software experiment and a dependable instrument have different jobs.

A live set is an inconvenient place to discover which one you brought.

The company therefore wants to preserve the reliability of its official releases while allowing users to make their own changes. Welcoming a modification does not, by itself, make that modification ready for a performance.

O'Donnell's proposed answer includes a reset mechanism. He wants people to be able to experiment and then return without losing what they already have.

That remains a stated goal, rather than a demonstrated guarantee that any failed modification can be reversed without loss. The distinction matters because easier access and reliable recovery solve different problems. An SDK may reduce the chance of trouble. A reset option is meant to help after an experiment has gone wrong.

For musicians considering these tools, the useful thing to watch is how those promises become working features. Access to code is one part of the offer. A dependable route back to official software would make that access considerably more comfortable to use.

## Creator Lab brings the plan to 22 products

inMusic plans to give technically curious musicians hands-on hacking time through Creator Lab at NAMM, the annual music manufacturers' convention in Anaheim. The company says the initiative will involve 22 new products from across its brands.

That number describes the products intended for the hands-on program. It should not be treated as a promise that 22 complete codebases will be published. The broader modding initiative includes several kinds of access, with open-source code and an SDK among the tools O'Donnell has discussed.

Moog is part of the plan, despite the apparent mismatch between vibe coding and instruments built around analog circuitry.

O'Donnell believes there is room to work if the company opens those instruments appropriately. His proposed approach is to build a platform that lets developers work around the analog parts of the circuit.

That is a more specific proposition than suggesting an analog instrument can simply be rewritten in software. The opportunity depends on what the surrounding platform lets developers change. The analog circuitry remains part of the design, rather than an inconvenience to be wished away by a coding prompt.

Creator Lab is intended to let musicians try that approach directly. Its value will depend on the access each product actually offers, not merely on how many instruments appear under the modding banner.

## Other manufacturers are opening their code

inMusic's move sits alongside several other manufacturers' decisions to give users more access to their devices. The examples span drum machines, grooveboxes, controllers and sequencers, although they are at different stages of release.

| Company | What it has done or announced |
| --- | --- |
| Erica Synths | Released the source code for its LXR-02 drum machine. |
| Polyend | Made its line of Tracker grooveboxes open source. |
| Behringer | Announced open-source devices including Kick, a $150 clone of the MPC One, an E-mu SP-1200 clone, the Anima DJ controller, the Ignite sequencer and the Polykeys 61 MIDI controller. |

The distinction between released code and announced plans is worth keeping intact. Erica Synths and Polyend have opened code. Behringer has announced devices, while inMusic is describing a combination of future code access, development tools and hands-on activity.

These moves give the modding community several points of entry. They do not amount to a shared promise about support, recovery or the safety of any particular modification.

That is where the appeal of openness meets the less glamorous work of making it usable. Publishing code answers the question of access. Musicians still have to decide whether a particular modification belongs on an instrument they rely on.

## Elektron draws its boundary at forum links

Elektron has taken a more guarded approach. It has banned links to hacks and modified firmware on its official forums, while allowing general discussion of them.

Its concerns are concrete:

- **Unusable instruments.** A modification could brick a device and leave it unable to function.
- **Future updates.** Changed firmware could prevent later updates from working.
- **Warranty coverage.** Modifications could affect the protection available to an owner.

The restriction includes links to hacked Digitone firmware. It does not amount to a ban on discussing modifications, and Elektron is not actively trying to shut down the wider modding community.

That distinction makes its position less absolute than a simple account of manufacturers choosing sides might suggest. Elektron is setting limits on what people can link to through its own forums. inMusic is proposing tools that would make modification easier and, it hopes, safer.

Both positions acknowledge the possibility that unofficial changes can go wrong. The disagreement is over how much a manufacturer should help people make those changes and what it should host on its own channels.

For owners, those details matter more than a broad label such as mod-friendly. Permission to talk about a modification, access to source code and a supported development tool are different things. So is a working recovery mechanism.

## Five weeks from absent to urgent

The speed of inMusic's response is striking. O'Donnell said that providing developers with hacking tools had not been on the company's task list five weeks earlier. It then became something the company felt it needed to address.

That is a short interval for a decision touching source code, developer access and the relationship between official software and user modifications. The plans are taking shape as the company responds to the growing role of vibe-coded mods.

O'Donnell's reasoning is pragmatic. He regards attempts to shut the community out as a losing strategy and would rather work with people who want to alter their instruments.

The sensible test of that approach will be what developers and musicians can actually use: the code that becomes available, the tools that make changes easier and the recovery options that survive an unsuccessful experiment. Until then, the distinction between an announced direction and a finished capability deserves to stay visible.

inMusic is making a bet on musicians wanting more freedom over their hardware. Its proposed reset button acknowledges the equally reasonable desire to have a working sampler afterward.

## Related posts

- 2026.10.05 · [Google Pauses Open-Source Bug Bounty Program After Surge in AI Submissions](https://opencheese.dev/blog/google-pauses-open-source-bug-bounty-program-after-surge-in-ai-submissions.md): Google paused its Open Source Software Vulnerability Rewards Program on October 1 after a sharp rise in automated reports, most of which the company said were invalid. It plans to provide an update in the first quarter of 2027.
- 2026.11.05 · [Anthropic Builds FlashProve to Catch AI Labs Secretly Swapping Models](https://opencheese.dev/blog/anthropic-builds-flashprove-to-catch-ai-labs-secretly-swapping-models.md): Anthropic released open-source code for FlashProve, a cryptographic system that lets users verify whether an AI output actually came from the claimed model.
- 2026.11.05 · [OpenAI Acquires Pierre Computer Company to Expand Codex Code Review and Building Tools](https://opencheese.dev/blog/openai-acquires-pierre-computer-company-to-expand-codex-code-review-tools.md): OpenAI is acquiring Pierre Computer Company, Inc. to expand Codex with additional tools for building, understanding, and reviewing software code.