Test and install your custom MPC plugin

Compiling, validating the package, and testing behavior are separate steps. A build can compile yet produce silence or fail to restore settings.

Third-party plugins run inside the MPC application and can freeze or restart it. Save your work and use a separate test project for a new plugin.

Before I install this, rebuild, run the SDK validator and host-simulator tests, and investigate all failures. Explain warnings. Check the targets against my MPC model. Give me the exact finished install-folder path and a simple folder tree. Separate automated results from checks that need my hardware.

At the root of a USB drive or SD card, create a folder named exactly VST2 Plugins. Root means the first level of the drive, alongside its other top-level folders.

Copy the complete manufacturer-and-plugin folder into it. The result should look like VST2 Plugins / Your Creator Name - VST - Your Plugin / plugin.json, with the VST and Plugin Skins folders beside that file. Ask the agent to show you this exact folder; do not copy the whole SDK or a source-code file.

Eject the drive properly, connect it to the MPC, and leave it connected while using a plugin stored there.

On MPC OS 3.10.1 or later, open Preferences → Enhancements and turn on both Enable Enhancements and External Plugin Support. Read the device notice. If the switches are missing, check your model and firmware against Akai’s documentation.

For an instrument, use a plugin track and look under External Plugins in the browser. For an effect, open a track’s insert slot. If a newly copied plugin does not appear, save and restart the MPC.

For replacement builds, remove and re-add the plugin. Restart if its interface changed. Internal-drive installs may also need a restart to be discovered.

Start at a low listening level with audio you know well. These checks establish what works on your device; they do not prove support for every model.

• Play notes for an instrument or send audio into an effect. Listen to both stereo channels.
• Move each control through its range using touch and Q-Links. Listen for clicks and unexpected volume changes.
• For synced effects, change tempo, start and stop, and check the tails.
• Save a project and reopen it. Confirm the sound and settings return.
• Watch CPU use in a normal project and with multiple instances. Report dropouts to the agent.

USB and SD installation do not require SSH. For faster iteration, the SDK remote tool can install over a shared network after enabling the device’s developer mode.

Have the agent read the current remote setup instructions. Use the SDK tool rather than improvised device commands, and switch developer mode off when finished.

Read the SDK installation documentation and deploy skill. Help me enable developer mode and find my MPC address. Use tools/mpc_remote.py and its doctor check to install this plugin, limiting changes to its VST2 Plugins folder. Ask before restarting so I can save my work. Explain how to turn developer mode off afterwards.

Stop using it. For a removable-drive install, remove its folder from VST2 Plugins using your computer before trying again. Keep the error details and build so the agent can investigate. Keep backups of working versions before replacing them; projects may depend on those versions.