MPC Live · One · X · Key · Force — MPC OS 3.x
Native plugins for MPC OS.
What actually works, and what it costs.
These are working notes, not a product page. Every number here was measured on a device, every trap was hit at least once, and the places where we are still guessing are marked as guesses. The point is that someone building the next plugin does not have to rediscover them.
What this is built on
Everything here runs on sd88me/mpc-vst-plugins (MIT) — the wrapper, the parameter compiler, the skin generator, the offline host test, the CPU bench, the packager and the catalog. That project is the reason any of this is possible; these notes only add what comes after “it builds”.
The three things a plugin is
1 · An engine
A block renderer: 128-frame int16 stereo blocks at 44.1 kHz, through mpc_engine_t.
No allocation in the render path, no locks, no logs, no file I/O.
2 · A screen MPC can draw
MPC draws it itself, from pre-rendered PNGs plus values it polls. You do not get a framebuffer. Animated or dense UI has to leave the device.
3 · A folder and a line of XML
/sdcard/Synths/<vendor> - VST - <name>/ plus one entry in
MPC.settings. Get the sequence wrong and MPC resets its settings.
The loop that works
build (arm32, docker) → test (x86, ASan) → bench (device, CPU) → deploy → see it
Two of those four steps are cheap enough to run on every change. The expensive one is “see it” — a deploy plus an insert plus a screenshot. Making that step fast is what the companion screen and the agent tooling are about.
What we shipped with these notes
MPC Multihead Echo — a three-head tape echo, GPL-3.0, 32 parameters, three interface pages in a browser, bench p99 24.4 % of the 2902 µs block on a Live II. It is the worked example behind every page here, including the two crashes that shaped the rules.
Read in this order
| Page | Why |
|---|---|
| Build | Toolchain, first plugin, the commands and what they prove. |
| The device | The fourteen facts that cost time: services, paths, skins, /proc, crashes. |
| Companion screen | Giving a plugin a real UI without asking MPC to draw it. |
| Testing | What each test catches, and the bugs that got past the ones we had. |
| Ship | Release zip, licence rules, catalog entry, the exact API calls. |
| Agents | Driving a device from a model — what exists today, what is missing. |