anyone found a source for new mpc synth presets?

Thanks for the update and explanation.

Not to belabor the point, but I'm a bit confused about about this "currently the best way is still to offer presets inside an expansion and browse the presets in the expansion browser (audio previews for xpl files do now work here)."

Also, does the same apply to custom presets for effects ?

What are you specifically confused about? The technical limitations of installing presets as described, or that expansions are imo the best way to distribute?

droctii wrote:Thanks for the update and explanation.

Not to belabor the point, but I'm a bit confused about about this "currently the best way is still to offer presets inside an expansion and browse the presets in the expansion browser (audio previews for xpl files do now work here)."

Also, does the same apply to custom presets for effects ?

I understand the current limitations of bulk installing custom presets. I'm wondering how custom presets in expansions work with Akai's instrument plugins. Or am I missing something here?

Additionally, while it would be time-consuming to install custom presets manually, the hour or two (or three) of doing that may be worth it for some people. We have all spent hours setting up computers and weight the long-term benefits of such as greater than not doing it.

droctii wrote:I understand the current limitations of bulk installing custom presets. I'm wondering how custom presets in expansions work with Akai's instrument plugins. Or am I missing something here?

The preset files would be listed in the right hand side of the expansion browser, double tap and it creates a plugin program with that custom preset loaded. Load another preset and it will replace the currently loaded preset. You can save any of these individually as user presets. This is the only official way to install presets to a plugin, and this way they will be available in the sounds browser.

but yes, it would take a while to install them this way.

Thanks for explaining.

I note what you say about it taking time to install them manually. Some people may find it worth it if the option to purchase a well-done custom preset pack is available.

MPC-Tutor wrote:So currently the best way is still to offer presets inside an expansion and browse the presets in the expansion browser (audio previews for xpl files do now work here).

Wait.. audio previews do NOW work? Or did you mean to say "do NOT work"?

Yes they work with any file type recognised by the browser, e.g. mid, pattern, plugin, sqx etc. Not sure when this happened, I think it may have been ages ago and I just didn't notice (or maybe I messed up originally and it was always supported!).

EnochLight wrote:

MPC-Tutor wrote:So currently the best way is still to offer presets inside an expansion and browse the presets in the expansion browser (audio previews for xpl files do now work here).

Wait.. audio previews do NOW work? Or did you mean to say "do NOT work"?

Theoretical things that can be done
- One could cook up a script that generates random synth patches offline (sort of possible, I had a look at the file format of a couple of them and there's some weird redundancy in there, almost like a hash check, didn't try generating a random patch yet)
- IIRC, the SD card looks for a boot file and could be used to launch a shell script that copies newly downloaded patches from the SD card into the system SD (where the user can't access). This is most likely doable but it's not recommended as the user can bork the presets list and that can get messy (like the synth plugin not loading at all etc).
- There is an SSH enabled version of the MPC firmware that allows access to the internal SD card so the user can copy and manage the presets (but it's not for the faint of heart and touching any system internals is way too tempting there and user WILL bork their MPC when they go messing around)

It sort of looks to me, by the way things are going, that they will implement their own shop app in the MPC OS where you can buy and install presets and plugins (closed ecosystem like what Roland has). But this might be years ahead from now.

Yes, I'm assuming the are heading towards the walled-garden approach and eventually any remaining third party installation options will seem too archaic for most users, not when they can just download everything automatically from the preferences screen.

Hello, I programmed some Tube Synth sounds and ran into the same problem.
I made some synth programs for the TubeSynth on my One and want to save them to the card and swap that to a second MPC One that I intend to use for live performance.
I made a folder for those sounds on the card "Progs TubeSynth" and used the "pencil" on the right and "save program" function. I noticed it did not use the programname, just "Plugin001". Well... saved it with that name to try. While loading that on the second machine, it said "program already exists", but did load nontheless. After loading I saw one sound I made, but as soon as I scrolled further it showed garbage names first, then normal ones. The custom sound has vanished. There is also no "User" bank visible in the overview, like it is on my other machine. So... how do I copy the custom synthprograms content to a second machine? Obvioulsy it does not work the way I did.
After that I searched and ended up here. Since 22 we have received new update(s) (I guess?), are there any news about that issue?

Kaffimusic wrote:Hello, I programmed some Tube Synth sounds and ran into the same problem.
I made some synth programs for the TubeSynth on my One and want to save them to the card and swap that to a second MPC One that I intend to use for live performance.
I made a folder for those sounds on the card "Progs TubeSynth" and used the "pencil" on the right and "save program" function. I noticed it did not use the programname, just "Plugin001". Well... saved it with that name to try. While loading that on the second machine, it said "program already exists", but did load nontheless. After loading I saw one sound I made, but as soon as I scrolled further it showed garbage names first, then normal ones. The custom sound has vanished. There is also no "User" bank visible in the overview, like it is on my other machine. So... how do I copy the custom synthprograms content to a second machine? Obvioulsy it does not work the way I did.
After that I searched and ended up here. Since 22 we have received new update(s) (I guess?), are there any news about that issue?

Plugin 001 is the default name for the first plugin program you make in a project. A plugin program is required to load a plugin into. If you configure a plugin patch within this program it stores the plugin settings including the preset configuration. Give this program a unique name and save it to your disk and it will recall the plugin settings whenever you load that plugin program and assign it to a track.

However, it does not save the actual custom 'preset' itself (the XPL file). If you want to save this, press the 'disk' icon in program edit and save the preset - use the default location ot save it to the user folder on your current MPC. If you want to use the preset on a different machine, save to an external disk. Then on your other machine, open up your project, select your plugin, go to program edit and press the 'folder' icon at the top of the screen. Load your preset into the plugin. If you want to permanently save the preset in your user folder on this machine as well, hit the 'disk' icon in program edit and save it to the default location it offers you.

Thank you for your answer. I understand. My mistake was to save it from the main screen, but not from programedit.
But obviously there is still no way to transfer a bunch of them the same time?

Kaffimusic wrote:But obviously there is still no way to transfer a bunch of them the same time?

If it's a synth stored on an external drive then yes you can transfer in bulk as the presets sit in an accessible 'presets' folder, but not officially supported, and ideally requires each preset name starts with a completely unique number not used by any of the factory presets. It's what I did for my Fabric XL preset pack:

https://www.mpc-samples.com/product.php ... n-presets/

But that's not really sold so I won't be bothering with any more commercial preset expansions, complete waste of time.

when saving presets try to follow special naming convention for easier management later on, file name structure should look like this:

preset number-preset category-preset name.xpl

* preset number is the number from 000-999 - akai presets usually occupy first 300 positions so it's safe to start at 500.

* preset category is nothing but a special, virtual folder in your browser that let you separate your presets from the factory ones. You can name it whatever you like in order to make that separate category or put a name of existing category such as "Bass" for example. This will store your presets along the factory "bass" presets.

* preset name is self explanatory...

given all of above, your example file name should be like this:
513-CustomBass-Balls To The Wall Bass.xpl

Now, once you have all of your presets organized, drop them into one single folder called whatever (custom_presets or something) and drop that folder into SYNTHS/PluginName/Presets in your MPC

Thanks for the answers. Phew, this is... not awesome. Just the process of renaming everything, is no fun. Did you rename them with your computer or by typing everything into the MPC while saving to external drive?
I have spent some time today, loading them one by one, and even so saving them to the automatic folder on the device. But "technology today" ist something different.
However, thank you for the hints, when my amount of programs is rising above 30 I will do it this way.
Wait, but... what if I would give them the same name and the same prefix for the folder "user", but a number starting with 500+, what will happen to the sounds that are already in the machine with a lower number but the same name?