The Vault 2.0 and MPC One

I just registered my MPC One with Akaipro.com. I downloaded the F9 instruments expansion, MPC Standalone, no problem. I copied it to SD card and it recognizes the expansion and I've been playign around with the sounds on the MPC... sound great.

Then I downloaded The Vault 2.0 expansion for MPC Live/One MAC. The download actually says MPC Live Mac. It installed on my mac, but it didn't say where and also didn't say how I get it onto my MPC One. I found the files under /LIbrary/Application Support etc.. and trying to copy the expansion from there onto SD card. Surely, there is an easier way to get The Vault 2.0 on my MPC One? Is there some software I install on the MAC? It isn't clear what software after registering my product.

You'll need to use the software and export the expansion to the SD card you use on your One

EDIT: To be more clear... you'll need to use the MPC Software, it has an option to export expansions installed onto the computer to a directory of your choice.

Thanks. I guess I need to instal 2.8.1 MPC software on my mac. The software is called that as well.. same as the firmware version.

hello,
i have MPC one and the vault 2.0

i see now the xmas offer Day 8 - The Vault MPC Pack
is it the same content?
thx

Castelmau wrote:hello,
i have MPC one and the vault 2.0

i see now the xmas offer Day 8 - The Vault MPC Pack
is it the same content?
thx

There is a lot of overlap between the two, you should be fine with just 2.0

Thanks for the clarification kaydigi. I was kinda curious myself, with The Vault/The Vault 2.0 and Essential Instruments 2.0. Wondering if there’s a previous version of that or if it just means it was created for MPC 2.0+ version software/firmware.

I noticed that V1 has 5.8G contents and 8 projects
V2 has 3.8G contents and no projects

Projects in these expansions often just re-use the kits found in the main library, so you are not necessarily getting any additional kits or instruments with the project files, just duplicates.

I find it funny that so many companies use large file sizes as some kind of selling point, especially when we're dealing with standalone machines with limited memory, surely optimised memory footprint is more of a selling point. Personally I'd prefer to see the developer take the time to reduce file sizes (without impacting quality of course).