MPC500 RAM problems/errors and fixes

Installed an unofficial RAM as many of us have a few months ago, it worked just fine.

Then,,,,,,,,,,,,,,,,

I started to get the usual errors that are so regularly spoken about in this forum, among other errors i got was the "Cpu addr" error.

I AM 100% POSSATIVE I HAVE FOUND THE SOURCE OF THIS ERROR!!!

I belive it stems from the fact that the MPC500s RAM holder is relativly flimsy and very stupidly placed directly behind the pads, i belive that contsant impact from striking pads (or general shaking of the unit such as carrying your MPC500 around in a rucksack or bag) lousens the RAM holder to the point the RAM can move in the holder slightly therfore breaking the connection for a moment, the more you use your mpc the worse this problem gets to the point simply moving or toutching the MPC500 can trigger this error, infact if you stike the pads hard enough you can even pop the ram out of the ram holder!!!!!!

I DO NOT BELIVE INSTALLING THE AKAI RAM WILL SOLVE THIS PROBLEM, I HAVE TAKKEN MY MPC TO AN ELECTRICIAN AND MY PROGNOSES WAS ACCEPTED AS THE MOST PROBABLE CAUSE FOR THE PROBLEM.

HERE ARE POSSIBLE FIXES,


Glue the edges of the RAM to the arms of the RAM holder (taking care not to get glue on any of the ram curcuitry).

or

Put a rubber band around the RAM and arms of the RAM holder.


PLEASE FEEL FREE TO SUGGEST OTHER POSSIBLE FIXES!!!!


*I have used the glue method (super glue) and it works to a degree but striking the MPC500s pads hard or carring the MPC500 around in a rucksack/bag will still shake up the ram enough for it to dislodge from the glue, when this happens the typical MPC500 RAM errors return.

**Edit- I do understand that some people have had success in the short term by simply using a differnt RAM (that also fits the exact requirement to max out the MPC500), i belive this may in some situations only solve the problem at that time because certant brands of RAM are a tiny bit wider then others (were talkin like 1mm or so) hence makking them less lightly to move at that time (before the RAM holder becomes old and lousens its grip), but this will not solve the long term problem of the RAM holder simply being flimsy and lousing its grip on the RAM with age leading to the RAM moving slightly within the holder causing a loss of connection between RAM and MPC which results in the notorious read errors/freeezes.

why not remove and reput on the ram if it has moved

OriginalProducer wrote:why not remove and reput on the ram if it has moved

Because you would be doin that all the time once the arms of the ram holder are worn and louse (which only take a few months) as the ram holder itself is the problem here, you would litrely be takking the ram out and puttin it back in all the time doing this repeatadly will damage the ram itself as you should not really be toutching them that much as you can wear away layers of the metalic parts that make the ram work and also doing this over and over will break the arms of the ram holder.

hope someone tries out the ruberband method... it should work... ofcourse dont put a too strong one on it... no need to break the holster

Hey Cee,

I'm actually in the process of a (so far successful) RMA process with the seller of my MPC-500. Now mind you I'm working with only 3 months of having an MPC not a few years so I'm still cover'd under Akai Warranty.

I just wanted to cross post my problem, which was I guess out of the box, though it may be possible that this has to do with a re-sold product (unlikely) or with the Christmas shipping process, which I have had first hand experience working as a temp in a post-office just before christmas and packages are not treated as though they might have electronics in them!!

This is my post, underscoring a problem with the onboard RAM--

MPC 500 will not play more than one .5 second sample, help?
viewtopic.php?f=26&t=141830

But I guess my suggestion for this fix, is to go through an RMA process, if you're under a year it still has factory warranty, and also, maybe put insurance on your packages?? It only costs like 4 bucks.

S.J.

Speedy Jill wrote:Hey Cee,

I'm actually in the process of a (so far successful) RMA process with the seller of my MPC-500. Now mind you I'm working with only 3 months of having an MPC not a few years so I'm still cover'd under Akai Warranty.

I just wanted to cross post my problem, which was I guess out of the box, though it may be possible that this has to do with a re-sold product (unlikely) or with the Christmas shipping process, which I have had first hand experience working as a temp in a post-office just before christmas and packages are not treated as though they might have electronics in them!!

This is my post, underscoring a problem with the onboard RAM--

MPC 500 will not play more than one .5 second sample, help?
viewtopic.php?f=26&t=141830

But I guess my suggestion for this fix, is to go through an RMA process, if you're under a year it still has factory warranty, and also, maybe put insurance on your packages?? It only costs like 4 bucks.

S.J.

Just a thought brother, but do you mean your mpc will not play any more then 5seconds of a sample if you press

mode

load(pad 2)

then naviagate to your sample in your specified folder

then press play

?

If you are only getting 5 seconds of play in the above^ scenario then that is perfectly normal as you are just auditioning a sound and it is not yet assigned to a pad and the mpc500 will not play the sample in full if it is over a certant length.

If your program is perfectly normal and the mpc is not autoloading a program with changes made to that program (as i have set mine to), so if your on a totally fresh program and your not playing via trim mode or with decay turned up on that sample in the program or anything untaward like that (even stuff like mute groups or effects added maybe), there really is no reason you should get the type of behaviour you have described from the mpc500 as default, assuming you are talking about triggering samples from striking the pads, if this is the case i would return your MPC500 if possible.

If the later is the case and you do not have addition RAM installed (and you are only running the 16mb factory RAM) then i doubt it is any of the MPC500 generic RAM problems, plus it sounds possibly (just guessing from how your post is worded) like you can load multiple samples that are not playing in full, the fact you can load several samples does suggest that your RAM is not damaged and running on less MB that would only limit you to 5seconds (which would not be much RAM at all!) as if this were true you would not be able to load multiple samples. If this is the case i would return the MPC500 as it is broken and probably has some convoluted motherboard problem (maybe brang on by the way it was treated as it came through the mail) that just wont get fixed easy/if at all.

I tried so many things.

This happens in a blank program, it happens in the pre-set (demo) program. It has to do with anything I use 0.5 second samples as an example. Any length. I could be 5 seconds it could be 0.5 seconds, also it happens consistently yet randomly based around pad hits.

It happens no matter what the sample length and it happens no matter what the program setting. It is not related to any filter, effect, decay, attack or anything. It is not related to mono and poly its not related to mono and stereo. It is not program related. It happens both inside a sequence playing, and when you are just hitting pads outside of a sequence. It happens in blank program and factory pre-sets.

A good example of how it works is if you have a longer lets say three second sample on a loop. Then you play some drums over top of this. It will randomly shut off upon the hitting of a new sample. So you can theoretically for a loop or two play through with the drums over top (rare) but most of the time the allready playing sample will randomly stop upon activating a new sample from the pads. It could happen on any sample from any other sample being played. It is pad and program independent. (I've been trying to resolve this for months)

Anyhow. I am 100% at this point that it is a hardware issue.

Note: If you have problems related to hardware and you are under a year of ownership your cover'd under manufactures warranty. THis is a really good thing!!!

That's basically the main reason I cross-posted this. Check your warranty is could be a blessing.

The OP was brilliant - not sure about superglue and sht like that, but I certainly found that my RAM had worked its way loose - possibly I hit the pads too hard, I don't know, but I clicked that RAM right back in and it was all good.

I've searched a few forum posts and had worries about poly/monophony, soft and hardware issues, etc etc... Was getting serious problems when messing around with reverbs and delays in particular, losing polyphony, v. v. strange stereo issues (perhaps MPC being only able to use one channel of a stereo wav) - I tried turning off then on again, and played around with the FX on the first pre set sequence - delay and reverb really killed it, confirming I had issues, as if the presets are f-ed up then something must be wrong! Was getting a bit upset (want to sell it and thought there's no way I can sell a dodgy piece of gear) and then finally found this post!

Opened the back, and the RAM stick just about fell out. Clicked it back down, all good! Wacked a few pads, then the MPC froze, and the startup screen came straight back on, and said I had 16mb (should be 128). Opened it up and sure enough the RAM fell back out.

SO... Here's my two cents to add to the OP - I will admit with hindsight I probably didn't install the RAM correctly, and wonder if a there are a bunch of other noobs like me making the same mistakes. Basically I was scared to jam the RAM down properly. It fits so snugly and tightly that when I first put it in a year or two ago I thought I was forcing it. Since having much more experience with computers and stuff like this I've become a lot braver, and have now clicked the RAM RIGHT DOWN so it stays put.

The thing worth noting is that when it was half in/half out it would work, and register on startup screen as 128mb, and then wobble about through use I guess. My point is I missed it, and never even thought to check the RAM.

Not saying it'll fix everyones problems but it worked for me. Problem now is I'm skint and need to sell the MPC but since the glitches and issues have gone I've fallen back in love with it! Learned some useful things along the way too RE poly/mono, mono/stereo...