2.11.7 is out now...

So what is the lastest firmware that works with audio interface and with the least amount of bugs?
I see the mention of 2.11.5 as more stable. I have tested so far 2.11.6 tons of bugs... Audio clicks issues with midi causing crashes of the interface, bounce to Audio... You name it.

2.11.7 bounce to Audio works but no favorites or user presets... A real pain in the neck. Still some clicks audio interface sounds worse than the 1969 Apollo audio from the moon

Lancerben wrote:So what is the lastest firmware that works with audio interface and with the least amount of bugs?
I see the mention of 2.11.5 as more stable. I have tested so far 2.11.6 tons of bugs... Audio clicks issues with midi causing crashes of the interface, bounce to Audio... You name it.

2.11.7 bounce to Audio works but no favorites or user presets... A real pain in the neck. Still some clicks audio interface sounds worse than the 1969 Apollo audio from the moon

There is no best 2.11, they all have issues, basically pick the one that you can live with until Akai get their shit together. Many still prefer 2.10.1, but then you have no support for the newer plugins.

hi I'm a new user and also updated to 2.11.7 recently. Just today I hook up my Scarlet 6i6 1st gen and I'm getting audio crackles. In the forums it's said to work fine. So anyone using the similar interface and functioning without any issue and have a a different OS? Would be great to hear your advice!

I am having the same problem with all of my audio interfaces. I have given up on using audio interfaces with my MPC Live II. Sad thing is it used to work when 2.10 first came out.

IMO....The reason why there are so many Bugs, is because...Akai is trying to Cram in Too many features into 6-7 year old Hardware Infrastructure.

Imagine a FULL Pot of Boiling Water on the Stove. What happens when throw in a Few Fresh Eggs. Sh*t Spills out of the Pot. Important Infrastructure is being starved because there's not enough Space to Move About...hence (Bugs)

The Only Logical way to handle more Features is to Drop NEW Hardware with New, More Robust Circuitry that can handle it with more speed and RAM, Internal Drive Space, etc

Imagine Cramming 2023 Modern Features into a 1991 Yugo!

Terry Bollea wrote:I am having the same problem with all of my audio interfaces. I have given up on using audio interfaces with my MPC Live II. Sad thing is it used to work when 2.10 first came out.

fwiw i'm on 2.11.4 with no issues on my interfaces. (behringer 204 and 404)

40Beatz wrote:IMO....The reason why there are so many Bugs, is because...Akai is trying to Cram in Too many features into 6-7 year old Hardware Infrastructure.

Imagine a FULL Pot of Boiling Water on the Stove. What happens when throw in a Few Fresh Eggs. Sh*t Spills out of the Pot. Important Infrastructure is being starved because there's not enough Space to Move About...hence (Bugs)

The Only Logical way to handle more Features is to Drop NEW Hardware with New, More Robust Circuitry that can handle it with more speed and RAM, Internal Drive Space, etc

Imagine Cramming 2023 Modern Features into a 1991 Yugo!

On top of this, it seems like all the new features are just being 'tacked on' to the OS as well, hence why every time a new release comes out several other things break. Instead of proper planning and proper integration, they're just 'OH LOOK NEW PLUGINS ADDED' that breaks basic features like incoming MIDI cutting itself off.

From the looks of it, the folks who claim they dont listen to their beta testers reports are dead accurate heh.

New sales can only come from new plugins and features. This drives the updates. Fixing bugs is expensive to them and won't attract new buyers.

40Beatz wrote:IMO....The reason why there are so many Bugs, is because...Akai is trying to Cram in Too many features into 6-7 year old Hardware Infrastructure.

I don't think that the hardware is the root of the evil. From the outside I expect old code that has been tinkered with endlessly beyond the original scope. Probably the whole thing is by now a bloody mess no software developer really wants to touch but marketing forces them to add stuff again and again.

Options are either to abandon the current OS in some form and create a new version that is not campatible withe legacy hardware or stop developing any features or plugins for a year and devote all energy on creating automated tests and do some refactoring for cleaning up the code.

Otherwise folks will really start to leave a bug-ridden platform. I thought I could perform for friends when I bought an MPC One. It has already crashed too many times form me to trust if for live usage.

Masi wrote:I expect old code that has been tinkered with endlessly beyond the original scope. Probably the whole thing is by now a bloody mess no software developer really wants to touch but marketing forces them to add stuff again and again.

IMO that is exactly what has happened. The marketing speak at namm a few years back claimed to have re-coded from the ground up with MPC 2.0 (but I have my doubts), but even so, since then they just seem to be shoe-horning in new features, and with each release core features get broken and plenty of features remain half finished and ill thought out.

Definitely seems to need a complete re-working from the ground up, but I suspect this is unlikely to happen.

40Beatz wrote:IMO....The reason why there are so many Bugs, is because...Akai is trying to Cram in Too many features into 6-7 year old Hardware Infrastructure.

Imagine a FULL Pot of Boiling Water on the Stove. What happens when throw in a Few Fresh Eggs. Sh*t Spills out of the Pot. Important Infrastructure is being starved because there's not enough Space to Move About...hence (Bugs)

The Only Logical way to handle more Features is to Drop NEW Hardware with New, More Robust Circuitry that can handle it with more speed and RAM, Internal Drive Space, etc

Imagine Cramming 2023 Modern Features into a 1991 Yugo!

think u have it wrong; I think the issue with the software is the software, why would u put the issue as the hardware?
Akai is adding features and potentially making the application into a bloatware; but the issue is simply due to lack of testing and the amount of features being added, more likely.

MPC-Tutor wrote:

Masi wrote:I expect old code that has been tinkered with endlessly beyond the original scope. Probably the whole thing is by now a bloody mess no software developer really wants to touch but marketing forces them to add stuff again and again.

IMO that is exactly what has happened. The marketing speak at namm a few years back claimed to have re-coded from the ground up with MPC 2.0 (but I have my doubts), but even so, since then they just seem to be shoe-horning in new features, and with each release core features get broken and plenty of features remain half finished and ill thought out.

Definitely seems to need a complete re-working from the ground up, but I suspect this is unlikely to happen.

A couple years ago when Akai Dan was still in the mix over at the GS forum, he claimed 3.0 was going to require a complete rewrite too, wonder what ever happened to that?

Monotremata wrote:he claimed 3.0 was going to require a complete rewrite too,

I think the whole code rewrite idea was related to the complexity of incorporating arranger and disk streaming into the way the MPC had originally been coded, I think it was easier to implement on the Force as it had been built structurally different to the MPC (complete assumption on my part).

But he seemed to be thinking out loud rather than revealing any concrete future plans. I'm still not convinced we're going to see any of that on the MPC, maybe one day they'll just merge both units into an 'MPC Force'. The Force is really pretty good and can be more flexible than the MPC in many respects. But like the MPC is suffering from increasing numbers of bugs.

jpeg wrote:

40Beatz wrote:IMO....The reason why there are so many Bugs, is because...Akai is trying to Cram in Too many features into 6-7 year old Hardware Infrastructure.

think u have it wrong; I think the issue with the software is the software, why would u put the issue as the hardware?
Akai is adding features and potentially making the application into a bloatware; but the issue is simply due to lack of testing and the amount of features being added, more likely.

They've been Testing different features for YEARS. Even when they use Us as "Beta Tester Bait". I put the issue as Hardware because the Firmware is Struggling as a result of what they're trying to pack inside.
The Software Engineers are pulling their hair out tryin to figure out where to Cram these NEW features without disturbing previous enhancements. Meanwhile the Marketing side of things are forcing the issue, trying to figure out how to Generate Revenue from existing Customers...

Again I may be wrong, but that's how I see it. Don't read into it too much lol Only InMusic knows whats goin on

weirdly i got a second 2.11.7 update message from my mpc one directly and after installing it, the user favorites are back