sd88me / mpc-vst-plugins

# VST Plugins for MPC OS
> 💬 **Community:** join **Open MPC** on Discord for support, release announcements, plugin requests and MPC hacking.
Native plugins for **Akai MPC OS standalone devices** (MPC Live/One/X/Key, Force): a catalog to find and install them,
an installer app, and the tools to build, test and release your own.
> **MPC OS 2.x and 3.x.** Plugins here are built and tested on **MPC OS 3.x**. On **MPC OS 2.x** a plugin loads and its
> Q-Links work, but its touchscreen page only appears if the plugin's skin is written in the older format 2.x reads. The
> catalog checks from its files whether each release can work on 2.x, and marks one tested on a 2.x unit **MPC OS 2.x tested**
> (3.x, the standard, gets no badge); the installers warn before putting a 3.x-only plugin on a device that looks like 2.x.
> A 3.x-only plugin becomes 2.x-capable when its developer re-releases it with a compatible skin
> (how, and what the catalog checks: MPC OS 2.x vs 3.x below).
## Plugin catalog
**Open MPC - Plugin Catalog**: one browsable list of the community's VST2
plugins for MPC OS, with each plugin's current version, license, source link and a checksummed download.
- **Find a plugin.** Search, filter by kind, style, developer, license or distribution, and sort by recently updated or
 most downloaded. Every version shows its date and SHA-256, and what it was tested on. Each plugin is **Verified** (the newest release was tested on real hardware and the test is recorded; shown per generation as Verified Gen1 and/or Verified Gen2), **Listed** (it passed the catalog's automatic release checks, but no hardware test is recorded) or **Experimental** (new or unproven, hidden unless you ask for it). None of these is a security review: nobody reads each plugin's code, so stick to developers you trust. There is an Atom feed
 (`feed.xml`) of new releases.
- **Install with the installer app.** The MPC plugin installer is a
 small Windows, Mac and Linux app: connect to your device, tick plugins from the catalog (or drop in zips, including
 build-yourself ones), and it checks each download, installs the batch with one MPC restart and backs up your settings
 first. It can also remove plugins (keeping your own files), install to an SD card or USB drive, register plugin folders
 MPC does not know about, and clean up old settings backups. Needs root SSH access. Source in
 tools/desktop.
- **Guides on the site:** install a downloaded plugin,
 build a plugin, the
 release workflow and
 how to get yours listed.
- **Get your plugin listed.** Publish a GitHub release built with `tools/release.py` (or the reusable
 `vst-release.yml` workflow), then open a PR adding one small file, `catalog/plugins/ .json`. After that new
 releases appear on their own: the catalog reads your releases every night and checks each zip. Open-source licenses,
 or public source with a limited-use license (shown with a "Restricted use" badge).
- **Plugins built from your own firmware** (so a built zip