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 Sun Dec 29, 2024 7:57 pm
All I want is enough bandwidth that the device is stable to produce music with. We have all experienced losing a song we are working on every single one of us. It doesnt have to happen if we had a platform with enough room for the system they have developed.
By BeatWilson Sun Dec 29, 2024 7:59 pm
The thing is by answering with something like... "So: it can crash if you use too many plugins. Don't use too many plugins." This really doesn't solve a thing...
You see what he's talking about leaks into all other area's of this machine without the prioritizing.
It's like how recently there's talk about the Akai Plugins creating 4ms of latency for each one added and someone answered "well just use air plug-ins" which yes... we get it but also... you can see how, once again, it doesn't truly solve the issue that these machines are sorta only "ok" at everything, instead of actually good at the one thing they were originally designed for. Akai has everyone jumping through hoops. Being beta testers for them, because they lazy asf, or don't have a large team, which I find sorta hard to believe. Inmusic, Akai, DenonDj, Rane, all use the same processors. They keeping everyone in standstill with there marketing crap. By doing this, with some terrible code writers... issues come out, such as, having too many plugins, latency when tracking out, too many hardware synths and samples at once, too many fx, and so on... I could keep going.. When this issue happen, there is no notification, or warning, so you gotta sit there... figure it out for yourself. Atleast when ya run out of memory, it tells you. It doesnt tell you that every track you have playing are completely out of sync by "X" Amount of ms. They should of prioritized the midi, sequencing first with there code, but they did not. It's barely hanging in there at times. Even in windows you can unpark cores, or set priorities as far as what application should get how much juice from the computer. I've tried 3.4 only a couple times, but I'm not hugely impressed.
User avatar
By Ultros Sun Dec 29, 2024 8:12 pm
yeah, in laymens terms the physical box doesnt have enough computing power to deliver what the software is configured to do. couple that with actual logic bugs in code and ey bada bing you got this... i am sure they are well aware of it and have something else in cue for the horizon.. its not a giant leap to move from 32bit arm to 64bit arm.. just when god damn it when.. lol
By HouseWithoutMouse Sun Dec 29, 2024 9:31 pm
BeatWilson wrote:The thing is by answering with something like... "So: it can crash if you use too many plugins. Don't use too many plugins." This really doesn't solve a thing...
You see what he's talking about leaks into all other area's of this machine without the prioritizing.
It's like how recently there's talk about the Akai Plugins creating 4ms of latency for each one added and someone answered "well just use air plug-ins" which yes... we get it but also... you can see how, once again, it doesn't truly solve the issue that these machines are sorta only "ok" at everything, instead of actually good at the one thing they were originally designed for. Akai has everyone jumping through hoops. Being beta testers for them, because they lazy asf, or don't have a large team, which I find sorta hard to believe. Inmusic, Akai, DenonDj, Rane, all use the same processors. They keeping everyone in standstill with there marketing crap. By doing this, with some terrible code writers... issues come out, such as, having too many plugins, latency when tracking out, too many hardware synths and samples at once, too many fx, and so on... I could keep going.. When this issue happen, there is no notification, or warning, so you gotta sit there... figure it out for yourself. Atleast when ya run out of memory, it tells you. It doesnt tell you that every track you have playing are completely out of sync by "X" Amount of ms. They should of prioritized the midi, sequencing first with there code, but they did not. It's barely hanging in there at times. Even in windows you can unpark cores, or set priorities as far as what application should get how much juice from the computer. I've tried 3.4 only a couple times, but I'm not hugely impressed.


All of the things you're talking about are software issues. Plugin delay compensation to keep signal paths time-aligned, it's a software feature. CPU overload detection and management, it's a software feature. Protection from corrupting project files on disk, it's a software feature.

I can't see how fragmenting the hardware base would help in writing any of that code. But I can see how it would make things more difficult.

Maybe Ultros is saying that Inmusic will never be able to get their coding shit straight anyway, but at least with more processing power, CPU power related stability issues could be eased?
User avatar
By Lampdog Sun Dec 29, 2024 9:38 pm
Akai didn’t just pack up and quit. There is always something on the horizon.
By B-Wise Sun Dec 29, 2024 10:18 pm
Lampdog wrote:Akai didn’t just pack up and quit. There is always something on the horizon.


Something on the horizon could mean the same or worse bugs. Before Akai drop the current gen, they were what was on the horizon & now in the current time they have old ass bugs the past units didn't have. They make up for it with having more features. MPC3 is the same old **** just with a face lift, a boob job & funky BBL. :lol:

I hope the new gen is coded better so when there are new bugs they're not so hard to kill like roaches. It seems like they tried do some special proprietary code & the people that who knew how to work it left like JJ & the remaining team only know enough to patch it up like bandaid & add new features but can't fix the main problems.
User avatar
By DJ_GodsOwn Mon Dec 30, 2024 12:43 am
Ultros wrote:
HouseWithoutMouse wrote:It's not beaten to death. Bugs and usability issues remain! How much CPU and memory and other computer geek numbers does it take to have proper legato for keygroup instruments? At what GHz value does the MIDI note-off bug disappear?


Ok so in WHAT VERSION of update are they gonna solve that god damned bug. I have a folder with 20-ish rom images it persists across. It would be a valid arguement if inMusic was writing stable code but they arent. A prime reason to flat out abandon MPC until an all new product with all new software and hardware design come along because this rn is garbage.

Peoples projects bind and bottle neck all the time and they lose their work, too many fx? wrong combo of fx? kiss your stuff in memory and current state good bye. are you unwilling to recognize this issue? thats due to it not having enough bandwidth on an RT system.

the current software design has passed hardware capability, long ago.. and the software is screwed up in its own way too. Even their new beta is a buggy pos that does not operate well on any piece of hardware it resides on.

You keep arguing this point with me but its clear that you don't comprehend on a real time system bandwidth has a factor on performance and people are finding that limit all the time in the strangest of ways. Who gives a crap about the midi bug thats piddly in comparison to it crashing and tossing your project in the garbage all because you added the whatever garbage ass plugin you paid $100 for to your project. That is happening and it cannot be addressed via software bud.

Let me tell you about kernel preemption so you fully comprendo wtf real time means. On a regular system with kernel preemption your tasks are all prioritized and interleve in a timed manner relative to thread priority. On a real time system tasks are excuted immediately, there is no priority for rt tasks the moment you execute it it's using as much processor as it needs to get the task done. Now start heaping tasks on to a cpu without prioritization and you end up with an operating system that by design requires bandwidth to be open to the software.... It will allow you to heap tasks on it until the cpu literally runs out of space to insert tasks and start chugging and this is where you see projects disappear. So yes with RT if you up your bandwidth you get a more stable system with more room to process tasks.

Then we can get into a thing called "thread affinity" where we assign tasks to the various cores to make good use of the processor. The processor that has 4 underpowered 32bit cores that cant keep up.

Just fly me into hq for a **** week and ill help fix it **** me.. my rt systems don't suck or crash.


I never have any issues with my MPC Key 61 crashing, and my CPU and memory usage are always pretty low. I'm making boom bap type hip hop and occasionally house music with it. I've used quite a few plugins in some tracks as well that I've done. I can't image what someone would be doing with the device that would use up all those resources. I guess people must though or it wouldn't be an issue. :o
By HouseWithoutMouse Mon Dec 30, 2024 12:46 pm
The problem is, the software does not prevent the user from overloading the CPU with plugins. For these kinds of users there should be a hard safety limit.

My projects are very light on the CPU, and the crashes I've had with my Force have happened when doing an operation of some kind. Load a sound, undo, etc. Seems like plain old bugs. The most annoying bugs are completely fixable, like envelope followers being inoperative upon loading a project. WTF, did they not test the whole feature at all? And then there are usability issues like with the MIDI editor view scrolling to hell all the time, or that the Odyssey plugin's LFO modulation pitches upwards only which makes the mod wheel unusable. Or having to re-browse through the whole catalog of tracks and parameters to change a macro control's target. Keygroup instruments don't have non-retriggering legato, so you can't do proper lead synths with samples. I have not encountered an issue that would be solved by adding CPU power.
User avatar
By jaymack Mon Dec 30, 2024 3:10 pm
For real. Tighten up what you got first before you go releasing another bug filled unfinished product.
By Straker Mon Dec 30, 2024 4:43 pm
I read on Gearslutz that Akai is gonna release soon a new Mpc with 50gb Ram, 59 Tera internal ssd, with original Fender Rhodes ™ keybed 88 keys, Bose ™ high quality stereo speakers underneath, real diamond pads and qlinks, real time warp stems pro tools ™ algorithms, all for 999$.
Anyone can confirm?
By BeatWilson Mon Dec 30, 2024 7:29 pm
I can confirm this. I was in jail, ran into Dan in there. It was a Mpc-ini-Mini-Moe. During that time he showed me the new product. It was so small he could sneak it in. :lol: I was a little surprised. :smoker: :hmmm:
User avatar
By pk1 Mon Dec 30, 2024 9:51 pm
:lol:
:popcorn:
By Straker Tue Dec 31, 2024 12:55 am
BeatWilson wrote:I can confirm this. I was in jail, ran into Dan in there. It was a Mpc-ini-Mini-Moe. During that time he showed me the new product. It was so small he could sneak it in. :lol: I was a little surprised. :smoker: :hmmm:

No, that's Mpc16, it will be released on 2031. It's small as you said but gets bigger then MpcX as you switch it on. Future technology. Unfortunately it will have all the unsolved bugs of 2021/2031 decade, because Akai loves bugs and thinks they have some use in future music.
But I cannot say more. Dan is in jail because he discovered the time machine but he doesn't want to share this knowledge with government.
He showed you a glimpse of it.
I cannot say more, I am already saying too much.
Dm me if you want, but use pro encryption.