HouseWithoutMouse wrote:What concrete issue will a new SOC solve? That the software is proprietary and Akai sits on it and you can't fix their bugs and make it work like you want? If the current product doesn't work like you'd like it to, will the situation change if there's more CPU and RAM? I'm using the Force and none of the issues have pretty much anything to do with the SOC and its "gen", it's all about the software and things like not being able to tilt the screen. IMO.
I guess I'm saying that the potential of the previous-gen hardware in the existing products is far from being fully exploited. What was the biggest thing people got excited about here - 4GB RAM, woohoo ... why? So they could spend even more time loading even more samples from disk entirely to RAM?
what we gain is raw performance. the system uses a real-time kernel. threads do not *wait* for one another. there's no "kernel preemption" which means all the data flows through the processor as fast as you can tell it to. Raw performance matters with Real-time systems.
The gain would be we would no longer hear the MPC cracking an popping because its at the brink of its performance, this happens because the cpu cant keep up. it wouldn't cak out and crash on you murdering off your work like it does now. We could also then run network audio because we would have the resources to relay the audio streams over ethernet.
for example i have used "jack" to relay the audio over ethernet to my pc so i can track the mpc into reaper over multiple lanes. The current hardware struggles to keep up with the mpc software now, hence our audio drop outs and crashing of the audio interface on the regular. It's not inMusics fault or any sort of *bug* its just by nature that when using RT (Real time) systems that they will eventually sputter if you over load the processor.
Ego te absolvo.