VMPC2000XL can be installed in Linux, MacOS and Windows. The current version should run reliable enough to satisfy enthousiasts and hobbyists, given the fact that they can report bugs and request features by contacting the author.

Stability is roughly equal for the standalone and plugin versions, though your best bet is the standalone version. Standalone is the recommended way to use VMPC2000XL for other reasons too – the original is a complex piece of equipment with a 200 page manual. Roger Linn poured a tremendous amount of interconnecting functionality in the MPC2000XL’s ancestors, the MPC60 and the MPC3000. A modern computer, let alone a full-on DAW, offers a lot of potential distraction from all this.

On the other hand, the usefulness of a DAW can’t be denied – it’s great fun to load up an instrumental you made on a real 2000XL and run it through your favorite software effects, via 10 individual mono outputs if you wish. Let VMPC2000XL control your software instruments via MIDI. Or maybe you want to add some of the MPC workflow to your projects just for parts of the beat.

By exposing VMPC2000XL in standalone, LV2, AU and VST3 formats it is completely up to you.

Manual installation (Ubuntu 18)

At the moment there is no package of VMPC2000XL for any Linux distribution. If all goes well and the project is in good enough shape, and if enough Linux audio users ask for packages, these will hopefully become available.

Some effort was put into making VMPC2000XL more attractive for the Linux community, for example by following the XDG Base Directory Specification. Various self-contained standalone and LV2 Ubuntu builds are provided. You can generate ninja and Make build files.

Suggestions, or even better, contributions, to improve the Linux side of VMPC2000XL are welcome.

For now the recommended process for Ubuntu 18 is as follows:

As per the Filesystem Hierarchy Standard, the recommended location to store the portable VMPC2000XL executable is in /usr/local/bin.

As per the LV2 docs, the recommended location to store VMPC2000XL.lv2 is one of these:

  • ~/.lv2

  • /usr/local/lib/lv2

  • /user/lib/lv2

The standalone is built with JACK support, which is the recommended driver type to use.

The LV2 has run successfully in Carla.

Builds for other distributions can be requested, or made by yourself.

Building from source

You should be able to build VMPC2000XL on many platforms, for example most Linux distributions.

If you wish to build the VMPC2000XL JUCE implementation as is, which is the implementation used for the available binaries, please follow the instructions here.

Additionally the project has been set up in such a way that alternative front-ends can be implemented. Start exploring the source code of the JUCE implementation.

The main idea for an alternative front-end is to do what vmpc juce is doing, i.e. exchange audio i/o with and direct controller input into mpc and present the state of this library’s core entity, Mpc, and its children, to the user. This presentation can be for example an ASCII display, a hardware LCD or a vector GUI, and the controller input can come from a dedicated MPC-like board. A somewhat functional VR concept was implemented in Unreal.

Install using the installers (MacOS/Windows)

The installers allows you to select which format(s) (standalone, VST3 and AU) you want to install. After installation you can place move plugins from their default directories (see below) to anywhere you like.


The MacOS installer deploys universal binaries, compatible with Intel and Apple Silicon systems, in standalone, VST3 and AU formats. Plugins are installed in /Users/you/Library/Audio/Plug-Ins.


The Windows installer deploys 64 bit binaries on 64 bit systems, and 32 bit binaries on 32 bit systems, in standalone and VST3 formats. The VST3 is installed into C:\Program Files\Common Files\VST3 on 64 bit systems, C:\Program Files (x86)\Common Files\VST3 on 32 bit systems.

Important note for Windows users

If you experience missing DLL errors when attempting to run VMPC2000XL after a successful installation procedure, you are probably missing a Microsoft update which you can grab from here:


If you have installed VMPC2000XL before, the installer may offer various options to migrate your previous configuration and user data. Please run the installer to see what applies to your system.

In general it is recommended to regularly backup your data, especially before right updating VMPC2000XL.

Additionally the update process may not always succeed in cleaning up the old application files. Please refer to the Uninstall section below if you come across any files you’d like to delete, or simply want to clean up what can be.



Remove /Applications/ for v0.3 and later. Remove /Applications/ if you have v0.2 or older.

Plugins can be removed from /Library/Audio/Plug-Ins.


Run any VMPC2000XL and vMPC uninstallers you have in Add/Remove Programs.

Assuming you have installed VMPC2000XL into its default location, you can manually delete C:\Program Files\VMPC2000XL and C:\Program Files\vMPC afterwards. On 32 bit systems, and some v0.2 and older installations on 64 bit systems, you can delete the same directories from C:\Program Files (x86).

VST3 plugins can be removed from C:\Program Files\Common Files\VST3, C:\Program Files (x86)\Common Files\VST3 or any other locations where you store plugins.


As per the Filesystem Hierarchy Standard, you have likely placed your portable VMPC2000XL executable in /usr/local/bin.

As per the LV2 docs, you likely have your VMPC2000XL.lv2 in one of these locations and can remove it from there:

  • ~/.lv2

  • /usr/local/lib/lv2

  • /user/lib/lv2


For a full cleanup including demo beats, configuration files and user data (your sounds, sequences, etc.), refer to the File Locations section below and delete from those what you wish.

File Locations

For locations of the executable and plugin binaries, refer to the Uninstall section above. The discussion below is restricted to all other files that are installed and generated by VMPC2000XL.

There are three categories of files:

  1. Demo recovery data: Demo beats that are never modified by VMPC2000XL

  2. Documents:
    • Everything you create: VMPC2000XL/Volumes/MPC2000XL

    • Direct-to-disk recordings: VMPC2000XL/Recordings

    • Log file: VMPC2000XL/vmpc.log

  3. Configuration files:
    • Keyboard mapping: config/keys.txt

    • NVRAM data (main screen user defaults): config/nvram.vmp

    • VMPC2000XL-specific: config/vmpc-specific.ini

    • Audio/MIDI configuration and auto-save data: VMPC2000XL.settings

    • USB volumes: volumes.json

On MacOS and Windows, demo data is bundled into the installer, which places it in a safe location from which it can always be restored. When you start VMPC2000XL, a check is performed to see if a DEMOS directory exists in your user data directory. If not, a fresh copy of the original demo data will be placed in VMPC2000XL/Volumes/MPC2000XL/DEMOS.

Resources that are absolutely required by the application, such as background images and the metronome click PCM WAV data, are bundled into the executables and plugins, making them fully portable and self-contained. Hence you will not find such files anywhere in your filesystem.


Demo recovery data Unavailable

Documents ~/Documents/VMPC2000XL

Configuration files ~/.config/VMPC2000XL/config and ~/.config/VMPC2000XL.settings


Demo recovery data /Library/Application Support/VMPC2000XL/DemoData

Documents /Users/you/Documents/VMPC2000XL

Configuration files /Users/you/Library/Application Support/VMPC2000XL/config and /Users/you/Library/Application Support/VMPC2000XL.settings


Demo recovery data C:\Usersyou\AppData\Roaming\VMPC2000XL\DemoData

Documents C:\Users\you\Documents\VMPC2000XL

Configuration files C:\Users\you\AppData\Roaming\VMPC2000XL\config and C:\Users\you\AppData\Roaming\VMPC2000XL\VMPC2000XL.settings

File Locations (v0.3 and lower)

In older releases most non-application files are stored in /Users/you/vMPC on MacOS and Windows.

On Linux most non-application files are stored in /home/you/vMPC.

When you are cleaning up, you can remove this vMPC directory completely, or you can backup your sounds, sequences, programs and so on from vMPC/Stores/MPC2000XL.

On Windows audio/MIDI preferences are saved in C:\Users\you\AppData\Roaming\vmpc.settings.

On MacOS this is /Users/you/Library/Application Support/vmpc.settings.

On Linux it is ~/.config/vmpc.settings.