Repository navigation
Releases
Plugin Manager G2 VST v0.9.1
Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; for Gen1 and Gen2.
Requirements
- A first-generation MPC OS standalone device (32-bit ARM, like the Force, MPC Live / Live II, One, X and Key 61).
The installer refuses anything else. Newer models are untested. - Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
- Tested on MPC OS with a Force. Installing plugins this way is unofficial: back up first, use at your own risk.
Install (scripted)
- Unzip, then copy the whole folder to the device, e.g.
scp -r Plugin-Manager-G2-0.9.1 root@<device-ip>:/tmp/ - Run it:
ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.9.1/install.sh
The installer checks the device, stops MPC (save your project first), copies portable/OpenMPC - VST - Plugin Manager G2/ (the plugin, its skin
and its data, as one folder) into /sdcard/Synths, backs up MPC.settings, adds the plugin to MPC's plugin list from the
folder's plugin-meta.xml and starts MPC again. Running it again upgrades in place, keeping your own files.
An older install of this plugin (the previous layout, with the .so in /sdcard/vst) is replaced, not duplicated.
-y skips the confirmation prompt; -t <folder> installs into another Synths folder (for example on a card).
Then add Plugin Manager G2 to a track from the plugin browser (Instrument plugins). Its screen appears in the plugin view,
and the Q-Links follow the page.
Full instructions, including installing by hand, are in INSTALL.md inside the zip.
Built by GitHub Actions from d797507 with mpc-vst-plugins@d797507.
Plugin Manager G2 VST v0.9.0
Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; for Gen1 and Gen2.
Requirements
- A first-generation MPC OS standalone device (32-bit ARM, like the Force, MPC Live / Live II, One, X and Key 61).
The installer refuses anything else. Newer models are untested. - Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
- Tested on MPC OS with a Force. Installing plugins this way is unofficial: back up first, use at your own risk.
Install (scripted)
- Unzip, then copy the whole folder to the device, e.g.
scp -r Plugin-Manager-G2-0.9.0 root@<device-ip>:/tmp/ - Run it:
ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.9.0/install.sh
The installer checks the device, stops MPC (save your project first), copies portable/OpenMPC - VST - Plugin Manager G2/ (the plugin, its skin
and its data, as one folder) into /sdcard/Synths, backs up MPC.settings, adds the plugin to MPC's plugin list from the
folder's plugin-meta.xml and starts MPC again. Running it again upgrades in place, keeping your own files.
An older install of this plugin (the previous layout, with the .so in /sdcard/vst) is replaced, not duplicated.
-y skips the confirmation prompt; -t <folder> installs into another Synths folder (for example on a card).
Then add Plugin Manager G2 to a track from the plugin browser (Instrument plugins). Its screen appears in the plugin view,
and the Q-Links follow the page.
Full instructions, including installing by hand, are in INSTALL.md inside the zip.
Built by GitHub Actions from 1f2282f with mpc-vst-plugins@1f2282f.
Plugin Manager stick 0.9.0
The one-prompt USB stick that installs the OpenMPC Plugin Manager 0.9.0 on MPC OS 3.9.1 and earlier (every MPC and the Force; it carries both the Gen1 and the Gen2 build and picks the right one).
The easy way
Open the Install page in Chrome or Edge, answer the two questions and press Choose the drive and write: it writes this stick for you. Use an empty, freshly formatted USB stick.
By hand
- Download
Plugin-Manager-G2-Stick-0.9.0.zipbelow and unpack it onto the root of an empty USB stick (hidden files included). - Save your project, put the stick in the MPC and choose Open on the prompt. MPC restarts with the Plugin Manager installed; you can then unplug the stick.
- Create a Plugin track and choose OpenMPC Plugin Manager G2. Install from its screen, or from the web address on its status line (phone or computer, same Wi-Fi).
What's new in Plugin Manager 0.9.0
- A web page on your network: browse and install from your phone or computer.
- Drives with a space in their name are found; one storage is listed once.
See the Plugin Manager 0.9.0 release.
SHA-256: 645a92e1beae3ebd0b9d9033ac8825607bdad5a81cc3075a1175d826f34dd7da
Unofficial community software, not made or supported by Akai. The stick runs a script as root once you confirm the prompt. MPC OS 3.10 is not supported by this stick: install on 3.9.1, then update (see the Install page).
Plugin Manager G2 VST v0.2.5
What is new in 0.2.5: tap the storage readout at the top right to choose where new plugins go. With more than one place (the internal drive and an SSD or card, say) it names the drive (CARD · 12.0 GB ▾) and opens an INSTALL TO menu with each drive's free space; the choice is remembered. Fixes: the zip safety checks (unsafe file names, 600 MB limit) now actually run on the MPC (its unzip lacked the option they used, so they passed every zip unread; downloads were still checked against the catalog's SHA-256); reinstalling a plugin that an older installer put on the MPC now updates it where it is instead of making a second copy on the chosen drive; and a stray "N failed" message with garbage text after a successful apply is gone. Tested on a Force (MPC OS 3.9.1) with an internal drive and an SSD. (Called the OpenMPC Plugin Manager VST; the zip and plugin names still say "G2".)
Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; for Gen1 and Gen2.
Requirements
- A first-generation MPC OS standalone device (32-bit ARM, like the Force, MPC Live / Live II, One, X and Key 61).
The installer refuses anything else. Newer models are untested. - Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
- Tested on MPC OS with a Force. Installing plugins this way is unofficial: back up first, use at your own risk.
Install (scripted)
- Unzip, then copy the whole folder to the device, e.g.
scp -r Plugin-Manager-G2-0.2.5 root@<device-ip>:/tmp/ - Run it:
ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.2.5/install.sh
The installer checks the device, stops MPC (save your project first), copies portable/OpenMPC - VST - Plugin Manager G2/ (the plugin, its skin
and its data, as one folder) into /sdcard/Synths, backs up MPC.settings, adds the plugin to MPC's plugin list from the
folder's plugin-meta.xml and starts MPC again. Running it again upgrades in place, keeping your own files.
An older install of this plugin (the previous layout, with the .so in /sdcard/vst) is replaced, not duplicated.
-y skips the confirmation prompt; -t <folder> installs into another Synths folder (for example on a card).
Then add Plugin Manager G2 to a track from the plugin browser (Instrument plugins). Its screen appears in the plugin view,
and the Q-Links follow the page.
Full instructions, including installing by hand, are in INSTALL.md inside the zip.
Built by GitHub Actions from 7e582b5 with mpc-vst-plugins@7e582b5.
MPC plugin installer v1.1.2
What is new
- SSH stick: password and key settings now take effect on the Force (the firmware's own sshd settings were overriding them)
The MPC plugin installer: a small app that installs, updates and removes plugins on a modded MPC or Force from your computer. Guide: https://sd88me.github.io/mpc-vst-plugins/install.html
Which file do I need?
| Your computer | Download |
|---|---|
| Windows (almost every PC) | mpc-installer-1.1.2-windows.zip |
| Windows on an ARM chip (rare) | mpc-installer-1.1.2-windows-arm64.zip |
| Mac with an Apple chip (M1, M2, M3, M4 or later: any Mac from late 2020 on) | mpc-installer-1.1.2-mac-apple-silicon.tar.gz |
| Mac with an Intel chip (older Macs: Apple menu > About This Mac says "Intel") | mpc-installer-1.1.2-mac-intel.tar.gz |
| Linux | mpc-installer-1.1.2-linux.tar.gz (on an ARM chip: -linux-arm64.tar.gz) |
Unpack it and start mpc-installer. It is not signed, so your system warns the first time (Windows: More info, then Run anyway; Mac: right-click the file, Open, then Open). README.txt in the archive has the steps. Check a download against SHA256SUMS.
MPC plugin installer v1.1.1
What is new
- SSH stick: key mode now works on the Force (it stopped early on a missing install command)
- SSH stick: password mode now takes effect straight away (sshd is restarted)
The MPC plugin installer: a small app that installs, updates and removes plugins on a modded MPC or Force from your computer. Guide: https://sd88me.github.io/mpc-vst-plugins/install.html
Which file do I need?
| Your computer | Download |
|---|---|
| Windows (almost every PC) | mpc-installer-1.1.1-windows.zip |
| Windows on an ARM chip (rare) | mpc-installer-1.1.1-windows-arm64.zip |
| Mac with an Apple chip (M1, M2, M3, M4 or later: any Mac from late 2020 on) | mpc-installer-1.1.1-mac-apple-silicon.tar.gz |
| Mac with an Intel chip (older Macs: Apple menu > About This Mac says "Intel") | mpc-installer-1.1.1-mac-intel.tar.gz |
| Linux | mpc-installer-1.1.1-linux.tar.gz (on an ARM chip: -linux-arm64.tar.gz) |
Unpack it and start mpc-installer. It is not signed, so your system warns the first time (Windows: More info, then Run anyway; Mac: right-click the file, Open, then Open). README.txt in the archive has the steps. Check a download against SHA256SUMS.
Plugin Manager G2 VST v0.2.4
What is new in 0.2.4: the on-screen keyboard no longer types every letter twice, and buttons no longer fire twice. MPC delivers one tap as two presses 30 to 140 ms apart; the manager and the shared plugin wrapper now treat a second press of the same button within 250 ms as the same tap. Also from 0.2.3: zips in local-plugins/ are listed with no network. (Called the OpenMPC Plugin Manager VST; the zip and plugin names still say "G2".)
Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; for Gen1 and Gen2.
Requirements
- A first-generation MPC OS standalone device (32-bit ARM, like the Force, MPC Live / Live II, One, X and Key 61).
The installer refuses anything else. Newer models are untested. - Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
- Tested on MPC OS with a Force. Installing plugins this way is unofficial: back up first, use at your own risk.
Install (scripted)
- Unzip, then copy the whole folder to the device, e.g.
scp -r Plugin-Manager-G2-0.2.4 root@<device-ip>:/tmp/ - Run it:
ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.2.4/install.sh
The installer checks the device, stops MPC (save your project first), copies portable/OpenMPC - VST - Plugin Manager G2/ (the plugin, its skin
and its data, as one folder) into /sdcard/Synths, backs up MPC.settings, adds the plugin to MPC's plugin list from the
folder's plugin-meta.xml and starts MPC again. Running it again upgrades in place, keeping your own files.
An older install of this plugin (the previous layout, with the .so in /sdcard/vst) is replaced, not duplicated.
-y skips the confirmation prompt; -t <folder> installs into another Synths folder (for example on a card).
Then add Plugin Manager G2 to a track from the plugin browser (Instrument plugins). Its screen appears in the plugin view,
and the Q-Links follow the page.
Full instructions, including installing by hand, are in INSTALL.md inside the zip.
Built by GitHub Actions from 3522548 with mpc-vst-plugins@3522548.
Plugin Manager G2 VST v0.2.3
What is new in 0.2.3: zips you put in local-plugins/ are now listed, and can be installed, with no network. If the catalog cannot be reached the manager says so in a small warning and still shows your local zips and what is installed. (Called the OpenMPC Plugin Manager VST; the zip and plugin names still say "G2".)
Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; for Gen1 and Gen2.
Requirements
- A first-generation MPC OS standalone device (32-bit ARM, like the Force, MPC Live / Live II, One, X and Key 61).
The installer refuses anything else. Newer models are untested. - Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
- Tested on MPC OS with a Force. Installing plugins this way is unofficial: back up first, use at your own risk.
Install (scripted)
- Unzip, then copy the whole folder to the device, e.g.
scp -r Plugin-Manager-G2-0.2.3 root@<device-ip>:/tmp/ - Run it:
ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.2.3/install.sh
The installer checks the device, stops MPC (save your project first), copies portable/OpenMPC - VST - Plugin Manager G2/ (the plugin, its skin
and its data, as one folder) into /sdcard/Synths, backs up MPC.settings, adds the plugin to MPC's plugin list from the
folder's plugin-meta.xml and starts MPC again. Running it again upgrades in place, keeping your own files.
An older install of this plugin (the previous layout, with the .so in /sdcard/vst) is replaced, not duplicated.
-y skips the confirmation prompt; -t <folder> installs into another Synths folder (for example on a card).
Then add Plugin Manager G2 to a track from the plugin browser (Instrument plugins). Its screen appears in the plugin view,
and the Q-Links follow the page.
Full instructions, including installing by hand, are in INSTALL.md inside the zip.
Built by GitHub Actions from d408cbf with mpc-vst-plugins@d408cbf.
Basic stick test build (0.2.2-r7)
Test build: the basic one-prompt stick, with a fallback to the user space for units whose system drive has little room, and a drive scan in the report. For people whose stick said "no internal Synths folder qualifies" or "too little free space".
The basic stick installs the OpenMPC Plugin Manager VST on MPC OS 3.9.1 and earlier. It finds the plugin folder from MPC's own list of plugin folders. When MPC lists none that can take a plugin, it uses the unit's internal drive (/sdcard, /nvme or /storage), and if that drive can't take it or is missing, the internal user data partition (/media/az01-internal): it creates a Synths folder there, adds it to MPC's list of plugin folders so the plugin's skin shows, and installs. If it isn't sure of exactly one drive, it changes nothing and says why.
New in the report (g2-install-result.txt): a drive scan. Every drive gets a line saying whether it could take a plugin (internal, read-write, executable, enough room) or why not (USB drive, system folder, no executables). It chooses nothing yet; it helps us see how different models lay out their storage.
How to try it
- Download
Plugin-Manager-G2-Stick-0.2.2-r7.zipbelow. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too). - Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
- Next to Bundle, press Browse and pick the zip (if you paste its path, leave out any quote marks). Pick an empty USB stick and press Write stick.
- Save your project, insert the stick in the MPC, and confirm the prompt. MPC restarts with the plugin manager installed.
What to send back
g2-install-result.txt from the stick's root (a photo is fine), your device and MPC OS, whether it worked, and whether the plugin manager shows its own design.
What it changes on your MPC
Only when it has to add the folder: it stops MPC, copies MPC.settings to the stick (MPC.settings.backup) and beside the original, adds one line to the plugin folder list, checks the file, installs, and starts MPC again whatever happens. If the check fails it leaves the settings as they were. This part has been tested only against stand-ins, not yet on a real device. The /media/az01-internal fallback has not been seen on a Force: if MPC does anything odd, or the plugin manager doesn't appear, tell me and keep the stick.
Beta. Unofficial community software, not made or supported by Akai. The stick runs a script as root once you confirm the prompt. It does not run on MPC OS 3.10.
Basic stick test build (G2 0.2.2-r4)
Test build: the basic one-prompt stick, now for a Force (or any unit) whose MPC lists no internal plugin folder. For people whose stick said "no internal Synths folder qualifies".
The basic stick installs the OpenMPC Plugin Manager VST on MPC OS 3.9.1 and earlier. This build finds the plugin folder from MPC's own list. When MPC lists no usable internal plugin folder (a Force that has never had a plugin installed lists only Akai's own content), it uses the one internal drive (/sdcard, /nvme or /storage): it creates a Synths folder there, adds it to MPC's list of plugin folders so the plugin's skin shows, and installs. If it isn't sure of exactly one drive, it changes nothing and says why.
How to try it
- Download
Plugin-Manager-G2-Stick-0.2.2-r4.zipbelow. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too). - Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
- Next to Bundle, press Browse and pick the zip (if you paste its path, leave out any quote marks). Pick an empty USB stick and press Write stick.
- Save your project, insert the stick in the MPC, and confirm the prompt. MPC restarts with the plugin manager installed.
What to send back
g2-install-result.txt from the stick's root (a photo is fine), your device and MPC OS, whether it worked, and whether the plugin manager shows its own design.
What it changes on your MPC
Only when it has to add the folder: it stops MPC, copies MPC.settings to the stick (MPC.settings.backup) and beside the original, adds one line to the plugin folder list, checks the file, installs, and starts MPC again whatever happens. If the check fails it leaves the settings as they were. This part has been tested only against stand-ins, not yet on a real Force: if MPC does anything odd, tell me and keep the stick.
Beta. Unofficial community software, not made or supported by Akai. The stick runs a script as root once you confirm the prompt. It does not run on MPC OS 3.10.