groovemonger wrote:I have no idea why Akai are now jumping on board Microsoft's latest stab at embedded. Okay, if it's so embedded that it's merely something to place a typical MPC interface on top of, that's okay. No one cares what's under the hood.
I wouldn't characterize it as a "stab". We've had embedded versions of Windows for something like 20 years, going as far back as Windows 3.1 embedded. Most kiosks, ATMs, digital signs, etc. run Windows Embedded. A lot of medical and shop floor equipment does as well. (A fair number of cars also run versions of Windows, but that's our somewhat unrelated auto/nav offering.)
The nice thing about full Windows Embedded is it can run all the same software you run on your desktop. That means there's zero programmer learning or porting curve to move software over. Combine that with the fact that you can optimize it like crazy should you (the developer/OEM) want, and it certainly seems like a smart decision. The ability to ensure it runs only the software that should be installed means no worries about making it a multi-purpose email/facebook/whatever machine, with the potential stability and support questions that would raise.
When you run on embedded, you (the developer/OEM) have 100% access to all the hardware, using the drivers you want to use. As you can imagine, this lets them make sure any ASIO, network, etc. drivers are the perfect ones to match the hardware and perform best.
Finally, InMusic gets to brand it any way they want. Like the typical ATM, most people, unless they saw this thread, probably wouldn't even know it ran Windows unless InMusic wanted to publicize that.

I can't speak for why InMusic picked Windows Embedded Industry 8.1 for the MPC and the new NS7 (I only worked with them on presenting their work at Build), but I suspect the software portability and tools/API compatibility had a fair bit to do with it.
Pete