Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
User avatar
By Ultros Sat May 07, 2022 2:37 pm
Your MPC uses a real time kernel which means all threads are ticking. The kernel makes sure time critical events are processed with a high priority.

Which means instead of halting and waiting for the sub processes to finish and lagging it actually bottlenecks in real time while you run out if resources and comes out audibly.
User avatar
By DeaDeus Mon May 09, 2022 3:13 pm
True - my Virus Ti has the same behaviour - or say it that way - probably all synth with options to run literally dozens of synth/drums plus millions of filter combinations, will end up with this issue.
Even if they would put a 16 core 4.8Ghz in it, one day somebody would mention that it came to note drops.

My thought anyways...

Edit: my tip would be - use less but more effective.

btw.: Access mentioned the "reverb" as a very processor intensive effect, and to use a short delay instead. Might be Virus specific issue, but it will not hurt to think about it elswhere too.
User avatar
By Ultros Mon May 09, 2022 5:02 pm
DeaDeus wrote:True - my Virus Ti has the same behaviour - or say it that way - probably all synth with options to run literally dozens of synth/drums plus millions of filter combinations, will end up with this issue.
Even if they would put a 16 core 4.8Ghz in it, one day somebody would mention that it came to note drops.

My thought anyways...

Edit: my tip would be - use less but more effective.

btw.: Access mentioned the "reverb" as a very processor intensive effect, and to use a short delay instead. Might be Virus specific issue, but it will not hurt to think about it elswhere too.


That's right, at the point when things start grinding to a hault is a good indicator its running outta processing power. Bouncing stuff to samples isnt a bad idea since playback of .wav is less cpu intense but comes at the cost of being ram intense.

cpu's are freq based too but when they get smashed with a stream thats math intense they require time to do those tasks and as it chugs data is being missed as the stream goes by in real time. unlike a standard kernel would instruct the cpu to do with a lower priority / wait to insure data is processed.