mpc-vst-plugins

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)

1. Unzip, then copy the whole folder to the device, e.g. scp -r Plugin-Manager-G2-0.2.5 root@<device-ip>:/tmp/
2. 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 sd88me/mpc-vst-plugins@7e582b5 with mpc-vst-plugins@7e582b5.

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.

Test build: the basic one-prompt stick with plugin manager 0.2.4, which looks in the internal user space first. 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 tries the internal user space (/media/az01-internal) first, and only if that can't take it, the unit's own 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. A Force's internal SD is the system partition and has little room by design, which is why the user space comes first. If the stick isn't sure of exactly one drive, it changes nothing and says why.

New in this build: it carries plugin manager 0.2.4, where the on-screen keyboard no longer types every letter twice and buttons no longer fire twice (MPC delivers one tap as two presses). It also shows the zips in your local-plugins folder with no network.

How to try it

1. Download Plugin-Manager-G2-Stick-0.2.4.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS. (The installer also downloads this stick by itself if you leave the Bundle box empty.)
3. 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.
4. 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. The user-space-first order has been tested only against stand-ins, not yet on a real device (the previous test build used the unit's own drive first and worked on a Force through the user space only because that drive had too little room): 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.

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)

1. Unzip, then copy the whole folder to the device, e.g. scp -r Plugin-Manager-G2-0.2.4 root@<device-ip>:/tmp/
2. 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 sd88me/mpc-vst-plugins@3522548 with mpc-vst-plugins@3522548.

Test build: the basic one-prompt stick with plugin manager 0.2.3, which looks in the internal user space first. 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 tries the internal user space (/media/az01-internal) first, and only if that can't take it, the unit's own 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. A Force's internal SD is the system partition and has little room by design, which is why the user space comes first. If the stick isn't sure of exactly one drive, it changes nothing and says why.

New in this build: it carries plugin manager 0.2.3, which shows the zips in your local-plugins folder even with no network.

How to try it

1. Download Plugin-Manager-G2-Stick-0.2.3.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS. (The installer also downloads this stick by itself if you leave the Bundle box empty.)
3. 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.
4. 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. The user-space-first order has been tested only against stand-ins, not yet on a real device (the previous test build used the unit's own drive first and worked on a Force through the user space only because that drive had too little room): 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.

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)

1. Unzip, then copy the whole folder to the device, e.g. scp -r Plugin-Manager-G2-0.2.3 root@<device-ip>:/tmp/
2. 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 sd88me/mpc-vst-plugins@d408cbf with mpc-vst-plugins@d408cbf.

What is new

• Beta: one-prompt install stick for MPC OS 3.9.1 and earlier; the installer downloads its bundle itself, and the bundle now also works on a Force whose internal drive is full (device-tested)
• Stick tab: three sections, each titled with the MPC OS it supports (basic one-prompt stick, plugin manager stick for all versions including 3.10, SSH for developers)
• The plugin manager is called the OpenMPC Plugin Manager VST in the installer
• Clearer messages when a bundle file can't be used (quoted paths, ~ and an unpacked folder now work)
• Folder picker lists mounted drives (it stopped at C: on Windows)
• SSH stick: no password for a Gen2 firmware (needs a key), password works without chpasswd (Force), and the bundled manager opens only the first time

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.0-windows.zip
Windows on an ARM chip (rare)	mpc-installer-1.1.0-windows-arm64.zip
Mac with an Apple chip (M1, M2, M3, M4 or later: any Mac from late 2020 on)	mpc-installer-1.1.0-mac-apple-silicon.tar.gz
Mac with an Intel chip (older Macs: Apple menu > About This Mac says "Intel")	mpc-installer-1.1.0-mac-intel.tar.gz
Linux	mpc-installer-1.1.0-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.

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

1. Download Plugin-Manager-G2-Stick-0.2.2-r7.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
3. 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.
4. 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.

Test build: the basic one-prompt stick, with a clearer low-space message and a fuller report. For people whose stick said "no internal Synths folder qualifies" or "too little free space".

This build explains a low-space refusal and makes the report more useful. If the internal drive has too little room, the stick now says how much it read (the plugin manager needs about 40 MB, and 64 MB free is required). A Force's internal SD is the system partition and often has little room by design; a newer test build (r7) uses the user space instead. The report also shows each internal-looking drive's device, free space and folder id, which tells us how a Force lays out its storage. It also no longer wants 600 MB of free memory to unpack a 40 MB package (it needs 150 MB).

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

1. Download Plugin-Manager-G2-Stick-0.2.2-r6.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
3. 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.
4. 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.

Test build: the basic one-prompt stick, with a fix for units whose report said "under 64 MB free". For people whose stick said "no internal Synths folder qualifies".

This build makes the report show how much free space it read (r4 only said "under 64 MB"), and reads it in a way that works when a device's drive name is long. If it refuses for lack of space, the report says how much room the drive has: the plugin manager needs about 40 MB (64 MB free is required). A Force's internal SD is the system partition and often has little room by design; a newer test build (r7) uses the user space instead.

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

1. Download Plugin-Manager-G2-Stick-0.2.2-r5.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
3. 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.
4. 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.

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

1. Download Plugin-Manager-G2-Stick-0.2.2-r4.zip below. Don't unpack it (if a Mac's browser unpacked it into a folder, that works too).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
3. 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.
4. 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.

Test build: the basic one-prompt stick, with smarter plugin-folder detection. For people who tried the basic stick and saw "no internal Synths folder qualifies", or who want to help test it on other models.

The basic stick installs the OpenMPC Plugin Manager VST on MPC OS 3.9.1 and earlier (Gen1 MPC, Force, Gen2). This build finds where your MPC keeps its plugins from the MPC's own list of plugin folders, instead of looking in three fixed places, so it should work on more layouts (for example an MPC One, or a fresh unit that has never had a plugin installed). It installs only when it is sure of exactly one internal folder; otherwise it changes nothing and says why.

How to try it

1. Download Plugin-Manager-G2-Stick-0.2.2-r3.zip below (it is a stick bundle; don't unpack it).
2. Open the MPC plugin installer 1.1, go to the first tab, and in Basic user: one-prompt install stick choose your MPC OS.
3. Under Bundle, press Browse and pick the downloaded zip. Pick an empty USB stick and press Write stick.
4. Save your project, insert the stick in the MPC, and confirm the prompt. MPC restarts with the plugin manager installed.

What to send back

The stick leaves a file called g2-install-result.txt on its root. Please send me its contents, your device (for example "MPC One, MPC OS 3.9.1") and whether it worked. If it refuses, the file lists the folders your MPC has, so I can fix it for your model.

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.

Tested offline (21 tests) and with a dry run on a Live III; not yet tried on a Gen1 unit.

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)

1. Unzip, then copy the whole folder to the device, e.g. scp -r Plugin-Manager-G2-0.2.2 root@<device-ip>:/tmp/
2. Run it: ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.2.2/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 sd88me/mpc-vst-plugins@6634b26 with mpc-vst-plugins@6634b26.

Open MPC Plugin Manager G2 0.2.1: it remembers where you install

If your plugins live on an SSD or card instead of the user drive, you now choose it once and it sticks.

What's new

• Remembers your install location. When more than one place can take plugins, the restart prompt shows where the new ones will go with a CHANGE button. The place you confirm is now the default for new installs, so an SSD or card chosen once stays the default. If that drive is missing, the manager uses its normal default and keeps your choice for when the drive is back. Updates always stay where the plugin already is.
• Cleans up after itself on restarts. Each time the manager restarts MPC to apply changes, it also empties MPC's skin image cache (a RAM disk that only a reboot used to clear), so skins don't start drawing black patches after many restarts.
• A Gen1 and a Gen2 build in the same release, as before: -mpc-armv7.zip for Force, Live, One, X and Key, -mpc-aarch64.zip for the Live III and other 64-bit models.

Upgrade: run the new install.sh over the old one with -t <your Synths folder>; it upgrades in place.

Built on poloq's mpc-vst-manager. Credits and full feature list are in the README.

---

Downloads

• Plugin-Manager-G2-0.2.1-mpc-armv7.zip: Gen1 (32-bit ARM: Force, MPC Live / Live II, One, X, Key)
• Plugin-Manager-G2-0.2.1-mpc-aarch64.zip: Gen2 (64-bit: MPC Live III and the other 64-bit models)

Install

1. Unzip, then copy the whole folder to the device: scp -r Plugin-Manager-G2-0.2.1 root@<device-ip>:/tmp/
2. As root, run: sh /tmp/Plugin-Manager-G2-0.2.1/install.sh -t '<your Synths folder>'

The installer stops MPC (save your project first), copies the plugin and its skin into your Synths folder, backs up MPC.settings, adds the plugin to MPC's plugin list and starts MPC again. Running it again upgrades in place.

<your Synths folder> must be one of the folders listed under SynthContentLocations in MPC.settings (MPC draws a plugin's skin only from there). Typically /sdcard/Synths on a Force or Gen1 MPC, /nvme/Synths on a Live III, /storage/Synths on an MPC One Gen2. To see the list: grep -A6 SynthContentLocations <your MPC.settings> (/data/Settings/MPC/MPC.settings on Gen2, /media/az01-internal/Settings/MPC/MPC.settings on Gen1).

You need root shell access to the device for this first install. Then add Plugin Manager G2 (VST, manufacturer OpenMPC) to an instrument track; the device needs a network connection for the catalog. Installing plugins this way is unofficial: back up first, use at your own risk.

Full instructions, installing by hand, and the credits are in INSTALL.md inside each zip and in the README.

The official OpenMPC plugin manager: first release, for Gen1 and Gen2

Install, update and remove catalog plugins on the MPC itself. It's a plugin with its own touchscreen skin: no computer or USB stick once it's installed.

Why it exists: it's built on poloq's mpc-vst-manager (the concept, the whole working app, releases up to 1.2.0) and pulls in the best ideas from Eurikon's tool and real-device reports, as an official OpenMPC version that stays in step with the catalog and the official install methods. One release, both builds: Gen1 (32-bit: Force, Live, One, X, Key) and Gen2 (64-bit: Live III and kin).

What it does

• Browse Discover / Installed / Updates with search, filter, sort, five per page with thumbnails, Stable/Beta, High CPU and "Tested on" badges, and a details page
• Queue INSTALL, UPDATE, UPDATE ALL, REMOVE, then one APPLY and one restart; CHANGE picks where to install
• Safe: installs only where MPC will draw the skin; checks every zip's SHA-256, contents and your device (architecture, glibc, MPC OS) before MPC stops; if an install fails, the plugin folder and MPC.settings are put back and the screen says why
• Picks the right zip for your device (armv7 or aarch64)
• Local zips, REGISTER for folders MPC doesn't list, light/dark theme, install history, keeps your 10 newest settings backups, warns when MPC's image cache is filling

Tested on an MPC Live III (Gen2, OS 3.10) and a Force (Gen1). The MPC One layout comes from a user's report and is tested offline only.

Install: unzip, copy to the device, run install.sh -t as root (INSTALL.md has the steps).

Credits: poloq (the foundation), jacob-sabella (addins), Eurikon, FullPace/Padbangers (ideas), and everyone who reported issues. MIT licence.

---

Downloads

• Plugin-Manager-G2-0.2.0-mpc-armv7.zip: Gen1 (32-bit ARM: Force, MPC Live / Live II, One, X, Key)
• Plugin-Manager-G2-0.2.0-mpc-aarch64.zip: Gen2 (64-bit: MPC Live III and the other 64-bit models)

Install

1. Unzip, then copy the whole folder to the device: scp -r Plugin-Manager-G2-0.2.0 root@<device-ip>:/tmp/
2. As root, run: sh /tmp/Plugin-Manager-G2-0.2.0/install.sh -t '<your Synths folder>'

The installer stops MPC (save your project first), copies the plugin and its skin into your Synths folder, backs up MPC.settings, adds the plugin to MPC's plugin list and starts MPC again. Running it again upgrades in place.

<your Synths folder> must be one of the folders listed under SynthContentLocations in MPC.settings (MPC draws a plugin's skin only from there). Typically /sdcard/Synths on a Force or Gen1 MPC, /nvme/Synths on a Live III, /storage/Synths on an MPC One Gen2. To see the list: grep -A6 SynthContentLocations <your MPC.settings> (/data/Settings/MPC/MPC.settings on Gen2, /media/az01-internal/Settings/MPC/MPC.settings on Gen1).

You need root shell access to the device for this first install. Then add Plugin Manager G2 (VST, manufacturer OpenMPC) to an instrument track; the device needs a network connection for the catalog. Installing plugins this way is unofficial: back up first, use at your own risk.

Full instructions, installing by hand, and the credits are in INSTALL.md inside each zip and in the README.

Browse the OpenMPC catalog and install, update and remove plugins on the MPC itself, with rollback; Gen2 first.

Requirements

• A Gen2 MPC OS standalone device (64-bit ARM, aarch64: MPC Live III and the other 64-bit models) on MPC OS 3.x. The installer refuses anything else (the 32-bit Force, MPC Live / Live II, One, X and Key 61 need the -mpc-armv7.zip build).
• Root shell access (SSH) to the device. Stock MPC OS doesn't offer this; you need a modded unit.
• Gen2 devices keep plugins in the internal drive's Synths folder, and the folder differs: /nvme/Synths on a Live III, /storage/Synths on an MPC One. It must be one of the folders listed under SynthContentLocations in /data/Settings/MPC/MPC.settings (MPC draws a plugin's skin only from a listed folder): grep -A6 SynthContentLocations /data/Settings/MPC/MPC.settings. Use that folder wherever this guide says <your Synths folder>. Tested on an MPC Live III. Installing plugins this way is unofficial: back up first, use at your own risk.

Install (scripted)

1. Unzip, then copy the whole folder to the device, e.g. scp -r Plugin-Manager-G2-0.1.9 root@<device-ip>:/tmp/
2. Run it: ssh root@<device-ip> sh /tmp/Plugin-Manager-G2-0.1.9/install.sh -t '<your Synths folder>'

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 <your Synths folder>, 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 sd88me/mpc-vst-plugins@dfb0067 with mpc-vst-plugins@dfb0067.

What is new

• New: Gen2 support, tested on an MPC Live III (MPC OS 3.9.1). The installer finds /nvme/Synths, offers /nvme as a drive when /sdcard is missing, and uses the settings in /data/Settings/MPC/MPC.settings

• Fix: a stalled SSH connection (weak Wi-Fi) now errors out so you can retry, instead of the installer hanging after the last download

• Keepalive pings the device every 15s and drops a dead connection

Which file do I need?

Your computer	Download
Windows (almost every PC)	mpc-installer-0.6.1-windows.zip
Windows on an ARM chip (rare)	mpc-installer-0.6.1-windows-arm64.zip
Mac with an Apple chip (M1, M2, M3, M4 or later: any Mac from late 2020 on)	mpc-installer-0.6.1-mac-apple-silicon.tar.gz
Mac with an Intel chip (older Macs: Apple menu > About This Mac says "Intel")	mpc-installer-0.6.1-mac-intel.tar.gz
Linux	mpc-installer-0.6.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.

What is new

• Reconnects and copies again when the connection drops during a copy
• Create Synths folder button for drives that have none
• Register every plugin folder as part of an install (tick box)
• Waits for the auto exec patch before refusing a noexec drive; the Advanced step now offers Auto exec
• Tells you when a newer installer release exists (--no-update-check turns it off)

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-0.5.5-windows.zip
Windows on an ARM chip (rare)	mpc-installer-0.5.5-windows-arm64.zip
Mac with an Apple chip (M1, M2, M3, M4 or later: any Mac from late 2020 on)	mpc-installer-0.5.5-mac-apple-silicon.tar.gz
Mac with an Intel chip (older Macs: Apple menu > About This Mac says "Intel")	mpc-installer-0.5.5-mac-intel.tar.gz
Linux	mpc-installer-0.5.5-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.