Audio artifacts and glitches in standalone mode (Live Mk 2)

Hello everyone! This is my first post, but I've done some search and my problem doesn't seem to be happening to anyone, which I don't think is a good sign

I'll paste the message(s) that I left in Akai's support forum (no reply yet), just to see if anyone has experienced the same. First message:

Hi there,

I've noticed a problem with the last version of the firmware (2.11.7) in my MPC Live II. After working for a while with the machine in any project, some audio artifacts (cracks and pops) start to appear in the outputs (they appear in all of the audio outputs: main, headphones and monitors). At first they appear sporadically, but then they occur more often every time and finally they are constantly present, to the point that creating almost like a bitcrush effect.
Projects are not heavy at all:

- CPU doesn't even reach 15% while reproducing
- Memory is below 10%
- Internal drive has 3.6Gb free (about 75% used)
- No internal SSD nor SD card is being used
- No USB devices connected, and the device itself is not connected to any computer

- I've reset preferences several times now, but the problem keeps happening. If I load a new project, the outs start sounding good again for a while, but then it happens all over again.

I would have said that it didn't happen with previous firmware versions (I come from 2.11.3), but I'm not sure since I didn't use it intensively before this. I can only think of freeing up some space in the internal unit and installing an internal SSD, but I would love to hear any suggestions or if I have to send the unit to repair.

Thanks in advance, and best regards,

Second message:

I can confirm that in firmware version 2.11.7 the degradation in sound just after a few minutes using the machine keeps happening. I would like to know if I can go back to a previous version of the firmware just to be sure, but at this point I don't know what else to do.

- I deleted expansions from the internal storage so now there are almost 9Gb free in that unit.
- I installed an SSD in the expansion port, and moved my projects there.
- I updated the firmware using an USB unit.

As an additional information, the unit is not recognized in controller mode by the MPC software in my computer (AMD Ryzen 7 PC running Windows 11). It's not really that important to me, since I don't intend to use it that way, but just for you to know.

I'm starting to think this is a hardware problem, maybe some faulty component.

Third and last:

I've kept doing tests trying to retrieve more information, in both of them the audio dropouts keep happening:

- Using the unit with the internal battery instead of power adaptor
- Creating a project using only virtual instruments (without any samples)

I would like to try an older firmware such as 2.11.4, but I cannot find the .img files for those. Is it possible/safe to downgrade the firmware? Any other suggestions apart from what I already tried? I can upload some audio example where the glitching is noticeable.

I will try to contact the spanish store that sold my unit (it's still in warranty) to see if they can move the support thing a bit faster, since I just saw a post here of a user that has been waiting for weeks with no response in the akaipro support forum. Which is actually unbelievable, and shouldn't be tolerated.

Thanks!

... At first they appear sporadically, but then they occur more often every time and finally they are constantly present, to the point that creating almost like a bitcrush effect. ...

I remember that effect from my Alesis ioDock (also inMusic brand).
It happened randomly and I never could locate the source, regardless how hard I tried. There could be 3 days without or it happened every 20 minutes.
I assume it was related to the charging electronic because one day that failed (no more power to the iPad, everything else still working) and from then on the effect never returned.

Exchange the unit while under warranty. There is no cure (if it‘s the same flaw).
Btw there was a Behringer clone of the dock, which also had this „feature“.

Well, this is super-weird but I actually found version 2.11.4 .img file online and the audio glitch doesn't happen with that version. I mean, with 2.11.6 and 2.11.7 it happens in just a few minutes but with 2.11.4 yesterday and today I've been working more than two hours straight without a single click. I actually tried going from 2.11.4 to 2.11.6 but it fails again (in some devices, skipping a version when updating can be problematic and I came from version 2.11.3). So, back to 2.11.4 and everything is ok.

I haven't managed to find 2.11.5 .img file, to test that version and also if upgrading from 5 to 6 it doesn't happen. If someone has an URL to that .img file, it would be great.

Thank you guys, I'll keep this updated but this post can be useful in case someone else has this problem (heard nothing from Akai "support" yet).

Any link to 2.11.5 .img file? I can use the unit perfectly with 2.11.4, but I'm kind of curious about this. If the hardware is fine, and it is, the glitching has to be a software issue.

I'm thinking that maybe 2.11.5 included an update to some internal microcontroller.

Also, still no reply from Akai support. I really hope not to have any more issues in the future, it's definitely the worst support I've ever had from ANY product, not only audio. I mean, even the Amazon fake brands of cheap knockoffs answer you within one or two days, how can this multinational company be worse than those? How many support messages can they possibly have to answer? It's terrible. I mean, this is an expensive and complex product that will have problems and defects for sure, they should dimension their support department to have any problem answered within 24h.

Sorry for the rant, but these things drive me nuts.

Install the buggy firmware and then send it to the reseller for service? Then they'll have to at least comment on it. Is their response going to be downgrading to 2.11.4 and telling you not to update ever again? Or will they give you a replacement unit that does work with newer firmwares?

Firmware 2.11.5 can still be downloaded on the AKAI Pro website if you scroll to the bottom of the page. Here is the direct link to MPC-2.11.5-Update.img.

Oh, you are right, thanks!

Anyway, I tested it and it also fails so my conclusion is that the "problem" starts with 2.11.5, because I've been working a lot of hours with the 2.11.4 and no sign of failure.

I also wrote to the reseller just in case they have more info from a different support service (definitely it cannot be the same: no response yet) and they told me that AKAI is aware of the issue and they will solve it in a future update. Which makes me suspicious for two reasons: I cannot find anyone with the same problem posted in a forum, reddit or wherever, and also there have been two versions already after the problematic one and they haven't solved it.

I'll keep pushing on InMusic support, but this seems to go for long.

Thank you for your answers! I'll update if anything comes up.

Your reseller is likely fobbing you off with this, the fact is your MPC is not usable, probably due to a hardware failure. Plenty of public reports of these issues with USB audio interfaces, not seen any reports of this on the internal device. I have not experienced this personally. But it is possible that people have reported this, not everyone posts these things to social media, but the chances are quite low, and if it were a bug I think we would be seeing something from other users as well.

The fact is, Akai should be responding to this. Personally I'd be demanding this gets attended to by the retailer. Not sure where you are located, in the UK/Europe the retailer needs to deal with it, the contract is with them.

BTW, there is a live chat on the Akai web site, try using that, perhaps you'll get some direct engagement.

if it only happens after a while you are working try the following thing:
hit stop twice quickly, it "resets" the cpu load. check if the glitches are temporarily gone and if the cpu is gone back to normal %.

if this is the case, it's related to the fact that the cpu load isn't very well optimized and cpu drain from use of effects builds up over time. the solution is use less effects. there are a couple things you can do:
1)put reverbs\delays on aux return tracks and use sends instead of putting multiple reverbs on single channels\pads.
2)flatten pads with effects in your drum programs.