MPC X - Audio device error 71 and then freezes.

There needs to be a sticky for not posting these type of files, instead of you cursing out people that don't know why that's a problem & without an explanation, especially since sharing it seems like the logical thing to do on a site dedicated to MPC's...just something to think about.

Maoxiung wrote:"...system files were missing, and that only in workshop these can be restored."

This is brain dead stuff. So was the product put in this state by the user, by using regular functions available in the product's user interface? That's like having a BRICK DEVICE button. I wonder what kind of reasoning was behind that design.

Lampdog wrote:Sharing a legal / intellectual IP that will belongs to Akai where they hold the rights to distribute. You don't hold those rights. No.

Sharing an intellectual IP that can at worst get Tutor sued / site shutdown for piracy.
You can figure that much?? I don't need to explain. Shame.

Sharing because you "feel" entitled to share something that isn't yours to share in the first place. No.

Anytime piracy comes up and I see where it's suggested on this site I'll do the same thing.
We want this site up, not down. Take that somewhere else and kill another site.

I actually didn't curse any one out.

If it's that important & people keep doing it or think it's good idea to do, why not make it sticky?
Instead of getting upset everytime someone does this or attempt to do & then don't even explain to the person why not. Just: "No, no and flowers no. Don’t post the file here. Don’t suggest that sharing here." Keep in mind you said this to a new member with only 4 post. That's not the best way to handle this situation. Like I told you when did this to me, don't just tell me don't do it, give the explanation or a link to it. A new person to the site my also be new to insanity of Akai & aren't thinking of IP laws when sharing files.

Making a sticky titled: *WARING: DON’T POST THESE KINDS OF FILE HERE!!!" Or something like this would be more effective & may even help in court if someone does & it goes unnoticed at least you or Tutor can say we put a warning not may not help but it better than the current strategy.

Let a stranger answer one of your love ones like that & see if you sit there all peaceful & say well he didn't really curse you out.

Lampdog wrote:Not upset. Didn’t curse anyone out. We both know what being cursed out sounds like, stop frontin. Keep on speaking untruths. Done.

Wow, that all you took from my comment. Just make a sticky bro.

Lampdog wrote: Don’t post the file here.
Don’t suggest that sharing here.

Well...it's already done ... But I promise not to do it again : )
As A Supreme Moderator I understand that you have to say those words.
But I hope you'll let me say that, in a critical point of view, the outlaw piracy is more to deliver a device, linux system based, with no re-install media, nor factory reset option.
Then, when the device crash by itself (can't be the user's fault 'cause we have no way to edit files in this internal SD, apart opening the device and void the waranty) force users to pay for a shiping to workshop (case of a warantied device), or for the device's shiping and a system re-instal (case of an out of waranty device).
It's not fairplay, I was expected more from Akay than a kind of raketeering to solve a problem that is not the user's fault...
And I'm a litle bit astonished to be pointed as a pirate when I'm just trying to help other users also victims of this unfair thing.
Those system re-instal files should be available just as system updates. And I wonder how it's legal not to do it.

Nonetheless I apreciate that you're here to check about all those posts, and allow us to express even bad reviews about Akay, thank you !

HouseWithoutMouse wrote:So was the product put in this state by the user, by using regular functions available in the product's user interface? That's like having a BRICK DEVICE button.

I don't really understand the meaning of your sentence (sorry I'm french and google don't help here) do you mean that I could have done something by myself that have corupted system files? No I couldn't did that because the internal SD isn't accessible without opening the device.

EDIT: looking to other forums, it seems that the system files aren't in the internal SD but somewhere else in the hardware...so we have no solution to re-install those files by ourselves anyway.
And, by the way, obviously no way to damage those files with our litle hands...
(source : https://fr.audiofanzine.com/sequenceur- ... 68282.html)


(Mhh, can someone tell me where to click to be notified about answers here, I can't find the 'follow' buton...I must be dumb)

I'm no expert on it, but you can technically get at the internal SD storage in a couple different ways.
1) You can take the device apart, and get to the internal SD physically, but this is a lot of work and you can damage the internals as some of them are delicate
2) There are several custom firmware solutions that would allow you to get access to ssh to the device so you could copy files through sftp or similar means

I don't really have much better answers beyond that because I haven't gone down either of those paths, but I am aware they exist.

How ! SSH mod looks great! seems to be the solution for those who have no anymore waranty support.
I have just googled SSH + MPC and droped on a github howto, thanx to those people for making all those things possible...and thank you mate : )

(still dunno how to be notified about answers here...)

Hacked firmware is definitely the way forward. You can download the factory content from your akai account, install it on your computer and then copy to your standalone internal disk. Plus you get to backup all your content easily via SFTP and do all sorts of the good stuff. If you need to send back your MPC was warranty purposes, just re-install the official firmware.

Regarding distribution of the factory content, I know this sucks and I absolutely agree that it's not the fault of the customer and that Akai should provide this special standalone installer inside your Akai account. But this is still copyrighted content, in fact Akai still sell it as a separate product (it was in their recent summer sale). Hence why we are not able to share it on the site.

Its 2024 and i still get these -71 code errors. I emailed akai a long time ago (warranty was done) and they were no help. A crash happened to me at a rehearsal once and i immediately went and bought a sp404 for live shows. Wont be using or purchasing another mpc until akai’s right to repair policies improve.

I just got a 2nd hand MPC Live II from GC and had this issue. Seemed to be heat related, because from a cold start everything worked fine for about 20-30 minutes, then the error happens, and a restart will result in an immediate repeat of the error. Turn it off, let it cool down, start it up, and again it will work 20-30 minutes. Doesn't seem to matter if its playing anything or just sitting idle with an empty project. Took it back, which I am bummed about as otherwise everything was working and the price was $200 less than the cheapest they now have listed.

This was with no SSD or external SD card. I did a firmware upgrade, reset preferences, and restored the internal SSD content. I also saw a video with someone having this error due to a loose cable harness, so I opened it up and checked that but the cable was properly seated. None of these made a difference; still had the same problem.

Thankfully I hadn't sold my mk1 yet.

Just to say that I've the feeling that this error code seems to point on a lot of differents issues (pretty much the same as cars' notification are doing nowadays) . My MPC returned this error code and first I thought about an hardware issue because of the fact that it didn't happened on a fresh start but after a while. Actually It was nothing but a software issue. See my post above : viewtopic.php?f=48&t=213704&start=0#p1868016

geekraver wrote:I just got a 2nd hand MPC Live II from GC and had this issue. Seemed to be heat related, because from a cold start everything worked fine for about 20-30 minutes, then the error happens, and a restart will result in an immediate repeat of the error. Turn it off, let it cool down, start it up, and again it will work 20-30 minutes. Doesn't seem to matter if its playing anything or just sitting idle with an empty project. Took it back, which I am bummed about as otherwise everything was working and the price was $200 less than the cheapest they now have listed.

This was with no SSD or external SD card. I did a firmware upgrade, reset preferences, and restored the internal SSD content. I also saw a video with someone having this error due to a loose cable harness, so I opened it up and checked that but the cable was properly seated. None of these made a difference; still had the same problem.

Thankfully I hadn't sold my mk1 yet.

this could be the carrier board being faulty. you can get a new one from mpc stuff. some have also removed the back cover and re-seated the ribbon connectors which helped some out with errors like this.