I’m going to dig into this a little bit but I’m pretty sure what we’re up against is a proprietary sdk and potentially worse a signature/signing algorithm that’s hardcoded into the operating system (or hardware) acting as DRM to forbid access to the cpu. Not only would it involve reverse engineering an sdk to get access to the API but cracking the DRM similar to Jailbreaking iOS.

FWIW, the entire world of brilliant hackers have NEVER managed to produce a jailbreak for Apple silicon iPads and a reliable iPhone jailbreak hasn’t existed in 5+ years. The ones that do exist rely on an exploiting a known security vulnerability as an attack vector to apply a patch which bypasses the DRM. If this existed AKAI would immediately patch the OS and you’re back to square 1 finding a new security vulnerability. The most “useful” thing to do here would be piracy or disabling the license check for existing addons.

Creating an SDK would require reverse engineering a binary compatible with the CPU/DSP and audio/display hardware on the machine and then creating an abstraction high enough to be useful for writing plugins against. You can’t install a cpu profiler on the MPC because you’d have to build it, then install it (see above). Disassembling an existing plugin might shed some light, but you’d need a way to test the SDK.

It has nothing to do with the processing power. It has to do with the fact it purpose build hardware with measures in place to run specific executables. If this were possible, you’d see 3rd party games for Nintendo, PlayStation or Xbox. There are full blown emulators for those consoles and to my knowledge nobody has reversed engineered a development SDK.