Technical questions for the MPC2000xl and the MPC2000
User avatar
By astromonk108 Thu Dec 17, 2015 6:29 am
Image

I was just erasing a pad sequence from a track aand itdid this and I just lost the heat I was making :( seems to be fine when I turned it back on but im curious as to know what caused it
:?:
User avatar
By The Jackal Thu Dec 17, 2015 7:17 am
Hmmm crazy...the first column contains letters AX-DX, so maybe that has something to do with the pad banks and the last column with numbers in the rows almost looks like MIDI CC/Sysex data, Note On/Off information. Some of it, like "SP:0A70" and "SI:0D73", might have something to do with MIDI notes or ranges that are assigned to pads in things like bank A and bank D. It almost looks like data the MPC handles in the background and doesn't normally show you, but I don't think it's some kind of menu you can access either. Maybe your MPC just glitched out and displayed some shit it was processing. I dunno though, I'm just going off reoccuring patterns and coincidences I'm seeing in those lines of letters & numbers.

I think it's become one with the Matrix :lol:
User avatar
By Coz Thu Dec 17, 2015 9:36 am
That happened several times to me when I had the XL. :fku:
User avatar
By distortedtekno Thu Dec 17, 2015 6:07 pm
Coz wrote:That happened several times to me when I had the XL. :fku:

Damn. What OS version were you running when you seen that happen?

@ astromonk108 - Which OS version are you running?

I'm curious to know if this issue can be isolated to a specific OS version. I don't have any experience with the 2000xl. But it would be beneficial for all of us to know if it's an isolated issue pertaining to a specific OS version, or if occurs on other versions. Even though there's nothing Akai can do about it, we could all benefit by figuring out how to avoid that crash from happening and losing a good amount of work.
By solidsilver Thu Dec 17, 2015 9:14 pm
Before I put in my hot swap drive I regularly got that on the start up, it was a matter of timing based upon when I put my CF card in. Id had enough of that screen so I splashed the cash on the new one. Its like giving the MPC a heart transplant.

I run 1.2 (though 1.14c is reported on the hidden screen which is confusing). Mine is an MPC 2000 XL SE2
User avatar
By astromonk108 Tue Dec 22, 2015 8:25 pm
I run 1.2 as well on a se3. I just use floppies. I stole a cf reader from frys that allegedly works but it'snot hhot swap. So you're saying this happens alot on non hot swap able card readers?
User avatar
By Coz Wed Dec 23, 2015 11:32 pm
distortedtekno wrote:Damn. What OS version were you running when you seen that happen?



I think it was 1.14.

It only seemed to happen when there were a lot of samples and sequence data in memory.
By edocronian Mon Jan 18, 2016 8:28 pm
Coz wrote:

I think it was 1.14.

It only seemed to happen when there were a lot of samples and sequence data in memory.


If RAM goes bad, its usually a chip, rather than the whole module, so if it goes bananas when you hit 6.2meg used, then the issue is in which ever chip holds that part of memory. If its a lot of data in RAM, and the MPC fills its RAM from the bottom up (not sure on that part) then its probably in the area of that amount. It's probably time for a RAM change soon.
User avatar
By Lampdog Tue Jan 19, 2016 7:09 pm
It's a "untrapped error". Developers can read through that, you can't, just reboot, no other choice.
Usually erros like this are "trapped" and you don't see them, never notice them or anything. This one that "got away", hence untrapped. Reboot move on.