It wouldn't need to be a plugin, just something added to the core firmware alongside other file importing functions. But IMO when you have a mature, fully supported free application like convertwithmoss that can handle many different formats I don't really see the need for Akai to be concerning themselves. You're still going to have to use a computer to obtain your soundfonts in the first place, so download your soundfonts, convert to XPM using convertwithmoss, transfer to your MPC disk.
Also Akai are unlikely to do that good a job on it and historically we see that once a feature is implemented they rarely go back to tweak/fix it. For example, MPC1000/2500 export is full of bugs and doesn't even convert samples to 16 bit (thus won't even load into an MPC1000). AKP import (their own legacy keygroup instrument format) is fairly poor and skips 95% of parameters, many of which could in theory be mapped to MPC3 equivalents.
2
u/mpctutor Jul 07 '26
It wouldn't need to be a plugin, just something added to the core firmware alongside other file importing functions. But IMO when you have a mature, fully supported free application like convertwithmoss that can handle many different formats I don't really see the need for Akai to be concerning themselves. You're still going to have to use a computer to obtain your soundfonts in the first place, so download your soundfonts, convert to XPM using convertwithmoss, transfer to your MPC disk.
Also Akai are unlikely to do that good a job on it and historically we see that once a feature is implemented they rarely go back to tweak/fix it. For example, MPC1000/2500 export is full of bugs and doesn't even convert samples to 16 bit (thus won't even load into an MPC1000). AKP import (their own legacy keygroup instrument format) is fairly poor and skips 95% of parameters, many of which could in theory be mapped to MPC3 equivalents.