An official path for standalone plugins
MPC OS 3.10.1 brings a route for custom instrument and effect plugins on supported standalone hardware. Gearnews reported the update on 13 November. inMusic’s public MPC Plugin SDK describes how developers can build plugins and prepare packages for the device.
The SDK lists the original MPC One among its supported 32-bit targets. It also names the MPC One+, Live, Live II, X, X SE, Key 61, Key 37 and Force in that group, with Live III and MPC XL among its 64-bit targets. Check the SDK’s current compatibility list for your exact model; the similarly named MPC Sample is not listed there.
Akai
Akai MPC One
View product →
What the update requires
According to the SDK, on-device external plugin support requires MPC OS 3.10.1 or later. In Preferences, open Enhancements and enable both Enhancements and External Plugin Support. Its documented workflow builds an MPC-specific package and places it in the VST2 Plugins folder on a USB drive or SD card.
The SDK describes an MPC plugin as a Linux shared library using the VST 2.4 binary interface, with a manifest and optional device interface definitions. That does not mean any desktop VST file will run on an MPC: the build must target the device’s processor and follow the SDK package format.
Test before relying on a session
inMusic says third-party plugins run inside the MPC application without isolation and a fault can freeze or restart it. Its SDK includes a host simulator and recommends testing there first, saving work often and removing a faulty plugin folder if needed. These are the developer’s precautions, not results from a hands-on test.